upleb.uk

Public git repos — served from a NIP-34 GRASP relay at git.upleb.uk

summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--29.md25
-rw-r--r--README.md1
2 files changed, 10 insertions, 16 deletions
diff --git a/29.md b/29.md
index b83d2db..0f4a579 100644
--- a/29.md
+++ b/29.md
@@ -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
57This is the basic unit of a "microblog" reply note sent to a group. 57This 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
70Replies 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
77Similar to `kind:11`, this is the basic unit of a chat message sent to a group. 64This 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
78Similar 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
91Any 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. 84Any 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.
diff --git a/README.md b/README.md
index 0ee6039..3aa330d 100644
--- a/README.md
+++ b/README.md
@@ -94,6 +94,7 @@ They exist to document what may be implemented by [Nostr](https://github.com/nos
94| `7` | Reaction | [25](25.md) | 94| `7` | Reaction | [25](25.md) |
95| `8` | Badge Award | [58](58.md) | 95| `8` | Badge Award | [58](58.md) |
96| `9` | Group Chat Message | [29](29.md) | 96| `9` | Group Chat Message | [29](29.md) |
97| `10` | Group Chat Threaded Reply | [29](29.md) |
97| `11` | Group Thread | [29](29.md) | 98| `11` | Group Thread | [29](29.md) |
98| `12` | Group Thread Reply | [29](29.md) | 99| `12` | Group Thread Reply | [29](29.md) |
99| `13` | Seal | [59](59.md) | 100| `13` | Seal | [59](59.md) |