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

Define l-tag on Text Events #1474

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

Define l-tag on Text Events #1474

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
14 changes: 12 additions & 2 deletions 10.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,8 +2,8 @@ NIP-10
======


On "e" and "p" tags in Text Events (kind 1).
--------------------------------------------
On "e", "p" and "l" tags in Text Events (kind 1).
-------------------------------------------------

`draft` `optional`

Expand Down Expand Up @@ -62,3 +62,13 @@ When replying to a text event E the reply event's "p" tags should contain all of

Example: Given a text event authored by `a1` with "p" tags [`p1`, `p2`, `p3`] then the "p" tags of the reply should be [`a1`, `p1`, `p2`, `p3`]
in no particular order.

## The "l" tag

Text events MUST indicate the level in their respective thread. The root event
MUST use ["l", "0"], replies to an l-0 event MUST use ["l", "1"] etc.

As this tag was not defined from day one, clients should not assume 100%
adoption and use it when querying for root events `…,kinds:[1],"#l":["0"]` or
immediate replies `…,kinds:[1],"e":[<event-id>],"#l":["3"]` only once broad
adoption was achieved.