upleb.uk

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

summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJonathan Staab <shtaab@gmail.com>2023-06-07 16:09:26 -0700
committerJonathan Staab <shtaab@gmail.com>2023-06-13 09:31:15 -0700
commit92ce49dda0acce1f661868316a9858521d4bc974 (patch)
tree9a43b715e1940796e84deac491de90d72d4f1c12
parent363d112e335c13f4fa1c113e2418db1102c58ed5 (diff)
Add labeling to nip 56 as well
-rw-r--r--36.md4
-rw-r--r--56.md15
2 files changed, 13 insertions, 6 deletions
diff --git a/36.md b/36.md
index 379d40a..6d1cf63 100644
--- a/36.md
+++ b/36.md
@@ -9,7 +9,7 @@ Sensitive Content / Content Warning
9The `content-warning` tag enables users to specify if the event's content needs to be approved by readers to be shown. 9The `content-warning` tag enables users to specify if the event's content needs to be approved by readers to be shown.
10Clients can hide the content until the user acts on it. 10Clients can hide the content until the user acts on it.
11 11
12`l` and `L` tags MAY be also be used as defined in [NIP-32](32.md) with the `content-warning` namespace to support 12`l` and `L` tags MAY be also be used as defined in [NIP-32](32.md) with the `content-warning` or other namespace to support
13further qualification and querying. 13further qualification and querying.
14 14
15#### Spec 15#### Spec
@@ -31,6 +31,8 @@ options:
31 ["t", "hastag"], 31 ["t", "hastag"],
32 ["L", "content-warning"], 32 ["L", "content-warning"],
33 ["l", "reason", "content-warning"], 33 ["l", "reason", "content-warning"],
34 ["L", "social.nos.ontology"],
35 ["l", "NS-nud", "social.nos.ontology"],
34 ["content-warning", "reason"] /* reason is optional */ 36 ["content-warning", "reason"] /* reason is optional */
35 ], 37 ],
36 "content": "sensitive content with #hastag\n", 38 "content": "sensitive content with #hastag\n",
diff --git a/56.md b/56.md
index 55ee1a2..42174fb 100644
--- a/56.md
+++ b/56.md
@@ -32,6 +32,9 @@ being reported, which consists of the following report types:
32 32
33Some report tags only make sense for profile reports, such as `impersonation` 33Some report tags only make sense for profile reports, such as `impersonation`
34 34
35`l` and `L` tags MAY be also be used as defined in [NIP-32](32.md) to support
36further qualification and querying.
37
35Example events 38Example events
36-------------- 39--------------
37 40
@@ -39,7 +42,9 @@ Example events
39{ 42{
40 "kind": 1984, 43 "kind": 1984,
41 "tags": [ 44 "tags": [
42 [ "p", <pubkey>, "nudity"] 45 ["p", <pubkey>, "nudity"]
46 ["L", "social.nos.ontology"],
47 ["l", "NS-nud", "social.nos.ontology"],
43 ], 48 ],
44 "content": "", 49 "content": "",
45 ... 50 ...
@@ -48,8 +53,8 @@ Example events
48{ 53{
49 "kind": 1984, 54 "kind": 1984,
50 "tags": [ 55 "tags": [
51 [ "e", <eventId>, "illegal"], 56 ["e", <eventId>, "illegal"],
52 [ "p", <pubkey>] 57 ["p", <pubkey>]
53 ], 58 ],
54 "content": "He's insulting the king!", 59 "content": "He's insulting the king!",
55 ... 60 ...
@@ -58,8 +63,8 @@ Example events
58{ 63{
59 "kind": 1984, 64 "kind": 1984,
60 "tags": [ 65 "tags": [
61 [ "p", <impersonator pubkey>, "impersonation"], 66 ["p", <impersonator pubkey>, "impersonation"],
62 [ "p", <victim pubkey>] 67 ["p", <victim pubkey>]
63 ], 68 ],
64 "content": "Profile is imitating #[1]", 69 "content": "Profile is imitating #[1]",
65 ... 70 ...