Comment by lukev
7 days ago
I haven't looked at how Threadsky does it, and I don't want to weigh in on the merits of different approaches.
But blocking in ATProto happens at the application (AppView) layer. A different application can absolutely make different choices from the Bluesky app about how blocking works and is displayed.
Presumably you still need server code to prevent blocked users from interacting with each other, no?
If I block you, then my client will prevent me from seeing your records.
There's nothing at the protocol level that prevents you from seeing my records, even when blocked, because all records are public. Anyone (even without an account) can see everyone else's records.
Well behaved clients are guided not to show posts to a blocked user, but this is a developer norm to enhance user experience all around -- seeing posts from someone who blocked you generally doesn't do anyone any good. But the protocol fully lets you build a client that shows you exactly who has blocked you and what they're posting.
Right, but there's more to blocking than content filtering (which is more akin to muting in twitter nomenclature). It should also restrict the blocked person from interacting with my content. At least that's what I'd expect (and I suspect most would).