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

Define unmanaged based on supported_nips

Browse Source
This commit is contained in:
Jon Staab 2024-12-12 15:46:19 -08:00
parent 157fe36b98
commit e67f0a39be
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
29.md
View File

@ -54,7 +54,7 @@ Users with any roles that have any privilege can be considered _admins_ in a bro
If a group doesn't have a kind `39000` metadata event, it is considered `unmanaged`. Events posted to `unmanaged` group MUST NOT be handled by relays in any special way. If a group doesn't have a kind `39000` metadata event, it is considered `unmanaged`. Events posted to `unmanaged` group MUST NOT be handled by relays in any special way.
Relays that do not allow `unmanaged` groups MUST set `nip29.unmanaged` to `false` in their NIP 11 document. In this mode, events sent to non-existent groups MUST be rejected by the relay. Relays that do not allow `unmanaged` groups MUST NOT include `29` in their NIP 11 document's `supported_nips` field. In this mode, events sent to non-existent groups MUST be rejected by the relay.
## Event definitions ## Event definitions