Nostr Web Client

The goal is to moderal only the root items in the community. Inside of each of them, people can go crazy.

Why is that the goal? Why limit the moderation reach if that's the path we're taking to begin with?

Having an extra tag in kinds 34550 that says which kinds need approval and making replies include the a tag could allow for truly moderated communities.

Eventually it should be up to clients to take that into consideration or not.

And also since we don't to break the old model, clients like amethyst could introduce a switch to display/hide unapproved replies?

I am currently working on a client and I see this reduces the possibilities I have with moderated communities as it should preferably be interoperable with clients like Amethyst and Satellite.

Reply to this note

Please Login to reply.

Discussion

Vitor Pamplona 7mo ago

Mostly because nobody wanted to keep moderating each individual reply (huge amount of work) and having to filter replies to only show the moderated ones. Maybe we could have a separate NIP to make sure every single event that is a-tagged gets moderated.

hughh 7mo ago

It could also be a huge amount of work if there are a lot of root posts. And bots could take care of approving posts anyway. I don't know if a NIP-72 compatible client explored those possibilities yet, would definitely be great to see.

As for making this a separate NIP idk, i see it more like a completion or option of the NIP.