Today I updated my Matrix server because of a fix to mitigate a signing-key compromise in Element Server Suite (ESS) by ignoring the affected key by default.
For my rooms, this means a migration, and after that everyone sees: "This room has been replaced and is no longer active."
The only quick, meaningful explanation of why this message is displayed is to be found here:
https://forum.torproject.org/t/tor-project-matrix-room-upgrades-coming-next-week/20536.
It's funny; the average user has no idea, everyone just clicking on it.
In effect, this also means old messages can't really be deleted anymore. That's only possible in the currently active room.
Also, if the room is private, users cannot migrate on their own. An admin must invite them one by one.
Manually, there is no script.
In general, I realized a few more things:
Communities are in the documentation but aren't used anymore; there are Spaces instead.
And Spaces don't have any (non-technical, user-facing) documentation on Matrix . org.
Rooms can't be migrated between Spaces and standalone rooms easily anyway.
(At least in Element, I couldn't figure it out, maybe it's client-dependent for now.)
Not to mention: the biggest hurdle is still identity (MXID) in Matrix, which is DNS-dependent. DNS is a scam, a chokepoint of rented addresses.
Resilient, DNSSEC provides nice protection against response tampering, but that's it.
@username:sub.domain.xyz. That's all. If the server where you create the account isn't hosted well, you're cooked the moment the identity is created.
Stolen, seized, or expired domains. Or just the fact that, along the DNS chain of command, there's usually a SPOF, with a single person holding the credentials.
This is something Nostr definitely handles better.
View quoted note โ