Open evanp opened 5 months ago
I'd like to explicitly exclude this user story, at least for things like addressing, timestamps, or inReplyTo
. Routing, in particular, gets really hard if servers don't know the identities of addressees.
well, it depends what the client hands to the server. if, as you describe in the models document, client is encrypting the message and handing an encrypted payload and routing info to the server, a single group chat message might be decomposed into multiple individual messages, in which case the group message metadata could be encrypted, and only individual messages and their [partial] metadata handed to servers, no? kind of a "least privilege" kind of metadata leakage 😅
"As an ActivityPub user, I want metadata of my DMs to be encrypted also, so that no one can tell who I was messaging, when, or what the relationship between messages is."