Reality shows that implementations can very well implement the same extensions. If you don't use extremely outdated clients you will find they do have compatible file transfer and A/V calls. ActivityPub works the same way.

Meanwhile Matrix Ltd. cooks up a completely new, incompatible protocol instead of building upon existing internet standards.

[–] jarfil@beehaw.org 3 points 6 months ago* (last edited 6 months ago) (1 children)

There is no "Matrix Ltd.", the Matrix protocol is being worked on by the "Matrix Foundation", a UK CIC (kind of NGO), with adoption by French an German governments.

XMPP clients "appear" to have compatible file transfer and A/V calls... until you try using them and find out they sometimes lose bytes from one client to another, but not the other way around, sometimes calls only work one way, and so on. That's the effect of not having a minimum common ground defined in the protocol spec.

[–] kpw@kbin.social 4 points 6 months ago

The NGO is a decoy organization with exactly the same people (minus one) as the VC funded startup. Go look at the "core spec team" and find out which organization they belong to.

Your information on XMPP seems to be quite outdated. File transfer in XMPP is now mostly done by uploading the file via HTTP and sending the URL. Audio calls are done using WebRTC and work two ways.