From 114302517fa5b4ea499c5725f8a6aab675c36e24 Mon Sep 17 00:00:00 2001 From: Jonathan Staab Date: Sat, 27 May 2023 09:03:48 -0700 Subject: [PATCH] remove references to nip 56 in nip 32 --- 32.md | 22 ---------------------- 1 file changed, 22 deletions(-) diff --git a/32.md b/32.md index dd2f50ca..1939555c 100644 --- a/32.md +++ b/32.md @@ -12,11 +12,6 @@ A label is a `kind 1985` event that is used to label other entities. This suppor - Reviews and ratings - 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 ---- @@ -66,23 +61,6 @@ explanation of why something was labeled the way it was, should go in the event' 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", , ] - ], - "content": "", - ... -} -``` - A single event can apply multiple labels to multiple targets to support mass-tagging. Multiple namespaces may be used at the same time.