edit-group-status permission.

29.md

@@ -107,6 +107,7 @@ Each moderation action uses a different kind and requires different arguments, w
 | 9003 | `add-permission`    | `p` (pubkey), `permission` (name)     |
 | 9004 | `remove-permission` | `p` (pubkey), `permission` (name)     |
 | 9005 | `delete-event`      | `e` (id hex)                          |
+| 9006 | `edit-group-status` | `public`, `open`, `private`, `closed` |
 
 - *group metadata* (`kind:39000`) (optional)
 
@@ -123,14 +124,14 @@ If the group is forked and hosted in multiple relays, there will be multiple ver
     ["name", "Pizza Lovers"],
     ["picture", "https://pizza.com/pizza.png"],
     ["about", "a group for people who love pizza"],
-    ["public"],
-    ["open"]
+    ["public"], // or ["private"]
+    ["open"] // or ["closed"]
   ]
   ...
 }
 ```
 
-`name`, `picture` and `about` are basic metadata for the group for display purposes. `public` signals the group can be _read_ by anyone. `open` signals that anyone can request to join and the request will be automatically granted.
+`name`, `picture` and `about` are basic metadata for the group for display purposes. `public` signals the group can be _read_ by anyone, while `private` signals that only AUTHed users can read. `open` signals that anyone can request to join and the request will be automatically granted, while `closed` signals that members must be pre-approved or that requests to join will be manually handled.
 
 The [NIP-19](19.md) `naddr` pointer for this event including with a mandatory relay can be used as the canonical group identifier.
 
@@ -148,6 +149,7 @@ The list of capabilities, as defined by this NIP, for now, is the following:
 - `remove-user`
 - `add-permission`
 - `remove-permission`
+- `edit-group-status`
 
 ```js
 {