Synapse via ESS Community (https://element.io/server-suite/community), as it just works and is trivial to update, and tracks the best practices from Element in running a deployment with all the Matrix 2.0 stuff (sliding sync, OIDC auth, Element Call) enabled. The Helm charts are literally the same underlying codebase that powers ESS Pro for folks like NATO and the UN; the only difference is that ESS Community doesn't have the horizontal scaling and enterprise-privileging features that ESS Pro has.
The only gotcha is that Synapse is still not very resource efficient, especially for disk space, although work is finally under way to solve that.
(Meanwhile all our customer deployments run Synapse Pro + ESS Pro in order to get the scalability and Rust worker implementations in Syn Pro.)
remember when you agreed with me that it was maybe regretable that the Favorites space was removed in favor of a process that required multiple clicks? and now it's months later and Element still has this redesign shipped, with every single one of the original flaws mentioned, still present.
I think Matrix has a lot of smart people involved, and I can't believe I'm saying this, but dear god, are you hiring for a TPM, by chance?
Every, single, time I have to go "Home" -> "Expand" -> "Favorites" to do what used to take one click, I lose a bit more faith in Element/Matrix.
Though, y'all did finally fix the notification sound that made me want to kill myself every single time it violated my ear drums. Only took.... 4 years? for that?
What were meant to be fast-follow fixes to the new left panel after it shipped in September ended up getting starved out by deadlines for paying customers, frustratingly. The work is happening now however.
Matrix has a pretty comprehensive featureset with clients across a broad range of platforms.
The accusations of it being overengineered come typically due to the Synapse server implementation being slow. This is basically an artefact of Matrix being quite complicated to provide a byzantine fault tolerant decentralised equivalent to WhatsApp or Slack etc - and time has gone into fixing stability and usability rather than performance. Meanwhile performance is getting better, but progress is slow due to tragedy-of-the-commons related funding challenges. We will get there in the end, though.
Thanks for the response Matthew! But please go to sleep!
Yes it's unfortunate how much Synapse's unperformant implementation has decreased general confidence in the protocol itself. I'm confident it will get better
Synapse has improved; Dendrite has stagnated due to lack of funding; meanwhile there are also rust-native homeservers like Conduit which are beta but smaller footprint. The plan on the Element side is to keep optimising Synapse - the main win to be had is https://docs.google.com/presentation/d/1pKtLl4vCV3-8xz8crvxW...
I’m facing it on Element Desktop, but I’ll try to reproduce it on Element Web. I’ve tried to submit logs from Element Desktop, but it says that `/rageshake` (which I was told to do) is not a command. I’m happy to help with debugging this, but I’m not sure how to submit logs from Desktop.
Something like this happens basically every time I try to use Matrix though. Messages are not decrypting, or not being delivered, or devices can’t be authenticated for some cryptic reason. The reason I even tried to use Element Desktop is because my nheko is seemingly now incapable of sending direct messages (the recepient just gets infinite “waiting for message”).
Weird. Encryption these days (in Element Web/Desktop and Element X at least) should be pretty robust - although this whole identity reset thing is a known bug on Element Web/Desktop. You can submit debug logs from Settings: Help & About: Submit Debug Logs, and hopefully that might give a hint on what's going wrong.
At least a while ago Element X broke bridging in a pretty annoying way, since all chats with more than 2 members were classified as groups, even if they were marked as DMs.
The only gotcha is that Synapse is still not very resource efficient, especially for disk space, although work is finally under way to solve that.
(Meanwhile all our customer deployments run Synapse Pro + ESS Pro in order to get the scalability and Rust worker implementations in Syn Pro.)
reply