Thread-level content moderation

[ondra-novak]

One of the advantages of (for instance) Facebook, , or a moderated discussion under an article in an online magazine, is the ability of the author to moderate the discussion. This feature allows him to keep the discussion on topic, factual and limits the possibility of hate speech, abuse and troll feeding. As the author of the original post, I feel responsible for the content of the discussion. Because inadequate discussion can degenerate to the damage of the author's original intent. Therefore, I propose to add a new event type to NOSTR that would allow such moderation.

• The event should have a new kind.
• The event should refer the original post
• The event should refer any other event (a note), - in most of cases, the note which directly or indirectly refers the original post.
• The event should specify type of moderation.

The client can discover this event when it loads reactions in order to display the thread (all reactions). Based on this event, the client should adjust the way the entire thread is displayed. The client should only respect this event if it is from the same author as the original post, or if the author is the current user (who views the posts)

If the author is the same as the original post, this event is effective for all clients (and users). Otherwise, only the author of this event is affected.

Types of moderations

• answered - allows to mark a note as an answer to a question written in the original post. This note should be somehow highlighted and displayed as a first. The referenced event doesn't need to refer directly or indirectly to the original post
• up - similar as answered but only moves note up in the thread, also allows to show the note even if it is not referring to the original post (like a repost, but prevent double displaying of the post in the thread - original and repost)
• hide - hides the note. The post will not appear in the thread, however clients should offer the option to display hidden posts at the end of the discussion, as Twitter does. In this case, the hidden post should refer directly to the original post. It is possible to allow a post to be hidden if it refers to the original post indirectly, for example, if it is in a deeper level of the thread, but clients needn't always respect this, for example, if a user is viewing a sub-thread without seeing the original post

If necessary, I can write this as a new NIP. Unfortunately I am not a client developer, so I cannot implement a reference implementation, so I would like such a feature to be pushed by a client developer

[staab]

I think this could be solved more simply by adding a general-purpose "moderation" event (maybe even using NIP 32). Anyone can make one, and clients can interpret them how they want. If the author of an event "moderates" a reply, clients can pay attention to that or not. This way, users can subscribe to moderation for a trusted set of pubkey, people on a given list, etc. Specifying this so it's consistent across clients is probably needed though. I am planning to work on this in September at any rate.

[xeruf]

sounds sensible, yes - so moderation and users individually "reporting"/blocking posts can essentially be unified