diff options
| author | William Casarin <jb55@jb55.com> | 2023-02-07 13:15:38 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-02-07 18:15:38 -0300 |
| commit | f9e38ed00f5b11694ff93c368aacbf47ec21437a (patch) | |
| tree | bc68c9caafa0902d69cfdf366616c6d089172644 /56.md | |
| parent | b99ca748c8227d2723b5f856b004267b3c122c06 (diff) | |
NIP-56: Reporting (#205)
Co-authored-by: Semisol <45574030+Semisol@users.noreply.github.com>
Co-authored-by: Leo Wandersleb <leo@leowandersleb.de>
Diffstat (limited to '56.md')
| -rw-r--r-- | 56.md | 82 |
1 files changed, 82 insertions, 0 deletions
| @@ -0,0 +1,82 @@ | |||
| 1 | |||
| 2 | NIP-56 | ||
| 3 | ====== | ||
| 4 | |||
| 5 | Reporting | ||
| 6 | --------- | ||
| 7 | |||
| 8 | `draft` `optional` `author:jb55` | ||
| 9 | |||
| 10 | A report is a `kind 1984` note that is used to report other notes for spam, | ||
| 11 | illegal and explicit content. | ||
| 12 | |||
| 13 | The content MAY contain additional information submitted by the entity | ||
| 14 | reporting the content. | ||
| 15 | |||
| 16 | Tags | ||
| 17 | ---- | ||
| 18 | |||
| 19 | The report event MUST include a `p` tag referencing the pubkey of the user you | ||
| 20 | are reporting. | ||
| 21 | |||
| 22 | If reporting a note, an `e` tag MUST also be included referencing the note id. | ||
| 23 | |||
| 24 | A `report type` string MUST be included as the 3rd entry to the `e` or `p` tag | ||
| 25 | being reported, which consists of the following report types: | ||
| 26 | |||
| 27 | - `nudity` - depictions of nudity, porn, etc. | ||
| 28 | - `profanity` - profanity, hateful speech, etc. | ||
| 29 | - `illegal` - something which may be illegal in some jurisdiction | ||
| 30 | - `spam` - spam | ||
| 31 | - `impersonation` - someone pretending to be someone else | ||
| 32 | |||
| 33 | Some report tags only make sense for profile reports, such as `impersonation` | ||
| 34 | |||
| 35 | Example events | ||
| 36 | -------------- | ||
| 37 | |||
| 38 | ```json | ||
| 39 | { | ||
| 40 | "kind": 1984, | ||
| 41 | "tags": [ | ||
| 42 | [ "p", <pubkey>, "nudity"] | ||
| 43 | ], | ||
| 44 | "content": "", | ||
| 45 | ... | ||
| 46 | } | ||
| 47 | |||
| 48 | { | ||
| 49 | "kind": 1984, | ||
| 50 | "tags": [ | ||
| 51 | [ "e", <eventId>, "illegal"], | ||
| 52 | [ "p", <pubkey>] | ||
| 53 | ], | ||
| 54 | "content": "He's insulting the king!", | ||
| 55 | ... | ||
| 56 | } | ||
| 57 | |||
| 58 | { | ||
| 59 | "kind": 1984, | ||
| 60 | "tags": [ | ||
| 61 | [ "p", <impersonator pubkey>, "impersonation"], | ||
| 62 | [ "p", <victim pubkey>] | ||
| 63 | ], | ||
| 64 | "content": "Profile is imitating #[1]", | ||
| 65 | ... | ||
| 66 | } | ||
| 67 | ``` | ||
| 68 | |||
| 69 | Client behavior | ||
| 70 | --------------- | ||
| 71 | |||
| 72 | Clients can use reports from friends to make moderation decisions if they | ||
| 73 | choose to. For instance, if 3+ of your friends report a profile as explicit, | ||
| 74 | clients can have an option to automatically blur photos from said account. | ||
| 75 | |||
| 76 | |||
| 77 | Relay behavior | ||
| 78 | -------------- | ||
| 79 | |||
| 80 | It is not recommended that relays perform automatic moderation using reports, | ||
| 81 | as they can be easily gamed. Admins could use reports from trusted moderators to | ||
| 82 | takedown illegal or explicit content if the relay does not allow such things. | ||