Web 2.0’s Catch 22
I’m sorry to say that not long ago, my personal life hit a Web 2.0 saturation point. Not because I’ve ceased to find interesting applications, but because there’s a finite limit to the number of things you can effectively maintain.
This seems to be the hidden cost that underlies Web 2.0 technology. As Dion Hinchcliffe pointed out two years ago, truly useful apps are few and far between:
Tons of new Web 2.0 startups are being released every day, I can’t even keep track of the social bookmarking sites alone (I came across three new ones yesterday, seriously). And some of the better Web 2.0 apps that are coming out are for laughably obscure vertical markets.
The biggest problem of course is that these services don’t actually talk to each other, which is kind of ironic considering that much of it is called “social” software. Even those companies who design apps to integrate with other 2.0 platforms, have yet to truly make the disparate parts communicate with one another.
For example, if you want to track you’re reading and share that with your friends, you might choose to join Goodreads. If you’re on Facebook, you could then add the Goodreads app that will pull your list of books into your profile. But if your friends are using LibraryThing, iRead, or Shelfari, then the only problem you’ve solved is displaying the results in a specific location. Facebook doesn’t allow any of these services to talk to one another, nor do any of them support a seamless interface with any of the other applications.
As Michael Hirschorn theorized last April, “the third rail of social media may ultimately come down to that most old-media of issues: ownership.” For users though, it comes down to a question of manageability: how many services can you reasonably manage before they become a liability on your time?
My profession has been grappling with this problem for years. While all of us are attempting to plug our collections into various applications in order to get the most out of our libraries, if we’re asking our patrons to join (yet another) service, how likely are they to take the offer? And at what point does every user wind up hitting their saturation point?

