this post was submitted on 25 Jun 2023
135 points (100.0% liked)
Technology
37603 readers
376 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If itās technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if theyāre wrong, or use a Linux distro you donāt like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
There's a lot of subjectivity and emotions there. So, let's look at the facts instead: XMPP is a very simple protocol at its core. You can literally implement RFC6120 in an afternoon. But you have no reason to, because of the many existing mature implementations, which takes us to the second important aspect (IMO): "liveliness". XMPP has many well maintained client AND server implementations and a rich and dynamic ecosystem. Unlike Matrix, Zulip, RocketChat, Mattermost, ā¦ it's not pushed forward by a single entity, which severely reduces the probability and effects a bad actor might introduce. XMPP is extensible in ways that makes it more future-proof and resilient than most alternatives.
Those not learning from history are doomed to repeat it, and if you ask me, Matrix is doing everything that XMPP did, but worse :) I only arrived to XMPP after fighting for the Matrix cause and deeming it a lost one. No time to elaborate, but the protocol itself is insane and its creators are experts in deception and empty promises.
Edit: more about Matrix https://programming.dev/comment/66569