Good, as it should for normal people as well
post
Absolutely everybody here is sleeping on zulip.
Honestly, federated FOSS makes so much sense for government communication, as it insulates them from reliance on corporate entities.
I just wish Matrix’s E2EE worked better. Even if you have all your keys managed properly, it’s still really unreliable.
I just wish Matrix’s E2EE worked better.
For "real-time communication" for individuals who don't want to maintain their own communication infrastructure, the information around https://www.privacyguides.org/en/real-time-communication/ is surely at least somewhat useful. The recommendations might not be suitable for "government communication" or for people who are capable of setting up and maintaining a lot of infrastructure since I wouldn't describe the infrastructure required as being easy to host independently: it doesn't seem to be easy to set up 3 servers and make it possible to use them to communicate even if something bad happens to the communication network maintained by the original creators of the software. However, the Matrix protocol might be unsuitable for this too, since it is considered to be "social networking software" now, and it stopped being a recommendation for encrypted real-time communication: https://www.privacyguides.org/en/social-networks/#element
hope this leads to money going towards Element open source development. it works but it's not great right now
It's worrying to see that it's Matrix that's gaining ground in IT, when IT people more than anyone else should know that XMPP is the better alternative, Matrix is a bloated nu-protocol in comparison.
XMPP is not better than Matrix. My major gripes with it are OMEMO and the clients that implement different subsets of the extensions.
OMEMO still is an extension instead of the core. It should be extremely easy to upgrade a chat to an encrypted one but if the client doesn't have a plugin installed to support it, you're stuck with unencrypted traffic.
And the clients I've tested have all been visually unappealing and lacking in features. Reacting to messages, quoting messages, using threads, encryption, and finding rooms has been difficult or impossible with them.
Matrix has a major advantage over XMPP in that it has an official, reference client which implements just about everything. It works better than most any XMPP client I've tried and, this is my feeling, every MSC accepted by the foundation has actually been implemented, instead of just being suggested and"left as an exercise to the developer".
Matrix didn't come out of nowhere and didn't supplant XMPP for no reason. XMPP simply doesn't have the ecosystem that makes it attractive to users and debs alike.
Why do you need Cloudflare for Matrix?
You don’t. But you don’t get to make that decision for everyone you talk to. People /erroneously/ think they do, so it has become impossible to participate in a public discussion without Cloudflare in the loop.
FOSDEM 2026 demonstrates this embarrassment. Every single FOSDEM talk this year has a link to matrix.to (Cloudflare). Even if your own account is CF-independent, the rest of the crowd who you correspond with is not. You cannot isolate yourself from Cloudflare and also participate in FOSDEM rooms. That’s not ETS.
i don't see the connection here. it's not about Matrix.
This was about self-hosted instances, for the most part.
Cloudflare is not a host. It’s a reverse proxy and governments use it.
Ah, strictly internal, I read the post text wrong.
If you require something that couldn't be used over CloudFlare, that cedes a whole lot of power to what they choose to support, though. It's kind of a weird bar to place; any networking could, in theory, be run by proxy.
If you require something that couldn’t be used over CloudFlare, that cedes a whole lot of power to what they choose to support
Power is excessively unreasonably ceded when Cloudflare is in the loop. To avoid CF is to put power back where it belongs. Cloudflare-incompatible tech ensures CF does not wield inappropriate power.
any networking could, in theory, be run by proxy.
Indeed, and this frustrates sigsec. Connecting to someone requires trusting them not to do something stupid like hand their keys to a giant centralised corporate overlord. At least avoiding Cloudflare is low-hanging fruit. It’s usually easy to detect when CF is in the loop, apart from a few rare shenanigans where CF uses some IPs that are not in CF’s ASN records.
yikes! Not smart for “chasing digital sovereignty”.
1 comment