3 ms·
To all of those moaning about how great XMPP was: It wasn't. In a multi-device/mobile world XMPP is shit. HN constantly complains about Slack/Hipchat/etc "Rein
by joshstrange 11y ago
To all of those moaning about how great XMPP was: It wasn't.
In a multi-device/mobile world XMPP is shit. HN constantly complains about Slack/Hipchat/etc "Reinventing the wheel". "We have IRC and XMPP" they cry without stopping for a second to understand that IRC/XMPP as not trivial to setup correctly, mobile support is complete shit, without things like bouncers or servers to hold all your messages you can lose things and stuff not be in sync, clients can't really add features unless all client can support it, and more.
Does it kind of suck that the dream of federated chat died/is dying? Yes but if it doesn't support what users really want then it's the standards fault. I don't blame any of the major players for pulling support, it wasn't going to move fast enough so they ditched it and built something that would.
- hmans 11y agoXMPP (like many other similar protocols) is failing not because it's "not moving fast enough", but because open standards are required to make a commitment to simplicity (in order to be inclusive towards as many devices as possibility) which, in many cases, directly opposes the requirements of a business (ie. having unique features.) In the end, it's quite simple: federation and simplicity work _against_ many business cases. This is why this stuff is being dropped by the big players in favor of proprietary solutions left, right and center.
- joshstrange 11y agoPush notifications, message syncing, read receipts, offline sending (as in I'm offline, you send a message, I get it when I log in), encrypted chat, mobile clients, desktop clients, chat room support, direct message support. These are the things I need out of chat and while XMPP had extensions for some of those things finding server software and client that supported it reliably was near impossible.