diff options
| author | monlovesmango <96307647+monlovesmango@users.noreply.github.com> | 2022-11-27 16:02:38 -0600 |
|---|---|---|
| committer | fiatjaf <fiatjaf@gmail.com> | 2023-01-15 09:18:15 -0300 |
| commit | 5355edb9cb1c712bcc8c024416b1e2e25a32317a (patch) | |
| tree | a5621459bc1c6cbad37bde062b20067b97445a18 | |
| parent | 0019a206a351fcdb7429b829d08024fd4f565f02 (diff) | |
add 'mention' marker
I think that adding a mention marker would eliminate ambiguity for clients supporting both the deprecated and preferred conventions. I also think that this would allow for extensibility in adding new types of event mentions (for example if we want to add context for a note).
| -rw-r--r-- | 10.md | 4 |
1 files changed, 2 insertions, 2 deletions
| @@ -44,9 +44,9 @@ Where: | |||
| 44 | 44 | ||
| 45 | * `<event-id>` is the id of the event being referenced. | 45 | * `<event-id>` is the id of the event being referenced. |
| 46 | * `<relay-url>` is the URL of a recommended relay associated with the reference. It is NOT optional. | 46 | * `<relay-url>` is the URL of a recommended relay associated with the reference. It is NOT optional. |
| 47 | * `<marker>` is optional and if present is one of `"reply"` or `"root"` | 47 | * `<marker>` is optional and if present is one of `"reply"`, `"root"`, or `"mention"` |
| 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. Those marked `"mention"` denote id of events that are tagged and are not the `"reply"` nor `"root"`. |
| 50 | 50 | ||
| 51 | A direct reply to the root of a thread should have a single marked "e" tag of type "root". | 51 | A direct reply to the root of a thread should have a single marked "e" tag of type "root". |
| 52 | 52 | ||