Can’t force anything but clients could implement that in the presence of a block list that you are on.
Discussion
But a user could always open a browser and sidestep any block list, so I wonder if App Store policies would take this into account. I mean, it’s not really different than Twitter blocking. Anyone can easily spin up a new account and follow someone who blocked them.
I’ve always found muting to be a more appealing tool on twitter than blocking. 99.9% of my blocklist is just bots.
Yeah Twitter blocking is sort of a lie as you can just log out and see everything. I think the most important actions are follow and mute. Both on accounts and keywords/phrases.
It was all a lie :O
No but for real, the most important part is being able to personally customize your feed algorithm. Things, like a word block list and account mute, have their place. Relays & clients will experiment :)
The block is to not see their messages. It’s not a two way block like on Twitter. Think of client side more like muting or ignoring.
Actual blocking (to prevent an offending user from publishing events) would have to be done on the relay level.
Relays could store user’s blocks. Not a problem.
Can Damus add a semicolon or something innocuous to the code so that it stays in TestFlight until approval?