312
Matrix 2.0 Is Here!
(matrix.org)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 29 Oct 2024
312 points (100.0% liked)
Fediverse
28188 readers
355 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
founded 1 year ago
MODERATORS
And to use it with a similar feature set, everyone is using different extensions which also have to be supported by the clients. I know there is this one server implementation (name escapes me at the moment) and Conversations on the client side, but it's hardly the standard and we're not really talking about plain XMPP then anymore.
The same is true if you use a Matrix server other than Synapse and a client other than Element. If fact these days the spec incompatibilities are way worse on Matrix than on XMPP.
Have you used XMPP recently and ran into the issue of non-obscure servers, clients, or self-hostable implementations using different extensions or not supporting them? (I actually haven't experienced this even on the obscure ones, but can't confirm for all of them). Please do not make that accusation, because that I'd really not what happens in reality.
Why not when... It literally is? And all major implementations follow it? That is by definition a standard.
Why not? "extensible" is in the name. It is meant to be extended. The protocol is being used exactly as planned and intended.