OTOH, this means the source code of Mastodon contains explicit instructions not to list individual blocks when they are also instance blocks. This was by choice, even if the Hanlon razor would have us view it as a non intentional oversight.
Conversation
Notices
-
Embed this notice
Albert ARIBAUD ✎ (aaribaud@mastodon.art)'s status on Sunday, 15-Sep-2024 01:07:21 JST Albert ARIBAUD ✎ -
Embed this notice
Albert ARIBAUD ✎ (aaribaud@mastodon.art)'s status on Sunday, 15-Sep-2024 16:35:53 JST Albert ARIBAUD ✎ @RnDanger @mindpersephone @welshpixie I agree that offerrng to individually unblock an instance-blocked user would not make sense, but at least that user should be listed, possibly with a note replacing the unblock button.
-
Embed this notice
2xfo (rndanger@infosec.exchange)'s status on Sunday, 15-Sep-2024 16:35:54 JST 2xfo @aaribaud @mindpersephone @welshpixie
I think it makes sense not to show the option to unblock users that are blocked at the instance level since they can't really be "unblocked", at least in theory. I can see how that could be represented better though.
But it doesn't make sense to me that server-blocked users could see and interact with your stuff unless you have specifically blocked them as a user.
-
Embed this notice