Nicholas Conrad on Nostr: Per-community moderation is not ideal. It creates much duplicate work, and lends ...

Per-community moderation is not ideal. It creates much duplicate work, and lends itself to moderation via cutting off entire nodes that are less restrictive than your community. It also enforces one-size-fits-all within communities. I appreciate BS' subscription-based moderation approach, and I wish something like that was available per-server and per-user. I want to be able to subscribe to a trusted group identifying csam and hard-reject that at the server level, then apply server-level defaults via feeds that users can disable per-feed if desired, and let users select additional feeds if desired. While this may sound "per-community", the difference is that the subscription approach means the work of actually doing the moderation only has to happen once, amd then each community can choose to take advantage of it (or not). For BS, where they go wrong is having an overarching moderation subscription that no one is allowed to opt out of that will always be subject to abuse and manipulation.