diff --git a/29.md b/29.md index f39d4d81..9d20ef2e 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 | -| --- | --- | --- | -| 9000 | `put-user` | `p` with pubkey hex and optional roles | -| 9001 | `remove-user` | `p` with pubkey hex | -| 9002 | `edit-metadata` | fields to be modified, and optionally `unrestricted`, `open`, `visible` `public` | -| 9005 | `delete-event` | `e` with event id hex | -| 9007 | `create-group` | | -| 9008 | `delete-group` | | -| 9009 | `create-invite` | arbitrary `code` | +| kind | name | tags | +| --- | --- | --- | +| 9000 | `put-user` | `p` with pubkey hex and optional roles | +| 9001 | `remove-user` | `p` with pubkey hex | +| 9002 | `edit-metadata` | all the fields of *group-metadata* | +| 9005 | `delete-event` | `e` with event id hex | +| 9007 | `create-group` | | +| 9008 | `delete-group` | | +| 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.