Mika on Nostr: Moderation in #Fediverse currently works this way (as far as I can tell): - Instances ...
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.
- 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.