Remix.run Logo
Teever 3 hours ago

I gave up after I upgraded my server from a SQLite backend to a PostgreSQL one with their conversion script which introduced errors into my DB.

Maybe one day I'll dig into it and see if I can fix the DB by extracting whatever data in it that's causing the errors, but like, is it really worth it at this point?

What does running a matrix server get me in 2025?

Arathorn an hour ago | parent | next [-]

> What does running a matrix server get me in 2025?

Is there any other FOSS, self-hosted, decentralised platform with E2EE chat & E2EE group VoIP - i.e. the equivalent of Signal, but without depending on a centralised service?

From my pov (which is biased, as Matrix project lead), the downsides are:

* We still expose too much metadata to the server. Work is afoot to fix this, though - e.g. https://youtu.be/Q6NSmptZIS4?t=933 for encrypted state events.

* Synapse is still uses waaaaay too much database. I proposed a solution here: https://youtu.be/D5zAgVYBuGk?t=1852 but it needs to get properly implemented.

* Element's transition from the legacy apps to Element X has not been smooth, causing much of the gnashing of teeth in this thread (e.g. lack of interop between 1:1 voip and group-e2ee voip, or teething problems in the new apps).

* Post Quantum Encryption hasn't landed yet; it's been painful to get funding together for it.

lousken 2 hours ago | parent | prev [-]

Haven't been on the main matrix.org server for many years, but they used to have a lot of issues with latency - it wasn't really instant messaging but more like email. When I felt it was the worst, I decided on self hosting it. That improved things significantly - it started to behave like an instant msg platform. Now with OVH migration I am even able to scroll through hundreds of attachments super fast and everything feels snappy.

And I also know there is no online status on the main server. Other than that, no idea