- cross-posted to:
- foss@beehaw.org
- matrix@programming.dev
- cross-posted to:
- foss@beehaw.org
- matrix@programming.dev
Matrix Metadata Problem: the server sees everything except your messages
People pick Matrix because of end-to-end encryption. But E2EE only protects message content — everything around it is plaintext.
The server sees:
- Your ID, IP, client type and version, device you use
- Your presence, typing status, read receipts
- Which rooms you join and when you join/leave
- Who else is in those rooms → your entire social graph
- Room names, topics, avatars (all plaintext state)
- For every message: who sent it, which room, a millisecond timestamp, type, size
And federation copies most of that to every other server whose users are in the room. Your “social footprint” isn’t one copy — it’s as many as there are servers.


Kindly find me proof that the Matrix protocol explicitly sends a user client’s version and device details towards another server when engaging in federation.
Do note that Matrix and open protocols are federated, and requires some amount metadata to actually process+route stuff.
It’s already a problem that it sends the client’s version, device details, avatar, and bio at all. Those device details are transmitted during federation along with everything else.
https://spec.matrix.org/latest/server-server-api