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 also notice from your recent Lemmy posts that you are evangelizing Movim pretty hard lately.
I am, mainly due to the Discord situation which has resulted in much more interest in alternative platforms. After everything dies down and everyone is settled in their new platform, I’ll likely be posting about it a bit less.
but praising XMPP without mentioning its drawbacks
I am mentioning its drawbacks; it does not have two very important Discord features as of now, which I explicitly point out. I also pointed out that screen sharing audio only works with Chromium browsers, which is another downside (I only use Firefox myself).
while spreading outdated and vague criticism of other options
You yourself said that the issues I had were only fixed a few months ago. I had been using it in the period you mention the problem existing in, but stopped using it due to those issues. I think it’s a little unreasonable to expect me to regularly re-try every other platform before relating my past experiences with it (a few months is not that long ago). I’m glad to hear that problem has been finally resolved for them. As it’s not relevant anymore, I won’t mention it when relaying my experience with it in the future.
You yourself said that the issues I had were only fixed a few months ago.
No, I said I haven’t seen a single one of those errors in more than a few months. I haven’t been tracking the timeline, but I’m pretty sure the fixes were being put in place closer to a year ago.
I think it’s a little unreasonable to expect me to regularly re-try every other platform before relating my past experiences with it
When we choose to publish old experiences instead of gathering updated information first, it’s important to also state when those experiences were, so readers can take it into account. Things are constantly changing in this field. (Mostly for the better, I think.)
In any case, thanks for clarifying, and thanks in advance for adjusting your spiel now that you’ve been made aware that your information was out of date.
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.
I am, mainly due to the Discord situation which has resulted in much more interest in alternative platforms. After everything dies down and everyone is settled in their new platform, I’ll likely be posting about it a bit less.
I am mentioning its drawbacks; it does not have two very important Discord features as of now, which I explicitly point out. I also pointed out that screen sharing audio only works with Chromium browsers, which is another downside (I only use Firefox myself).
You yourself said that the issues I had were only fixed a few months ago. I had been using it in the period you mention the problem existing in, but stopped using it due to those issues. I think it’s a little unreasonable to expect me to regularly re-try every other platform before relating my past experiences with it (a few months is not that long ago). I’m glad to hear that problem has been finally resolved for them. As it’s not relevant anymore, I won’t mention it when relaying my experience with it in the future.
No, I said I haven’t seen a single one of those errors in more than a few months. I haven’t been tracking the timeline, but I’m pretty sure the fixes were being put in place closer to a year ago.
When we choose to publish old experiences instead of gathering updated information first, it’s important to also state when those experiences were, so readers can take it into account. Things are constantly changing in this field. (Mostly for the better, I think.)
In any case, thanks for clarifying, and thanks in advance for adjusting your spiel now that you’ve been made aware that your information was out of date.