Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update NIP-10: add 'mention' marker #80

Merged
merged 3 commits into from
Jan 15, 2023
Merged

Update NIP-10: add 'mention' marker #80

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
5733d3b
add 'mention' marker
monlovesmango Nov 27, 2022
bdaf4c9
define 'mention' tag
monlovesmango Nov 29, 2022
43f1dfe
clarify top level reply behavior
monlovesmango Dec 5, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions 10.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,9 +44,9 @@ Where:

* `<event-id>` is the id of the event being referenced.
* `<relay-url>` is the URL of a recommended relay associated with the reference. It is NOT optional.
* `<marker>` is optional and if present is one of `"reply"` or `"root"`
* `<marker>` is optional and if present is one of `"reply"`, `"root"`, or `"mention"`

**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.
**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"`.

>This scheme is preferred because it allows events to mention others without confusing them with `<reply-id>` or `<root-id>`.

Expand Down