Conversation

Notices

1. Embed this notice
   Mika (irfan@sakurajima.social)'s status on Sunday, 05-May-2024 17:11:02 JST Mika

   Moderation in #Fediverse currently works this way (as far as I can tell):
   
   - Instances could enforce their instance block and mute list. This gets passed down to all members of their instance.
   
   - Users could have their own block and mute list of users or instances. This only applies for them, on top of the home instance's list.
   
   This works great for the most part, but previously there have been plenty of discussions/arguments of instance members perhaps not agreeing to certain blocks/mutes enforced by instance maintainers - in cases such as this, since individual members have no power to "override" these rules for their account (i.e. to federate with users of another instance that's been blocked by their instance maintainer), their only choice as the last resort is for them to move to another instance.
   
   I imagine it'd be great if it works this way instead:
   
   - Instances could enforce their instance block and mute list. This gets passed down to all members of their instance by default.
   
   - Users could have their own block and mute list of users or instances. This only applies for them, on top of the home instance's list.
   
   - However users could also override the home instance's list granularly, if they would want to for example, federate with an instance that's been blocked by their home instance.
   
   As someone who's not really delved into the workings of the Fediverse/#ActivityPub or any of the projects using it all too much, this "feature" suggestion might totally be technically nonsensical or maybe expensive though for it to make sense or be possible to achieve. Just thought this might be an improvement for what I think is already an excellent moderation system that we have here.

   • Embed this notice
     Mika (irfan@sakurajima.social)'s status on Sunday, 05-May-2024 17:29:30 JST Mika

     • BeAware :fediverse:

     @BeAware@social.beaware.live if users being able to override an instance block/mute for their account alone will disrupt these enforcements/moderation for everyone else on the instance (so not really for their accounts alone), which I guess is possible, then it's certainly not what I would want.
     
     The "best" scenario I'm looking for is that for instance maintainers to still enforce blocks/mutes for all of their members, but with the only difference being users could perhaps granularly add exceptions to what is blocked/muted for them (not others). So for example if their instance blocks/mutes federation with Threads/Meta, but they alone would want to still federate with Threads/Meta.
     
     As of right now, users could only add to the block/mute list for themselves, not override or add exceptions to what's enforced by their instance.

   • Embed this notice
     Mika (irfan@sakurajima.social)'s status on Sunday, 05-May-2024 17:34:54 JST Mika

     • BeAware :fediverse:

     @BeAware@social.beaware.live yes I totally agree. The priority for me is still for instance-level blocks and mutes + user-level blocks and mutes to work reliably. This suggestion would be premature to look into or worked on if said priority hasn't even "matured" just yet.