Microsoft XMPP Implementation Issues

So, Microsoft have finally caved and implemented an XMPP interface for Windows Live Messenger. It sounds great, but I feel they’ve messed up on a few things.

Custom login procedure
My initial thought was to open Adium and add my Windows Live account as an XMPP account. I found the XMPP server address ( from some sample code they have on Github, but alas, it wouldn’t log in. Why? Microsoft have decided to use a custom OAuth 2 implementation for login, thus making all current XMPP clients incompatible. Ouch. So you can probably say goodbye to ever using WLM in iChat unless Microsoft decide to change it.

No write access to contacts list
Third party clients that decide to implement XMPP for WLM will find that they have no way of adding new contacts or accepting invitations from others. This has to be done in either Microsoft’s own client, or in a browser on web messenger. This kinda gimps third party clients for those who want to just rely on one interface, and one interface only.

XMPP Server Federation
I must preface this by mentioning that I’m not sure whether they support XMPP Federation or not. Microsoft go on about choice of services and not worrying about what your friends use, but there’s no clear mention of whether this means XMPP Federation. They mention Facebook and Yahoo by name, which as you may know, already have WLM integration. I attempted to add my Windows Live account to my Google Talk contacts list, but to no avail. One reason this is a big deal to me is that I’m expecting to get my hands on a Nokia Lumia 800 very soon, and would love to able to chat with my Google Talk contacts within the messaging hub on Windows Phone. It would be somewhat similar to the seamlessness of iMessage, although from what I can tell, not quite that seamless, but still awesome.

Anyone can build a Messenger client—with open standards access via XMPP - The official engineering blog for Hotmail, Messenger, SkyDrive, and Windows Live, hosted by The Windows Blog