jimmahdigital.com

Instant Messaging 2.0

Posted by James | Filed under Code, Future, Mobile, Privacy, Social, Web

There are some interesting things going on in the world of Instant Messaging these days. There is potentially going to be a shift from proprietary networks to ones built on an open standard called Jabber (aka XMPP, Extensible Messaging and Presence Protocol). The technical details of Jabber which I’ll example below, make this a very big deal.

The biggest IM providers are MSN, AOL, Yahoo, and Google. For years, the first three operated proprietary, closed protocols. If you are logged in to AOL, you can’t talk to people logged in to MSN (there have been some efforts to link these networks; but in a such a way that the closed protocols are still used). You can’t reuse your contacts across accounts, just as MySpace contacts can’t be reused by Facebook (until DataPortability.org gets going maybe…).

Then Google entered the game. Instead of creating their own IM protocol, they implemented an existing well known IM protocol originally called Jabber, now called XMPP. XMPP had been around for a while and had been implemented most notably by several enterprise collaboration suite providers. But Google implementing it caused the big three to wake up and take notice.

Well, they have. In January AOL announced experimental support for XMPP. And just last week it was discovered that Yahoo is doing the same.

Google announced long ago that they would work with AOL to make their IM protocols interop. The assumed reason was to combat a Yahoo - MSN IM interop that was announced. But the Google - AOL interop never materialised. Instead you see AOL announcing (two years later) support for XMPP which obviates the need for a Google - AOL integration - since they would be speaking a common language. It appears that Google and AOL have finally achieved what they stated they would; which in turn put pressure on Yahoo to join in the love-fest.

Why is this a big deal? Well, from the point of view of existing IM users, it means that I’ll be able to talk to users on different networks. Beyond that, it doesn’t mean much. As a user of, say, AOL IM, I don’t care to much that the messages I exchange are done over a proprietary AOL messaging protocol or some open standard. I only care that it works. But to crazy software developers like myself, who like to dream big, it’s a really, really big deal.

XMPP is XML over TCP/IP, which is:

an open standard: meaning anyone can implement it, and get to play in the game.
extensible: meaning that it is designed so that developers can layer additional features onto it.
federated: if an XMPP server implements federation then users on different networks can communicate. This means, for example, when I’m logged into Google Talk, I can talk to AOL users.

If you’re still yawning, consider that TiVO recently announced that it is using XMPP for a whole host of features that have nothing to do with chatting. Take a gander at the XMPP extensions and you’ll see that the people driving XMPP standards are also thinking big. There are many features you can layer onto the IM social graph that having nothing to do with chatting. If AOL and Yahoo continue down the XMPP path, this will put tremendous pressure on MSN to follow suit. And I believe it will spark a wave of IM 2.0 startups (not just ones focused around mobile IM, which is where you see a lot of the focus today).

Consider that everyone IMs. Websites come and go - but IM remains. What’s important about that is that your social network persists over many, many years. My ICQ buddy list is useless, as I never use that service any more. But my MSN buddy list, which I use regularly, has been around for nearly 10 years. And with XMPP, it could be reusable. It could be the standard machine-readable way to represent a social network.

IM is getting standardised… it’s getting standardised on an open standard… and the open standard is extensible.

Share and Enjoy: