The cloudflare concerns aren’t an issue as long as you run your own instance, or join one that doesn’t use cloudflare. There’s nothing requiring cloudflare built into the software or the protocol.
Yeah, but the vast majority of non-technical users don't bother to change homeservers, or even clients, so it could affect them. What puzzles me is why the Matrix/Element team chose Cloudflare for app.element.io, (matrix.org uses LetsEncrypt), when CF aims to centralize the web and is a privacy nightmare. It's more of an ethics thing, in my opinon. But sure, like I mentioned too, could be solved by switching homeservers/clients but the vast majority of users won't bother.
poVoq@lemmy.ml 2 years ago
The problem is not mainly the leaking metadata, but that the Matrix protocol is designed to indefinitely store and freely share this metadata with every home-server joining (which even gets a full copy of everything retro-actively). XMPP does not do this.
dessalines@lemmy.ml 2 years ago
How does xmpp not store information about federated users joining a room?
poVoq@lemmy.ml 2 years ago
XMPP only does this on the single server the room resides on and does not share this info with other participating servers except for the bare minimum needed to show the user's nick names.
I recommend you hosting your own Matrix home server and after joining a few rooms look at your database what kind of historical metadata ends up on your new server. It's honestly appalling from a privacy point of view.
Yes this is needed for room persistence across multiple servers, but IMHO that is a solution looking for a problem and IMHO also a highly over-engineered one.
Ferk@lemmy.ml 2 years ago
There's ongoing work to encrypt the metadata too. https://github.com/matrix-org/matrix-doc/pull/3414
Without this solution the transition to p2p would be much more complicated, would it not?