RSS never blocks you or goes down: why social networks need to be decentralized

Recurring outages on major networking sites such as Twitter and LinkedIn, along with incidents where Twitter members were mysteriously dropped for days at a time, have led many people to challenge the centralized control exerted by companies running social networks. Whether you're a street demonstrator or a business analyst, you may well have come to depend on Twitter. We may have been willing to build our virtual houses on shaky foundations might when they were temporary beach huts; but now we need to examine the ground on which many are proposing to build our virtual shopping malls and even our virtual federal offices.

Instead of the constant churning among the commercial sites du jour (Friendster, MySpace, Facebook, Twitter), the next generation of social networking increasingly appears to require a decentralized, peer-to-peer infrastructure. This article looks at available efforts in that space and suggests some principles to guide its development.

Update: a few days ago, OpenID expert Chris Messina and microblog developer Jyri Engeström published an article with conclusions similar to mine; clearly this is a felt need that's spreading across the Net. Interestingly, they approach the questions from a list of what information needs to be shared and how it needs to be transmitted; I come from the angle of what people want from each other and how their needs can be met. The two approaches converge, though. See the comments for other interesting related blogs.

(continue reading)

Four short links: 7 September 2009

XMPP, Future of Web Frameworks, Infrastructure Stories, Better Email Client

1. App Engine Now Supports XMPP (Jabber) -- messaging servers, whether XMPP or PubSubHubBub, are becoming an increasingly important way to loosely join the small pieces. Google's incorporation of XMPP into GAE reflects this (and the fact that Wave is built on XMPP). (via StPeter on Twitter)
2. Snakes on the Web (Jacob Kaplan-Moss) -- The best way to predict the future of web development, I think, is to keep asking ourselves the question that led to all the past advances: what sucks, and how can we fix it? So: what sucks about web development? An excellent and thought-provoking talk about the possible directions for improvement in web framework design.
3. Ravelry (Tim Bray) -- We’ve got 430,000 registered users, in a month we’ll see 200,000 of those, about 135,000 in a week and about 70,000 in a day. We peak at 3.6 million pageviews per day. That’s registered users only (doesn’t include the very few pages that are Google accessible) and does not include the usual API calls, RSS feeds, AJAX. [...] We have 7 servers running Gentoo Linux and virtualized into a total of 13 virtual servers with Xen. [...]". Interesting technical and business discussion with an unexpected busy site.
4. So's Your Facet: Faceted Global Search for Mozilla Thunderbird -- email clients are LONG overdue for improvement. Encouraging to see an active and open research project to improve it from the folks at Mozilla Messaging.

Breaking Down What's Happening on the Social Web

The past few weeks, John McCrea, Joseph Smarr, and I have been shooting a 15 minute video podcast called TheSocialWeb.tv. Each week we try to break down what's happened in the Social Web in a way that is understandable so you don't have to be living and breathing this stuff.

This week we discuss Meebo's announcement of Community Instant Messaging since it continues the trend of making the entire web more social while using existing building blocks to do so. As Joseph explained, the underlying architecture Meebo is using is Jabber/XMPP. What this means is that unlike Facebook's Chat, social networks using Meebo's Community IM have the ability to interoperate from day one if they choose to do so. Google's Friend Connect is another great example of reusing building blocks where they take advantage of OpenSocial, OpenID, and OAuth. Overtime supporting these underlying technologies becomes easier as companies like Google and Meebo start to build them into their products.

Last week we focused on Gnip and Identi.ca, explaining how Gnip is helping to change the model of accessing data on the web. Traditionally web APIs have been focused on pulling data though things like Twitter's XMPP Stream and Gnip are starting to flip this model on its head. And next week we'll be taping from Facebook's annual developer conference f8 in San Francisco. So please check it out, subscribe to our RSS feed (yes, we know our enclosures are broken), let us know what you think, and how we can do a better job of explaining the Social Web in an understandable way.