nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-22 08:25:53 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

remove references to nip 56 in nip 32

Browse Source
This commit is contained in:
Jonathan Staab 2023-05-27 09:03:48 -07:00
parent 057d097e74
commit 114302517f
1 changed files with 0 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
32.md
View File

@ -12,11 +12,6 @@ A label is a `kind 1985` event that is used to label other entities. This suppor
- Reviews and ratings - Reviews and ratings
- Definition of edges in a graph structure - Definition of edges in a graph structure
This NIP does not supersede NIP-56, which supports reporting content for the purpose of
direct moderation, in order to comply with laws or app store requirements. "Moderation"
as defined by this NIP is only relative to user preferences and should be interpreted
with the social graph in view to provide a better user experience.
Label Target Label Target
---- ----
@ -66,23 +61,6 @@ explanation of why something was labeled the way it was, should go in the event'
Example events Example events
-------------- --------------
A report that an event contains nudity. Note that NIP 56 is preferred for reporting content
to clients, while labels are recommended for supporting distributed content moderation use
cases.
```json
{
"kind": 1985,
"tags": [
["L", "report"],
["l", "nudity", "report"],
["e", <id>, <relay_url>]
],
"content": "",
...
}
```
A single event can apply multiple labels to multiple targets to support mass-tagging. Multiple A single event can apply multiple labels to multiple targets to support mass-tagging. Multiple
namespaces may be used at the same time. namespaces may be used at the same time.