upleb.uk

Public git repos — served from a NIP-34 GRASP relay at git.upleb.uk

summaryrefslogtreecommitdiff
path: root/56.md
diff options
context:
space:
mode:
authorfiatjaf_ <fiatjaf@gmail.com>2025-01-30 23:21:21 -0300
committerGitHub <noreply@github.com>2025-01-30 23:21:21 -0300
commit14d38014850930129e831b7ace25a9653e5d7095 (patch)
treef0944fb005c9b700c0b199a0c02cf936d416c92d /56.md
parent5eb515ceb97bdf0aa1570fb97ac510cd795bcf5a (diff)
parentf440eac3dccefa5c0ec9d3964e1d08357fd31e09 (diff)
Merge branch 'master' into video-events-regularvideo-events-regular
Diffstat (limited to '56.md')
-rw-r--r--56.md27
1 files changed, 21 insertions, 6 deletions
diff --git a/56.md b/56.md
index f7b1b1a..dc6f098 100644
--- a/56.md
+++ b/56.md
@@ -22,7 +22,7 @@ are reporting.
22 22
23If reporting a note, an `e` tag MUST also be included referencing the note id. 23If reporting a note, an `e` tag MUST also be included referencing the note id.
24 24
25A `report type` string MUST be included as the 3rd entry to the `e` or `p` tag 25A `report type` string MUST be included as the 3rd entry to the `e`, `p` or `x` tag
26being reported, which consists of the following report types: 26being reported, which consists of the following report types:
27 27
28- `nudity` - depictions of nudity, porn, etc. 28- `nudity` - depictions of nudity, porn, etc.
@@ -33,7 +33,9 @@ being reported, which consists of the following report types:
33- `impersonation` - someone pretending to be someone else 33- `impersonation` - someone pretending to be someone else
34- `other` - for reports that don't fit in the above categories 34- `other` - for reports that don't fit in the above categories
35 35
36Some report tags only make sense for profile reports, such as `impersonation` 36Some report tags only make sense for profile reports, such as `impersonation`.
37
38- `x` tags SHOULD be info hash of a blob which is intended to be report. when the `x` tag is represented client MUST include an `e` tag which is the id of the event that contains the mentioned blob. also, additionally these events can contain a `server` tag to point to media servers which may contain the mentioned media.
37 39
38`l` and `L` tags MAY be also be used as defined in [NIP-32](32.md) to support 40`l` and `L` tags MAY be also be used as defined in [NIP-32](32.md) to support
39further qualification and querying. 41further qualification and querying.
@@ -45,7 +47,7 @@ Example events
45{ 47{
46 "kind": 1984, 48 "kind": 1984,
47 "tags": [ 49 "tags": [
48 ["p", <pubkey>, "nudity"], 50 ["p", "<pubkey>", "nudity"],
49 ["L", "social.nos.ontology"], 51 ["L", "social.nos.ontology"],
50 ["l", "NS-nud", "social.nos.ontology"] 52 ["l", "NS-nud", "social.nos.ontology"]
51 ], 53 ],
@@ -58,8 +60,8 @@ Example events
58{ 60{
59 "kind": 1984, 61 "kind": 1984,
60 "tags": [ 62 "tags": [
61 ["e", <eventId>, "illegal"], 63 ["e", "<eventId>", "illegal"],
62 ["p", <pubkey>] 64 ["p", "<pubkey>"]
63 ], 65 ],
64 "content": "He's insulting the king!", 66 "content": "He's insulting the king!",
65 // other fields... 67 // other fields...
@@ -70,13 +72,26 @@ Example events
70{ 72{
71 "kind": 1984, 73 "kind": 1984,
72 "tags": [ 74 "tags": [
73 ["p", <impersonator pubkey>, "impersonation"] 75 ["p", "<impersonator pubkey>", "impersonation"]
74 ], 76 ],
75 "content": "Profile is impersonating nostr:<victim bech32 pubkey>", 77 "content": "Profile is impersonating nostr:<victim bech32 pubkey>",
76 // other fields... 78 // other fields...
77} 79}
78``` 80```
79 81
82```jsonc
83{
84 "kind": 1984,
85 "tags": [
86 ["x", "<blob hash>", "malware"],
87 ["e", "<event id which contains the blob on x tag>", "malware"],
88 ["server", "https://you-may-find-the-blob-here.com/path-to-url.ext"]
89 ],
90 "content": "This file contains malware software in it.",
91 // other fields...
92}
93```
94
80Client behavior 95Client behavior
81--------------- 96---------------
82 97