5 ms·

I'm of the same stance. I've been using Matrix for 3 years now, primarily to communicate with family located where there is high censorship and most messengers

by _lvbh 1y ago

I'm of the same stance. I've been using Matrix for 3 years now, primarily to communicate with family located where there is high censorship and most messengers are blocked. Probably due to the complexity of the system and inherent design, performance is horrible. Good enough for usage but just unpleasant. Their new Element X client is meant to solve a lot of problems but they're starting to deviate from common standards (e.g. TURN/STUN for calling) and towards "Element Call" and livekit which are a nightmare to set up. There's been more and more encryption problems lately where I'd sync the keys but still fail to decrypt messages on certain clients and lose history on others. I'm sticking with the old Element client but it's obvious the Vector people aren't putting much effort into it anymore seeing as there are very old but critical bugs (main one being the fact that it automatically reaches out to matrix.org when trying to sign in with other homeservers and freezes if the domain is blocked. This is fixed by Element X.) I can fix it myself but until IOS allows sideloading, I have no way of getting my fork onto my family's devices. If anyone knows an alternative that has web, IOS, and Android clients, easily self hostable, and can do calling, please let me know.

methuselah_in 1y ago
You can try monal xmpp. It's working great for my contacts. There are multiple servers that you can self host. On android you have better part is conversations. My entire family uses it.
freeopinion 1y ago
Aside from your valid concerns about Element roadmaps, you highlight a completely different really crummy problem. You have chosen (or have had chosen for you) the support of a closed platform that puts you in a pickle. The dev team for an app of interest to you doesn't seem to have the bandwidth to address all your concerns as quickly as would be super. But they have taken the hit to get their code into the walled garden where you can use it. You have the bandwidth to tackle some of your wishlist, but don't have access into the walled garden. So what might be a negotiation between two parties--you and the app dev team--is now complicated by a thorny third party--your os platform team. Presumably you derive some value in other areas from your walled garden that offsets the penalty it introduces in this case. But it's still crummy that you're caught in this snag created by your os platform.
- mattnewton 1y ago
  I think this misses that GP is using this to communicate with other people who use these platforms. It’s been chosen for them by their friends and family.
Arathorn 1y ago
It’s depressing to hear that you’ve given up on Element X, given that’s where all the work has been going, including ensuring the encryption is rock solid. Element Call is still webrtc; the fact it’s direct calling to a SFU rather than needing TURN for firewall traversal should be a good thing. How did you try to set it up? I did a basic walk through at https://github.com/element-hq/element-docker-demo https://github.com/element-hq/element-docker-demo in case that helps.
- AAAAaccountAAAA 1y ago
  It's depressing to see and hear that New Vector is rewriting the flagship client about every 5 years or so, with each rewrite taking multiple years. Each time the new client is hailed as the saviour, and then after a while, denounced as obsolete. Soon again, the new saviour is right around the corner. That is not the way you create high-quality software in a cost-efficient manner. While Matrix has a value as the pretty much only open-standard IM system with even moderate levels of user adoption, all this makes it hard to actually love it or even to be enthustiastic about it.
  - Arathorn 1y ago
    The only problem with this statement is that it’s untrue. Element Web/Desktop is 11 years old and has never been rewritten, and while we’re just starting to experiment with the Rust SDK for it, it’s unclear yet whether we migrate the current app to Rust SDK or write an Element X Web. Element iOS is also 11 years old, and as fun and expensive as it was maintaining three entirely separate codebases between iOS/Android/Web, we only switched to Rust with Element X as of Sept, and have no plans to switch again. Now, it’s true that Riot Android did get rewritten in ~2019 (into RiotX, which became Element Android) - mainly because it needed to get a proper storage layer and to move from Android 2.x vintage UI code. Now we have a common rust SDK to do all the heavy lifting it is reasonable to switch the app to use it, which is what Element X Android is. In other words, this whole exercise is trying to simplify development on to one stable Rust codebase, rather than hunting bugs and reimplementing features over 3 entirely separate codebases. If we did it again perhaps we’d try for a replace-the-engine like Signal did rather than rewrite-the-app - or perhaps do a big bang replacement when the rewrite is ready. But instead we wanted to get the new apps in the hands of users earlier, and we do not remotely have the funding to develop both old and new in parallel. Hopefully history will show this was an okay approach in the end, even if everyone hates us in the final stages of the transition.
