XML means xmpp is awful apparently. I feel pretty alone in having a bad experience with matrix, but a good one with xmpp+omemo.
At least the SAX parsers I've used allowed to get partial "subnode DOMs", which makes it quite easy to use in practice.
That said I've only parsed ~1GB XML files (no embedded binaries), not sure if that counts as large enough.
What could possibly go wrong if users in a multi user chat see messages in different orders? This decision is a perfect example of how smart systems engineers can be so completely divorced from the real problem (human communication) that they make completely asinine choices justified by implementation details no user cares about.
Matrix needs to die so it can stop sucking the air out of this space. The funding problems are also completely predictable but that's an opinion for another time.
0 https://artificialworlds.net/blog/2024/12/04/message-order-i...
Or look at how until a few months ago, the media store of every homeserver served media on the internet without any authentication. Someone just had to post CP in a popular room and they'd get hundreds of servers rehosting it for free. (Recently they finally added the ability to require authentication for the media store, although they didn't add support for it to their web client, only their new Android one.)
This is not true. If it were true, it would imply you can't view any newly uploaded media from the web client. Here is the web implementation of MSC3916: https://github.com/element-hq/element-web/pull/27326