nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-09-19 22:35:50 -04:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge pull request #1129 from coracle-social/relax-nip32

Browse Source 
relax requirements for NIP 32 L tags
This commit is contained in:
Alex Gleason 2024-06-07 11:37:04 -05:00 committed by GitHub
commit a7ed4e805f
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
32.md
View File

@ -20,7 +20,7 @@ Label Namespace Tag
An `L` tag can be any string, but publishers SHOULD ensure they are unambiguous by using a well-defined namespace An `L` tag can be any string, but publishers SHOULD ensure they are unambiguous by using a well-defined namespace
(such as an ISO standard) or reverse domain name notation. (such as an ISO standard) or reverse domain name notation.
`L` tags are REQUIRED in order to support searching by namespace rather than by a specific tag. The special `ugc` `L` tags are RECOMMENDED in order to support searching by namespace rather than by a specific tag. The special `ugc`
("user generated content") namespace MAY be used when the label content is provided by an end user. ("user generated content") namespace MAY be used when the label content is provided by an end user.
`L` tags starting with `#` indicate that the label target should be associated with the label's value. `L` tags starting with `#` indicate that the label target should be associated with the label's value.
@ -29,7 +29,9 @@ This is a way of attaching standard nostr tags to events, pubkeys, relays, urls,
Label Tag Label Tag
---- ----
An `l` tag's value can be any string. `l` tags MUST include a `mark` matching an `L` tag value in the same event. An `l` tag's value can be any string. If using an `L` tag, `l` tags MUST include a mark matching an `L`
tag value in the same event. If no `L` tag is included, a mark SHOULD still be included. If none is
included, `ugc` is implied.
Label Target Label Target
---- ----
@ -42,7 +44,7 @@ or topics respectively. As with NIP-01, a relay hint SHOULD be included when usi
Content Content
------- -------
Labels should be short, meaningful strings. Longer discussions, such as for a review, or an Labels should be short, meaningful strings. Longer discussions, such as for an
explanation of why something was labeled the way it was, should go in the event's `content` field. explanation of why something was labeled the way it was, should go in the event's `content` field.
Self-Reporting Self-Reporting