From e67f0a39be07cda86ec552d2c92221d56293bd17 Mon Sep 17 00:00:00 2001 From: Jon Staab Date: Thu, 12 Dec 2024 15:46:19 -0800 Subject: [PATCH] Define unmanaged based on supported_nips --- 29.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/29.md b/29.md index 7cdbfa3..ce17973 100644 --- a/29.md +++ b/29.md @@ -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. -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