Windows Live Messenger's protocol has often faced criticism for its lack of standards. Today in a world of cross-platform communications and open software development these arguments have never been stronger. Kip Kniskern has raised questions to why this in the case within the light of Facebook Chat supporting XMPP:

Well of course to us, it "makes sense" to interoperate with Facebook (we hate having to keep the browser open during a FB chat), but Windows Live Messenger has been a notoriously closed system in the past, so we’re not sure it will make sense to Microsoft. However if it means losing customers who find themselves using Facebook Chat more and Windows Live Messenger less, that may change. We should be hearing more about the Windows Live Platform later this year, so maybe there’s hope that Facebook Chat may be part of that "major focus".



In response Dharmesh Mehta, director of Windows Live Product Management stated:

Windows Live participates in an industry defined by change. Consumer choice is continually expanding with new services launching almost daily. To this end, with Windows Live and Messenger, we are making it easier for consumers to integrate contacts, communications and sharing across the multitude of internet services they want to use. We'll interoperate where it makes sense, as we've done with Yahoo! and customers of Office Communications Server. We'll continue to invest in contact portability and identity standards, as we've done with our contacts APIs. And we'll integrate feeds, as we've done with over 75 top web services in the last year. This will continue to be a major focus going forward.



Source: LiveSide - Facebook opens Chat to XMPP: Will Messenger join in?


Criticism over Messenger's protocol lack of standards
Posted by absorbation on Mon 02 Mar 2009 (23:09 GMT) (1426 views)
For all of you who don't quite understand the title, the large IM producing software companies i.e. Microsoft and Yahoo! use their own protocol systems to communicate instant messages, an annoyance for developers who wish to make instant messaging a universal application, where popularity resides within the client, not in the network. Jabber is by far the most popular and modern IM protocol used by many applications.

I recently came across a post which details the problem with the likes of Microsoft's way of sending IMs:

For the sake of argument, assume that you have a cell phone and you're subscribed to Carrier A. You then wish to call, or send a message to, a friend who happens to be a subscriber of Carrier B. Naturally, you would expect your messages to get across, otherwise you wouldn’t be able to keep in touch and your provider would be severely restricting you to their network.


Well, this is not the case when it comes to Instant Messaging (IM) Services like MSN and Yahoo because they're not standard. In order to communicate with other people, all members must be part of the same network, and this means that if the network goes down (and it does more than anyone’s liking), everybody goes down with it!



The post highlights a prevailing problem with IM in our modern world. Technology has become about standards. Whether it's the using Bluetooth within phones, or reading our emails, regardless of which software we use. We expect similar services to work in harmony. Instant messaging still does not do this, and a consequence is losing users to other, more convenient methods of communication i.e. social networking.

Why You Should Avoid Using MSN


One can infer there has been a social revolution in terms of communication within the past couple of decades. One Computer Science professor I recently met compared the growth of the Internet to something as significant as the printing press. Emails created a new wave of productivity and when they became instant messages, the Internet became more responsive, while the introduction of websites such as Facebook have made the web more social. Has the social networking revolution damaged instant messaging? There is evidence to suggest this may be true. How are the IM giants reacting? TechCrunch argues not very much.

Historically, IM has existed on closed and proprietary systems, with dedicated clients that can only connect to a single network. For many years users with accounts on multiple networks (say, AOL and MSN), would have to keep multiple programs open, which ate up system resources and cluttered desktops. By 2000 a handful of clients emerged that would allow users to manage multiple IM accounts from a single program. These stayed largely under the radar until 2002, when a client called Trillian hit 1 million downloads (and then jumped to 5 million six months later).



IM is also ripe for innovation, but developers have been hampered by a near-complete lack of cooperation from the major IM networks. Perhaps developers will take advantage of the growing number of networks that are open, adding new features that make them attractive to users still stuck on the old behemoths. Then Yahoo and Microsoft might be compelled to finally change - or perish.



The article examines how recent integration is only a piecemeal solution, with no efficient, direct change being achieved. The argument is that Microsoft and Yahoo! should open up their IM clients and be able to talk to everyone. I highly recommend reading the full article.

As IM Finally Begins To Open Up, Yahoo And Microsoft Cling To The Stone Age


There has been a number of small things going on in the Messenger world in the past couple of weeks. Below is a summary of some of the news that we have failed to cover, or too small for its own post:

  1. IMO is a small, stable, compact web Messenger has undergone major changes this week. The development team have been working hard to improve services and have recently launched a new and improved imo.im, along with eight cool new features. IMO now offers a number of options that allow you to personalize your contacts list and prioritize your buddies. Click here to check IMO out!
  2. This week has seen an update to the Messenger protocol (common when new versions are released). However, there has been implementation problems, freezing some 3rd party IM clients out from signing into the Messenger servers. Although the issue has now been claimed to be resolved, there is an update for Pidgin and Messenger for Mac users to download
  3. Rebelsean has recently had the opportunity to interview some Windows Live directors. Having recently moved to Neowin, Sean has not forgotten his Messenger roots and has brought up the issue of tabbed conversations and what we can expect from Windows Live Wave 4. Generally he got a good feel for the direct Windows Live is heading in, and although is not Messenger specific, it still provides a useful insight to what's going at the live front


Although there are only three relatively small pieces of news to cover, I thought it may be in your interest to know about them. There are a few other stories that should pop-up in the next couple of days, but with most of my admins currently busy or disappearing, don't count on us to cover everything until February starts.