3 ms·
XMPP (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 s
by hmans 11y ago
XMPP (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.