ezst 1y ago
> primarily to communicate with family located where there is high censorship and most messengers are blocked I was travelling frequently through Asia and the Middle East around a decade ago. I wanted a platform that just works, that is low on resources, that I can self-host, that I can "disguise" itself as something else when needed (run behind a different port, or IP, over ToR, etc). Matrix was new then, and promising to right every wrong from previous protocols (mild exaggeration). I bought into the hype, and got burnt by it, finally settled with XMPP (which Matrix had told me wasn't adequate), and stayed there to this day because when Matrix really didn't go anywhere since, XMPP kept getting better and better. That would be my recommendation to you.

by _lvbh 1y ago

methuselah_in 1y ago

You can try monal xmpp. It's working great for my contacts. There are multiple servers that you can self host. On android you have better part is conversations. My entire family uses it.

freeopinion 1y ago

Aside from your valid concerns about Element roadmaps, you highlight a completely different really crummy problem. You have chosen (or have had chosen for you) the support of a closed platform that puts you in a pickle. The dev team for an app of interest to you doesn't seem to have the bandwidth to address all your concerns as quickly as would be super. But they have taken the hit to get their code into the walled garden where you can use it. You have the bandwidth to tackle some of your wishlist, but don't have access into the walled garden. So what might be a negotiation between two parties--you and the app dev team--is now complicated by a thorny third party--your os platform team. Presumably you derive some value in other areas from your walled garden that offsets the penalty it introduces in this case. But it's still crummy that you're caught in this snag created by your os platform.

mattnewton 1y ago
I think this misses that GP is using this to communicate with other people who use these platforms. It’s been chosen for them by their friends and family.

Arathorn 1y ago

It’s depressing to hear that you’ve given up on Element X, given that’s where all the work has been going, including ensuring the encryption is rock solid. Element Call is still webrtc; the fact it’s direct calling to a SFU rather than needing TURN for firewall traversal should be a good thing. How did you try to set it up? I did a basic walk through at https://github.com/element-hq/element-docker-demo https://github.com/element-hq/element-docker-demo in case that helps.

AAAAaccountAAAA 1y ago
It's depressing to see and hear that New Vector is rewriting the flagship client about every 5 years or so, with each rewrite taking multiple years. Each time the new client is hailed as the saviour, and then after a while, denounced as obsolete. Soon again, the new saviour is right around the corner. That is not the way you create high-quality software in a cost-efficient manner. While Matrix has a value as the pretty much only open-standard IM system with even moderate levels of user adoption, all this makes it hard to actually love it or even to be enthustiastic about it.
- Arathorn 1y ago
  The only problem with this statement is that it’s untrue. Element Web/Desktop is 11 years old and has never been rewritten, and while we’re just starting to experiment with the Rust SDK for it, it’s unclear yet whether we migrate the current app to Rust SDK or write an Element X Web. Element iOS is also 11 years old, and as fun and expensive as it was maintaining three entirely separate codebases between iOS/Android/Web, we only switched to Rust with Element X as of Sept, and have no plans to switch again. Now, it’s true that Riot Android did get rewritten in ~2019 (into RiotX, which became Element Android) - mainly because it needed to get a proper storage layer and to move from Android 2.x vintage UI code. Now we have a common rust SDK to do all the heavy lifting it is reasonable to switch the app to use it, which is what Element X Android is. In other words, this whole exercise is trying to simplify development on to one stable Rust codebase, rather than hunting bugs and reimplementing features over 3 entirely separate codebases. If we did it again perhaps we’d try for a replace-the-engine like Signal did rather than rewrite-the-app - or perhaps do a big bang replacement when the rewrite is ready. But instead we wanted to get the new apps in the hands of users earlier, and we do not remotely have the funding to develop both old and new in parallel. Hopefully history will show this was an okay approach in the end, even if everyone hates us in the final stages of the transition.

ezst 1y ago

> primarily to communicate with family located where there is high censorship and most messengers are blocked I was travelling frequently through Asia and the Middle East around a decade ago. I wanted a platform that just works, that is low on resources, that I can self-host, that I can "disguise" itself as something else when needed (run behind a different port, or IP, over ToR, etc). Matrix was new then, and promising to right every wrong from previous protocols (mild exaggeration). I bought into the hype, and got burnt by it, finally settled with XMPP (which Matrix had told me wasn't adequate), and stayed there to this day because when Matrix really didn't go anywhere since, XMPP kept getting better and better. That would be my recommendation to you.