diff options
| author | fiatjaf <fiatjaf@gmail.com> | 2023-05-28 21:33:30 -0300 |
|---|---|---|
| committer | fiatjaf <fiatjaf@gmail.com> | 2024-02-23 20:51:46 -0300 |
| commit | 5084fe2e0867d0c06141ba0cb0a9b083dccc9d75 (patch) | |
| tree | c32cd9921ac3d766cdad146391ce6d51e7dd4b9e | |
| parent | d1f08d724c66efe9e16910935c64e5ac851eec8d (diff) | |
fix kind number for moderation event.
| -rw-r--r-- | 29.md | 2 |
1 files changed, 1 insertions, 1 deletions
| @@ -78,7 +78,7 @@ The list of capabilities, as defined by this NIP, for now, is the following: | |||
| 78 | } | 78 | } |
| 79 | ``` | 79 | ``` |
| 80 | 80 | ||
| 81 | - *moderation event* (`kind:39002`) (optional) | 81 | - *moderation event* (`kind:9000`) (optional) |
| 82 | 82 | ||
| 83 | An event sent from a client to the relay in order to accomplish a moderation action. The relay should read this event and act on it if the user sending the event has the required permissions and the date is close to the current date. The relay may discard the event after taking action or keep it as a way to expose a moderation log. This is similar to the `kind:9` event in its structure. | 83 | An event sent from a client to the relay in order to accomplish a moderation action. The relay should read this event and act on it if the user sending the event has the required permissions and the date is close to the current date. The relay may discard the event after taking action or keep it as a way to expose a moderation log. This is similar to the `kind:9` event in its structure. |
| 84 | 84 | ||