IETF should keep XMPP as IM standard, instead of Matrix
Surprisingly short text for how long it sets up an analogy with little value.<p>The problem with XMPP has always been that it is too extensible with too few guarantees in interoperability. You&#x27;ll know what this means if you ever set up OMEMO over 3 different client implementations. It also does too much, anything from Kafkaesque (pun intended) persistent pubsub to content labels. The quality of clients is simply not good enough, so most XEPs end up in specialized variants of clients or proprietary implementations (Facebook, GTalk, EA Origin) that lean more on ejabberd&#x27;s scalability than other XMPP features like federation.<p>Also, XML is not a good serialization format, and some of the requirements in the protocol are pretty exotic and not trivial to implement in a lot of languages. Like setting up TLS on an existing connection (plus the absolute refusal of the XMPP WG to allow on-connect TLS). JSON over websocket or HTTP are just better at reaching a wide audience of developers.