nip29: delete "unmanaged" groups.

1 files changed, 1 insertions, 17 deletions

diff --git a/29.md b/29.md
index 85f47ca..f39d4d8 100644
--- a/29.md
+++ b/29.md
@@ -48,14 +48,6 @@ The roles supported by the group as to having some special privilege assigned to
 
 Users with any roles that have any privilege can be considered _admins_ in a broad sense and be returned in the `kind:39001` event for a group.
 
-## Unmanaged groups
-
-Unmanaged groups are impromptu groups that can be used in any public relay unaware of NIP-29 specifics. They piggyback on relays' natural white/blacklists (or lack of) but aside from that are not actively managed and won't have any admins, group state or metadata events.
-
-In `unmanaged` groups, everybody is considered to be a member.
-
-Unmanaged groups can transition to managed groups, in that case the relay master key just has to publish moderation events setting the state of all groups and start enforcing the rules they choose to.
-
 ## Event definitions
 
 These are the events expected to be found in NIP-29 groups.
@@ -142,8 +134,6 @@ This event defines the metadata for the group -- basically how clients should di
 
 If the group is forked and hosted in multiple relays, there will be multiple versions of this event in each different relay and so on.
 
-When this event is not found, clients may still connect to the group, but treat it as having a different status, `unmanaged`,
-
 ```jsonc
 {
   "kind": 39000,
@@ -231,7 +221,7 @@ The process through which the relay decides what roles to support and how to han
 
 ### Checking your own membership in a group
 
-The latest of either `kind:9000` or `kind:9001` events present in a group should tell a user that they are currently members of the group or if they were removed. In case none of these exist the user is assumed to not be a member of the group -- unless the group is `unmanaged`, in which case the user is assumed to be a member.
+The latest of either `kind:9000` or `kind:9001` events present in a group should tell a user that they are currently members of the group or if they were removed. In case none of these exist the user is assumed to not be a member of the group.
 
 ### Adding yourself to a group
 
@@ -240,9 +230,3 @@ Anyone can send a `kind:9021` join request to a group. The relay may then genera
 ### Storing your list of groups
 
 A definition for `kind:10009` was included in [NIP-51](51.md) that allows clients to store the list of groups a user wants to remember being in.
-
-### Using `unmanaged` relays
-
-To prevent event leakage, when using `unmanaged` relays, clients should include the [NIP-70](70.md) `-` tag, as just the `previous` tag won't be checked by other `unmanaged` relays.
-
-Groups MAY be named without relay support by adding a `name` to the corresponding tag in a user's `kind 10009` group list.