I’ve personally not had terribly good experiences with Matrix. I found it to be slow at times, but more annoyingly, it would very consistently not un-encrypt messages both for me and the people I was talking to, requiring both parties to regularly need to re-send messages until they finally unencrypted properly. This made it a real ball-ache to use, as you could send a message, and then hours later have someone else say they can’t read it. I’m also not a fan of how much Metadata it spreads around.
XMPP on the other hand has always been snappy and fast, and I much prefer the clients available for it. It’s currently the most promising federated option, IMHO, with Movim being the most promising client as a Discord replacement.
It’s still missing some essential Discord-like features, such as groups of rooms in a server and drop-in voice rooms, but both features are being actively worked on, and a funding campaign was started to accelerate development.
But what it can do already is:
Excellent text chats, including with very good optional encryption
Group voice/video calls with screensharing (must use a chromium based browser to screenshare an app’s audio)
A neat integrated blogging feature for communities & individuals
a built-in paint program to draw stuff to input into the chat
Full working and proven federation thanks to the XMPP back-end
I found it to be slow at times, but more annoyingly,
Slow at what, exactly? If you mean slow at delivering messages, it suggests that you were using the world’s largest public server, which sometimes gets overloaded enough to be slow. In that case, your criticism is not of Matrix, but of a particular server. To compare apples to apples, you would have to either pick a different server or compare the largest one with a similarly loaded XMPP server.
it would very consistently not un-encrypt messages both for me and the people I was talking to,
When was that? Which clients were in use? This is relevant because unable-to-decrypt errors were fairly common until roughly mid-to-late last year. They put a lot of work into finding and addressing the causes, and I haven’t seen a single one in more than a few months. I suspect the experience you’re describing here is either out of date, or you’re using clients that haven’t applied the fixes yet.
I also notice from your recent Lemmy posts that you are evangelizing Movim pretty hard lately. There’s nothing inherently wrong with that, but praising XMPP without mentioning its drawbacks, while spreading outdated and vague criticism of other options, is a somewhat misleading way to do it… and a disservice to the community.
I’ve personally not had terribly good experiences with Matrix. I found it to be slow at times, but more annoyingly, it would very consistently not un-encrypt messages both for me and the people I was talking to, requiring both parties to regularly need to re-send messages until they finally unencrypted properly. This made it a real ball-ache to use, as you could send a message, and then hours later have someone else say they can’t read it. I’m also not a fan of how much Metadata it spreads around.
XMPP on the other hand has always been snappy and fast, and I much prefer the clients available for it. It’s currently the most promising federated option, IMHO, with Movim being the most promising client as a Discord replacement.
It’s still missing some essential Discord-like features, such as groups of rooms in a server and drop-in voice rooms, but both features are being actively worked on, and a funding campaign was started to accelerate development.
But what it can do already is:
Slow at what, exactly? If you mean slow at delivering messages, it suggests that you were using the world’s largest public server, which sometimes gets overloaded enough to be slow. In that case, your criticism is not of Matrix, but of a particular server. To compare apples to apples, you would have to either pick a different server or compare the largest one with a similarly loaded XMPP server.
When was that? Which clients were in use? This is relevant because unable-to-decrypt errors were fairly common until roughly mid-to-late last year. They put a lot of work into finding and addressing the causes, and I haven’t seen a single one in more than a few months. I suspect the experience you’re describing here is either out of date, or you’re using clients that haven’t applied the fixes yet.
I also notice from your recent Lemmy posts that you are evangelizing Movim pretty hard lately. There’s nothing inherently wrong with that, but praising XMPP without mentioning its drawbacks, while spreading outdated and vague criticism of other options, is a somewhat misleading way to do it… and a disservice to the community.