@filippo the user experience of ad blockers is what I aspire to for shared/collective blocklists. vast majority of folks stick with defaults, but you can go as granular as you want. good transparency and UX for overrides. would also want flow for "reporting" to specific blocklist maintainers.
providers could do keyword filters, instance-level, etc, in addition to user-specific blocks
Conversation
Notices
-
Embed this notice
bryan newbold (bnewbold@social.coop)'s status on Saturday, 11-Feb-2023 08:08:59 JST bryan newbold -
Embed this notice
Filippo Valsorda :go: (filippo@abyssdomain.expert)'s status on Saturday, 11-Feb-2023 08:09:01 JST Filippo Valsorda :go: The more I think about it the less it makes sense that instance admins also have the role of curating an instance blocklist ("defederations") for all their users.
They clearly have the role of moderating local users, as they are the ones that get to suspend or ban users.
It's also nice to delegate the curation of a blocklist to someone, but why to the admin? And why without opt-outs?
Feels like tooling to subscribe to blocklists would put users more in control.
Jake Hildreth (acorn) :blacker_heart_outline: repeated this.
-
Embed this notice