diff options
| author | ok300 <106775972+ok300@users.noreply.github.com> | 2022-12-29 11:40:58 +0100 |
|---|---|---|
| committer | fiatjaf <fiatjaf@gmail.com> | 2022-12-29 11:00:55 -0300 |
| commit | 570bc59e7dc1bf35ff8298b1c3d56ae2423f7613 (patch) | |
| tree | 786a7d29b9401ddb3505b88322e8fd8754344068 /10.md | |
| parent | c5d21351587f89e6d0c9a217310c4319c505175d (diff) | |
Update e-tag type for direct reply
Diffstat (limited to '10.md')
| -rw-r--r-- | 10.md | 2 |
1 files changed, 1 insertions, 1 deletions
| @@ -48,7 +48,7 @@ Where: | |||
| 48 | 48 | ||
| 49 | **The order of marked "e" tags is not relevant.** Those marked with `"reply"` denote the `<reply-id>`. Those marked with `"root"` denote the root id of the reply thread. | 49 | **The order of marked "e" tags is not relevant.** Those marked with `"reply"` denote the `<reply-id>`. Those marked with `"root"` denote the root id of the reply thread. |
| 50 | 50 | ||
| 51 | A direct reply to the root of a thread should have a single marked "e" tag of type "reply". | 51 | A direct reply to the root of a thread should have a single marked "e" tag of type "root". |
| 52 | 52 | ||
| 53 | >This scheme is preferred because it allows events to mention others without confusing them with `<reply-id>` or `<root-id>`. | 53 | >This scheme is preferred because it allows events to mention others without confusing them with `<reply-id>` or `<root-id>`. |
| 54 | 54 | ||