Blog Post

LiveJournal Goes XMPP-Jabber

Niall Kennedy points out that Live Journal is going to add XMPP and Jabber support to its community. Users can log into the Jabber chat client using their Live Journal usernames and passwords. There are plans to federate with Google Talk as well. Jabber/XMPP works over many popular clients such as iChat, Adium, Trillian, Gaim.

I think this deal is going to have a much bigger impact on Jabber/XMPP compared to preceding deals. There are 10 million LJ users and it is a vibrant community. Given the highly-social nature of LJ community, I expect rapid adoption. I wonder if there are any plans to add voice-to-the-mix? Wonder if this would work with Gizmo Project? (Michael Robertson, speak to us!)

Longer term, I wonder if this could become a major trend. Small, highly customized IM networks, federating with each other, and breaking the stranglehold of the big three IM networks. Thoughts?

Also: Big, Fat and Bulky: State of the IM Nation. Om and Niall Podsessions on Instant Messaging.

10 Responses to “LiveJournal Goes XMPP-Jabber”

  1. Google Talk federation is automatic, since it’s just another XMPP/Jabber server. Gizmo uses XMPP for chat and presence, so that works automatically too. For voice, Gizmo uses SIP, which is separate. LiveJournal allows you to post recordings to your journal (voice post); you can already call ljvoicepost on Gizmo (, or use a regular phone number.

    Integrating SIP/SIMPLE with Jabber is in a draft state and Google’s Jingle spec for intra-Jabber VoiP is still very young. And, actually, Jingle will require nothing from the server (DJabberd for; so whenever clients support it, it should just work. AFAIK, the official Google Talk client is the only released Jabber client that actually supports it, though.

  2. Jabber’s XMPP is the IETF standard for IM and Presence. Google is using XMPP. HP, Oracle, Sun, and Apple are major users.

    Here’s an excerpt from a recent Jabber press release:

    “With approval of XMPP by the IETF in 2004, the JSF (Jabber Software Foundation) continues to develop XMPP extensions that meet the needs of its many stakeholders: open-source and commercial developers (including Apple, HP, Oracle, and Sun), organizations large and small (including the U.S. defense establishment and most Wall Street investment banks), Internet and mobile service providers (including Google, NTT, and Orange), and over 25 million end users worldwide.”

  3. Federating IM networks makes perfect sense, using preferred front-ends that specific communities of users prefer using a common lingua franca. XMPP support in iChat, for example appeals to Mac users, whereas LJ appeals to bloggers, all speaking a common ‘tongue’, but understandable to others using the same backend. Think of it as akin to different dialects of English or Mandarin, for example – understandable to anyone who knows the language, but with just enough personality to identify the user as coming from a specific area.

  4. We also provide our users with a Jabber IM system and send alerts (for persistant search) to them using that.. since many IM clients these days support multiple protocols including jabber its easy to use many networks, federated or not, but its likely many more jabber networks will continue to spring up now.

  5. This is good news for Jabber/XMPP. I am not sure how much, if any difference it will make for LJ users. Instant messaging on websites is a challenge mainly because IM architecture is designed to connect trusted contacts. Websites, including social networks connect various degrees of strangers. You don’t want to share your IM information with strangers. As simple as that. If my buddies already have your IM, why share your IM information with strangers?