sorted by: new top controversial old
How come reddit user is growing in c/lemmyshitpost@lemmy.world
How come reddit user is growing in c/lemmyshitpost@lemmy.world
Matrix Metadata Problem: the server sees everything except your messages in c/matrix@lemmy.ml
You can't opt out of Apple's own keylogger in c/cybersecurity@sh.itjust.works
Matrix Metadata Problem: the server sees everything except your messages in c/matrix@lemmy.ml
Matrix Metadata Problem: the server sees everything except your messages in c/matrix@lemmy.ml
[–] [S] 1 point 2 days 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.

  • permalink
  • fedilink
  • source
  • parent
  • context
    • Matrix Metadata Problem: the server sees everything except your messages in c/foss@beehaw.org
    [–] [S] 1 point 2 days ago (1 child)

    These aren’t mutually exclusive trade-offs: Matrix could support communities while minimizing or encrypting metadata by default. There should be a protocol that doesn’t require device details and profile data to be exposed just to participate.

  • permalink
  • fedilink
  • source
  • parent
  • context
    • Matrix Metadata Problem: the server sees everything except your messages in c/matrix@lemmy.ml
    [–] [S] 3 points 2 days ago (4 children)

    Matrix can expose your device name and device details to other homeservers through federation. Profile information such as your avatar and bio can also be queried remotely. A client version is not a dedicated federation field, but it can leak through the device name. Signal at least has Sealed Sender, which hides the sender's identity from its own service in supported cases.

    This is about metadata, not centralisation, self-hosting, or phone-number registration. Those are separate issues, not trade-offs.

  • permalink
  • fedilink
  • source
  • parent
  • context
    • Matrix Metadata Problem: the server sees everything except your messages in c/matrix@lemmy.ml
    Matrix Metadata Problem: the server sees everything except your messages in c/matrix@lemmy.ml
    Matrix Metadata Problem: the server sees everything except your messages in c/matrix@lemmy.ml
    27
    Matrix Metadata Problem: the server sees everything except your messages (dfrws.org)
     

    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 all 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.

    15
    Matrix Metadata Problem: the server sees everything except your messages (dfrws.org)
    submitted 3 days ago* (last edited 2 days ago) by to c/matrix@lemmy.ml
    22 comments fedilink
     

    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.

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

    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 all 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.

    Rustdesk "This app tracks and reports your activity" in c/privacy@lemmy.ca
    view more: next ›