diff options
| author | fiatjaf <fiatjaf@gmail.com> | 2024-02-26 14:54:08 -0300 |
|---|---|---|
| committer | fiatjaf <fiatjaf@gmail.com> | 2024-02-26 14:54:48 -0300 |
| commit | e976d2f32d65e6f1d29f21c081a0c1f945c831ac (patch) | |
| tree | 7165a0b39ace0dd06e3191285b877e8a7af9cb12 /29.md | |
| parent | 188f398c8636631bd8f1ac2a31cfc42b7d85e18d (diff) | |
add kind:10 threaded chat replies.simple-chat-groups
Diffstat (limited to '29.md')
| -rw-r--r-- | 29.md | 25 |
1 files changed, 9 insertions, 16 deletions
| @@ -52,29 +52,16 @@ This is the basic unit of a "microblog" root text note sent to a group. | |||
| 52 | ... | 52 | ... |
| 53 | ``` | 53 | ``` |
| 54 | 54 | ||
| 55 | - *text reply note* (`kind:12`) | 55 | - *threaded text reply* (`kind:12`) |
| 56 | 56 | ||
| 57 | This is the basic unit of a "microblog" reply note sent to a group. | 57 | This is the basic unit of a "microblog" reply note sent to a group. It's the same as `kind:11`, except for the fact that it must be used whenever it's in reply to some other note (either in reply to a `kind:11` or a `kind:12`). `kind:12` events SHOULD use NIP-10 markers, leaving an empty relay url: |
| 58 | |||
| 59 | ```js | ||
| 60 | "kind": 12, | ||
| 61 | "content": "pizza is disgusting and you should be ashamed", | ||
| 62 | "tags": [ | ||
| 63 | ["h", "<group-id>"], | ||
| 64 | ["e", "<reply-event-id>", "", "root"], | ||
| 65 | ["previous", "<event-id-first-chars>", "<event-id-first-chars>", ...] | ||
| 66 | ] | ||
| 67 | ... | ||
| 68 | ``` | ||
| 69 | |||
| 70 | Replies SHOULD use NIP-10 markers, leaving an empty relay url: | ||
| 71 | 58 | ||
| 72 | * `["e", "<kind-11-root-id>", "", "root"]` | 59 | * `["e", "<kind-11-root-id>", "", "root"]` |
| 73 | * `["e", "<kind-12-event-id>", "", "reply"]` | 60 | * `["e", "<kind-12-event-id>", "", "reply"]` |
| 74 | 61 | ||
| 75 | - *chat message* (`kind:9`) | 62 | - *chat message* (`kind:9`) |
| 76 | 63 | ||
| 77 | Similar to `kind:11`, this is the basic unit of a chat message sent to a group. | 64 | This is the basic unit of a _chat message_ sent to a group. |
| 78 | 65 | ||
| 79 | ```js | 66 | ```js |
| 80 | "kind": 9, | 67 | "kind": 9, |
| @@ -86,6 +73,12 @@ Similar to `kind:11`, this is the basic unit of a chat message sent to a group. | |||
| 86 | ... | 73 | ... |
| 87 | ``` | 74 | ``` |
| 88 | 75 | ||
| 76 | - *chat message threaded reply* (`kind:10`) | ||
| 77 | |||
| 78 | Similar to `kind:12`, this is the basic unit of a chat message sent to a group. This is intended for in-chat threads that may be hidden by default. Not all in-chat replies MUST use `kind:10`, only when the intention is to create a hidden thread that isn't part of the normal flow of the chat (although clients are free to display those by default too). | ||
| 79 | |||
| 80 | `kind:10` SHOULD use NIP-10 markers, just like `kind:12`. | ||
| 81 | |||
| 89 | - *join request* (`kind:9021`) | 82 | - *join request* (`kind:9021`) |
| 90 | 83 | ||
| 91 | Any user can send one of these events to the relay in order to be automatically or manually added to the group. If the group is `open` the relay will automatically issue a `kind:9000` in response adding this user. Otherwise group admins may choose to query for these requests and act upon them. | 84 | Any user can send one of these events to the relay in order to be automatically or manually added to the group. If the group is `open` the relay will automatically issue a `kind:9000` in response adding this user. Otherwise group admins may choose to query for these requests and act upon them. |