Skip to content

Update NIP-10 including definitions for "a" tags #809

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

Closed
franzaps wants to merge 2 commits into from
Closed

Update NIP-10 including definitions for "a" tags #809

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0bcaf41
Include definitions for a tags
franzaps Oct 9, 2023
20b1118
Update subtitle
franzaps Oct 9, 2023
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
10 changes: 5 additions & 5 deletions 10.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,13 +2,13 @@ NIP-10
======


On "e" and "p" tags in Text Events (kind 1).
On "e", "a" and "p" tags in Text Events (kind 1).
--------------------------------------------
Comment thread
franzaps marked this conversation as resolved.

`draft` `optional` `author:unclebobmartin`

## Abstract
This NIP describes how to use "e" and "p" tags in text events, especially those that are replies to other text events. It helps clients thread the replies into a tree rooted at the original event.
This NIP describes how to use "e", "a" and "p" tags in text events, especially those that are replies to other text events. It helps clients thread the replies into a tree rooted at the original event.

## Positional "e" tags (DEPRECATED)
>This scheme is in common use; but should be considered deprecated.
Expand Down Expand Up @@ -37,8 +37,8 @@ They are citings from this event. `root-id` and `reply-id` are as above.

>This scheme is deprecated because it creates ambiguities that are difficult, or impossible to resolve when an event references another but is not a reply.

## Marked "e" tags (PREFERRED)
`["e", <event-id>, <relay-url>, <marker>]`
## Marked "e" and "a" tags (PREFERRED)
`["e", <event-id>, <relay-url>, <marker>]` (or `["a", <event-id>, <relay-url>, <marker>]` for replaceable events)

Where:

Expand All @@ -48,7 +48,7 @@ Where:

Those marked with `"reply"` denote the id of the reply event being responded to. Those marked with `"root"` denote the root id of the reply thread being responded to. For top level replies (those replying directly to the root event), only the `"root"` marker should be used. Those marked with `"mention"` denote a quoted or reposted event id.

A direct reply to the root of a thread should have a single marked "e" tag of type "root".
A direct reply to the root of a thread should have a single marked `"e"` tag (or `"a"` tag if it is a replaceable event) of type `"root"`.

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

Expand Down