nip29: match flotilla style "edit-metadata" (PUT, not PATCH).

because hodlbod controls nostr
author: fiatjaf <fiatjaf@gmail.com> 2026-03-30 08:58:57 -0300
committer: fiatjaf <fiatjaf@gmail.com> 2026-04-22 11:59:32 -0300
commit: 6735a229bcf0a75bf32f3e4f429ecd7675929356 (patch)
tree: 9c54da33f298763c08d3d08cc6a8df78af60e383
parent: 0a25dd524389d642ec153d9009a16fb183eb23ce (diff)
1 files changed, 9 insertions, 9 deletions
diff --git a/29.md b/29.md
index f39d4d8..9d20ef2 100644
--- a/29.md
+++ b/29.md
@@ -112,15 +112,15 @@ Clients can send these events to a relay in order to accomplish a moderation act
 Each moderation action uses a different kind and requires different arguments, which are given as tags. These are defined in the following table:
-| kind | name            | tags                                                                             |
+| kind | name            | tags                                   |
-| ---  | ---             | ---                                                                              |
+| ---  | ---             | ---                                    |
-| 9000 | `put-user`      | `p` with pubkey hex and optional roles                                           |
+| 9000 | `put-user`      | `p` with pubkey hex and optional roles |
-| 9001 | `remove-user`   | `p` with pubkey hex                                                              |
+| 9001 | `remove-user`   | `p` with pubkey hex                    |
-| 9002 | `edit-metadata` | fields to be modified, and optionally `unrestricted`, `open`, `visible` `public` |
+| 9002 | `edit-metadata` | all the fields of *group-metadata*     |
-| 9005 | `delete-event`  | `e` with event id hex                                                            |
+| 9005 | `delete-event`  | `e` with event id hex                  |
-| 9007 | `create-group`  |                                                                                  |
+| 9007 | `create-group`  |                                        |
-| 9008 | `delete-group`  |                                                                                  |
+| 9008 | `delete-group`  |                                        |
-| 9009 | `create-invite` | arbitrary `code`                                                                 |
+| 9009 | `create-invite` | arbitrary `code`                       |
 It's expected that the group state (of who is an allowed member or not, who is an admin and with which permission or not, what are the group name and picture etc) can be fully reconstructed from the canonical sequence of these events.
author	fiatjaf <fiatjaf@gmail.com>	2026-03-30 08:58:57 -0300
committer	fiatjaf <fiatjaf@gmail.com>	2026-04-22 11:59:32 -0300
commit	6735a229bcf0a75bf32f3e4f429ecd7675929356 (patch)
tree	9c54da33f298763c08d3d08cc6a8df78af60e383
parent	0a25dd524389d642ec153d9009a16fb183eb23ce (diff)

diff --git a/29.md b/29.md index f39d4d8..9d20ef2 100644 --- a/29.md +++ b/29.md
@@ -112,15 +112,15 @@ Clients can send these events to a relay in order to accomplish a moderation act
112		112
113	Each moderation action uses a different kind and requires different arguments, which are given as tags. These are defined in the following table:	113	Each moderation action uses a different kind and requires different arguments, which are given as tags. These are defined in the following table:
114		114
115	\| kind \| name \| tags \|	115	\| kind \| name \| tags \|
116	\| --- \| --- \| --- \|	116	\| --- \| --- \| --- \|
117	\| 9000 \| `put-user` \| `p` with pubkey hex and optional roles \|	117	\| 9000 \| `put-user` \| `p` with pubkey hex and optional roles \|
118	\| 9001 \| `remove-user` \| `p` with pubkey hex \|	118	\| 9001 \| `remove-user` \| `p` with pubkey hex \|
119	\| 9002 \| `edit-metadata` \| fields to be modified, and optionally `unrestricted`, `open`, `visible` `public` \|	119	\| 9002 \| `edit-metadata` \| all the fields of group-metadata \|
120	\| 9005 \| `delete-event` \| `e` with event id hex \|	120	\| 9005 \| `delete-event` \| `e` with event id hex \|
121	\| 9007 \| `create-group` \| \|	121	\| 9007 \| `create-group` \| \|
122	\| 9008 \| `delete-group` \| \|	122	\| 9008 \| `delete-group` \| \|
123	\| 9009 \| `create-invite` \| arbitrary `code` \|	123	\| 9009 \| `create-invite` \| arbitrary `code` \|
124		124
125	It's expected that the group state (of who is an allowed member or not, who is an admin and with which permission or not, what are the group name and picture etc) can be fully reconstructed from the canonical sequence of these events.	125	It's expected that the group state (of who is an allowed member or not, who is an admin and with which permission or not, what are the group name and picture etc) can be fully reconstructed from the canonical sequence of these events.
126		126