From a design perspective I think MSNP was quite good - mostly text-based, simple request/response structure, and relatively easy to write a client for (and I have.) If one were so inclined and knowledgeable, it's almost possible to just telnet to port 1863 and use the raw protocol, in a similar manner to IRC. The only flaw today would be the fact that it's plaintext, but were MS so inclined to do so, I believe they could've just wrapped it in TLS.<p>In comparison, the Skype native protocol is highly obfuscated binary, so the few reverse-engineering efforts that have surfaced thus far have not revealed all that much. Combine that with the legal issues and it's no wonder a lot of people are still trying to hang onto MSNP for as long as they can with all the unofficial clients out there that support it. On the other hand, from a few sources including the linked blog post (<a href="http://messengergeek.wordpress.com/2014/09/11/when-is-messenger-really-shutting-down/" rel="nofollow">http://messengergeek.wordpress.com/2014/09/11/when-is-messen...</a>) it appears MS is trying to replace the Skype protocol with a newer version of its own MSNP, so it's not all bad.<p>It looks like MSNP8 is still working, but my guess is that there's something at Microsoft that relies on this protocol which is what has kept it up for so long while some of the newer intermediate versions are no longer supported:<p><a href="http://wiki.dequis.org/projects/msn/protocol_versions/" rel="nofollow">http://wiki.dequis.org/projects/msn/protocol_versions/</a>