3 ms·
Back in '99, I was working in the Instant-Messaging and Chat-On-Page sector. Let me tell you what I observed back then: The IETF group working on IM was compri
by beagle3 16y ago
Back in '99, I was working in the Instant-Messaging and Chat-On-Page sector. Let me tell you what I observed back then:
The IETF group working on IM was comprised of people from Netscape, Microsoft, AOL and a few others. At that point, AOL owned the IM world through AOL Messenger and (then recently acquired) ICQ. Microsoft was starting to make a dent with MSN Messenger after they started bundling it with the O/S and everything.
I was following the IETF discussions and mailing lists, and after a couple of months realised that the people on these lists had no reason to make things happen -- on the contrary. Everyone wanted AOL to open up the ICQ/AOL networks; they wouldn't. Everyone was already working on their own IM protocol, and didn't want to share it with the others -- they just wanted the OTHERS to share THEIRS. The discussions were long and pointless, revolving around semantics and irrelevant scenarios.
XMPP/Jabber developer was among the participants. The suggestions were full of flaws, complex and inefficient to implement, and no one liked them. But he was the only guy releasing code. And after a couple of years (sometime in 2001 IIRC -- I was no longer closely following it) it actually became usable.
It is still inefficient; it is still too complex for what it does; But for the last 9 years or so, it was the only option for a documented protocol with an open source implementation that you could find cross-platform clients for and install inside your own network.
And that's a win.