Matrix

3974 readers

47 users here now

An open network for secure, decentralized communication

founded 6 years ago

MODERATORS

k_o_t@lemmy.ml

Matrix Metadata Problem: the server sees everything except your messages (dfrws.org)

submitted 1 day ago* (last edited 5 hours ago) by verifytheposter@leminal.space to c/matrix@lemmy.ml

19 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] verifytheposter@leminal.space 1 points 5 hours ago

device_display_name is optional in the federation response. Current Synapse omits it by default, but it can still be sent when explicitly enabled. Older Synapse versions also exposed it through some federation paths.

I believe you are saying that my statement, “Federation copies all of that,” is incorrect. I agree. I should have said, “Federation copies most of that.”

However, the main concern remains: a homeserver can still collect the client type and version, the device being used, room names, topics, avatars, and other metadata. Much of this information is not necessary for delivering end-to-end encrypted messages, and its collection is concerning in itself.