fix missing stuff from nip-29.

This commit is contained in:
fiatjaf
2026-01-19 09:39:55 -03:00
parent f34e98c73f
commit eb252ccfc4

18
29.md
View File

@@ -120,15 +120,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: 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 from `kind:39000` to be modified | | 9002 | `edit-metadata` | fields to be modified, and optionally `unrestricted`, `open`, `visible` `public` |
| 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` | | | 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. 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.