That compliance table is the thing really killing XMPP for practical modern usage. I tried to write an XMPP client about a year ago and found out about that co

That compliance table is the thing really killing XMPP for practical modern usage. I tried to write an XMPP client about a year ago and found out about that compatibility table the hard way. It's rough -- I had no idea what I was getting into. Turns out that XMPP, before expansions, has no standard definition of what message IDs are. Which means "good luck, have fun!" is pretty much the best anyone can hope for on synchronizing messages when you have multiple devices or when the network flakes on you. Which in turn means XMPP is basically unusable on multiple devices. If you're lucky, everything supports all the same extensions, and it'll probably work most of the time; but if any piece of software you use is missing one extension, your day is toast. (And even then, frankly, the "carbons" API is wrong-headed and not very capable of recovering from network failures. In no uncertain terms: It's time to move on.) I wrote about this more previously on HN: https://news.ycombinator.com/item?id=9772968 https://news.ycombinator.com/item?id=9772968