Add labeling to nip 56 as well

This commit is contained in:
Jonathan Staab 2023-06-07 16:09:26 -07:00
parent 363d112e33
commit 92ce49dda0
2 changed files with 13 additions and 6 deletions

4
36.md
View File

@ -9,7 +9,7 @@ Sensitive Content / Content Warning
The `content-warning` tag enables users to specify if the event's content needs to be approved by readers to be shown.
Clients can hide the content until the user acts on it.
`l` and `L` tags MAY be also be used as defined in [NIP-32](32.md) with the `content-warning` namespace to support
`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
further qualification and querying.
#### Spec
@ -31,6 +31,8 @@ options:
["t", "hastag"],
["L", "content-warning"],
["l", "reason", "content-warning"],
["L", "social.nos.ontology"],
["l", "NS-nud", "social.nos.ontology"],
["content-warning", "reason"] /* reason is optional */
],
"content": "sensitive content with #hastag\n",

5
56.md
View File

@ -32,6 +32,9 @@ being reported, which consists of the following report types:
Some report tags only make sense for profile reports, such as `impersonation`
`l` and `L` tags MAY be also be used as defined in [NIP-32](32.md) to support
further qualification and querying.
Example events
--------------
@ -40,6 +43,8 @@ Example events
"kind": 1984,
"tags": [
["p", <pubkey>, "nudity"]
["L", "social.nos.ontology"],
["l", "NS-nud", "social.nos.ontology"],
],
"content": "",
...