Open evanp opened 3 months ago
I think this might be a metadata issue. The ActivityPub server should have access to the sender address in order to do blocking on the server side. It's also a big issue for activity pub for validating activities that we can tell where the activity is supposed to come from and who the actor is supposed to be. I don't think an algorithm that hides the actor identity or encrypt that part of the meta-data would work for activity pub.
However, if such messages were deliverable, somehow, it's possible for the client to maintain its own Blocklist, and use that when hiding the unsolicited messages.
why? can't you just filter blocks client-side?
"As an ActivityPub user, I can block an encrypted DM from someone I don’t know, so I don’t get unsolicited messages."