Jun
29
2009
0

In Response to Marco

This morning Marco Arment wrote:

Dear internet “social media experts”:

I really, really don’t care which office or restaurant you’re sitting in and checking into Foursquare from.

It’s important to balance the abundance of cheap, widespread internet publishing with appropriate considerations for your intended audience. If you’re trying to be interesting to anyone beyond… yourself, you have to consider whether anyone else in the world will benefit from spending a tiny slice of their time learning where you’re having coffee or holding a meeting.

This isn’t to say that such posts can’t contain other value. On the contrary, many of my favorite internet writers (like meaghano) write amusing, insightful, or touching stories around the trivial task of getting coffee. But when you tell Foursquare or Brightkite to automatically publish your location to Tumblr or Twitter, that’s not adding any value.

If your location isn’t interesting enough for you to manually write a post about it for some reason, why should your audience spend their time reading about it?

My experience using foursquare and Loquacious have developed a somewhat contrary opinion to Marco here. From the out I believe it’s important to state that I think Marco is a brilliant developer, and anyone who uses Tumblr or Instapaper should be glad he’s doing what he does. I’m not writing to pick a fight or insinuate that I believe he’s anything less than an inspired individual. That said, I think he’s going down the wrong road. Also, I don’t let foursquare publish to my Twitter stream, but I do allow Spymaster, and I’ve heard similar criticism of it.

First, foursquare evolves the criticism I’ve heard about Twitter time and time again, and the main point I believe Marco’s making: “Why do I care about your ____?” While those friends of mine who live in Washington may find value in some of my tweets, they almost certainly don’t give a shit when foursquare notifies them (on my behalf) that I’ve stopped into Mojo Bicycle Cafe. However, that information can be of value to say, the friends I have who find themselves nearby Mojo when they read that tweet; They have some amount of encouragement to swing by and join me for a pint. The point here is that each tweet I publish has a different potential value for each person who reads it.

Second, while I was in New York last month my good friend Niall Kennedy loaned me his HTC Magic in order to get a feel for Android 2.0 (I’m a big fan). One of the applications I used while carrying the phone was the Loquacious Twitter client. The killer feature here is the app’s ability to filter out things from my Twitter stream. Specifically, Loquacious gives me the ability to select particular users or services that I don’t want to see on my phone. Anyone who considers themselves a serious Twitter user probably has feelings similar to mine and Marco’s, where there may be users (or services) which publish what they believe is low-value information. By having the option of pruning my Twitter reading, I was able increase the value of my stream as a whole. A perfect example here is Urban Journal; when I’m sitting at my desk, the tweets about new posts to this blog are of high value to me, whereas when I was walking around Brooklyn, those same tweets were of significantly lesser value.

What my experience with Twitter and Loquacious have shown me is that intelligent software design can be a more effective means of resolving the sorts of criticisms of technology that Marco makes, rather than trying to directly influence how people choose to use those same technologies. I believe there’s a ‘lazyweb’ request here for developers start to consider the different conditions under which the value of communications change. If a future version of Loquacious (or Tweetie, or Peep, or TweetGenius) included support for location-based filtering of my Twitter stream, they’ll have my money shortly thereafter.

Written by JD Lewin in: social, software, twitter |

Powered by WordPress | Aeros Theme | TheBuckmaker.com WordPress Themes