From 39c7f54db6af511361a4622744edaa84f90d5914 Mon Sep 17 00:00:00 2001 From: "Robert C. Martin" Date: Wed, 4 May 2022 12:00:51 -0500 Subject: [PATCH 1/4] mend --- e-and-p-tags.md | 33 +++++++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) create mode 100644 e-and-p-tags.md diff --git a/e-and-p-tags.md b/e-and-p-tags.md new file mode 100644 index 00000000..16fdbef6 --- /dev/null +++ b/e-and-p-tags.md @@ -0,0 +1,33 @@ +# On 'e' and 'p' tags in Text Events (kind 1). +### A recommendation for clients. + +The following seems to be the conventions that are used by `Branle`, `Damus`, and `more-speech` for referencing +events and authors when building a reply. These conventions help clients build event threads, and alert authors of +replies. + +## Definitions: + * A reply chain is the list of events from the root event to a specific reply. + * A reply thread is the tree of events consisting of all replies beginning at the root. + * An event id is a 32 byte number in lower-case hexidecimal. + +## The 'e' tag +Used in a text event contains a single event id. ["e", "~hex number~"] + + * No 'e' tag: +This event is not a reply to, nor does it refer to, any other event. + + * One 'e' tag: ["e",id]: +The id of the event to which this event is a reply. + + * Two 'e' tags: ["e",root-id], ["e",reply-id] +'root-id' is the id of the event at the root of the reply chain. 'reply-id' is the id of the article to which this event is a reply. + + * Many 'e' tags: ["e",root-id] ["e",mention-id], ..., ["e",reply-id] +There may be any number of 'mention-ids'. These are the ids of events which may, or may not be in the reply chain. They are citings from this event. 'root-id' and 'reply-id' are as above. + +## The 'p' tag +Used in a text event contains a list of pubkeys used to record who is involved in a reply thread. + +When replying to a text event E with 'p' tags P, the replying event's 'p' tags should contain P as well as the pubkey of the of the event being replied to. + +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. From 99c5425c42d700d27642e75b9361664e823dace4 Mon Sep 17 00:00:00 2001 From: "Robert C. Martin" Date: Wed, 4 May 2022 12:08:19 -0500 Subject: [PATCH 2/4] improve formatting --- e-and-p-tags.md | 26 ++++++++++++++------------ 1 file changed, 14 insertions(+), 12 deletions(-) diff --git a/e-and-p-tags.md b/e-and-p-tags.md index 16fdbef6..447f9f85 100644 --- a/e-and-p-tags.md +++ b/e-and-p-tags.md @@ -1,4 +1,4 @@ -# On 'e' and 'p' tags in Text Events (kind 1). +# On `e` and `p` tags in Text Events (kind 1). ### A recommendation for clients. The following seems to be the conventions that are used by `Branle`, `Damus`, and `more-speech` for referencing @@ -10,24 +10,26 @@ replies. * A reply thread is the tree of events consisting of all replies beginning at the root. * An event id is a 32 byte number in lower-case hexidecimal. -## The 'e' tag -Used in a text event contains a single event id. ["e", "~hex number~"] +## The `e` tag +Used in a text event contains a single event id. ["e", "`hex-number`"] - * No 'e' tag: + * No `e` tag: This event is not a reply to, nor does it refer to, any other event. - * One 'e' tag: ["e",id]: + * One `e` tag: ["e",`id`]: The id of the event to which this event is a reply. - * Two 'e' tags: ["e",root-id], ["e",reply-id] -'root-id' is the id of the event at the root of the reply chain. 'reply-id' is the id of the article to which this event is a reply. + * Two `e` tags: ["e",`root-id`], ["e",`reply-id`] +'root-id' is the `id` of the event at the root of the reply chain. `reply-id` is the id of the article to which this event is a reply. - * Many 'e' tags: ["e",root-id] ["e",mention-id], ..., ["e",reply-id] -There may be any number of 'mention-ids'. These are the ids of events which may, or may not be in the reply chain. They are citings from this event. 'root-id' and 'reply-id' are as above. + * Many `e` tags: ["e",`root-id`] ["e",`mention-id`], ..., ["e",`reply-id`] +There may be any number of `mention-ids`. These are the ids of events which may, or may not be in the reply chain. +They are citings from this event. `root-id` and `reply-id` are as above. -## The 'p' tag +## The `p` tag Used in a text event contains a list of pubkeys used to record who is involved in a reply thread. -When replying to a text event E with 'p' tags P, the replying event's 'p' tags should contain P as well as the pubkey of the of the event being replied to. +When replying to a text event E with `p` tags P, the replying event's `p` tags should contain P as well as the pubkey of the of the event being replied to. -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. +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. From 96e4e7eb5c0bba06e2a885c82b1a6e4db6ea49ef Mon Sep 17 00:00:00 2001 From: "Robert C. Martin" Date: Wed, 4 May 2022 15:04:20 -0500 Subject: [PATCH 3/4] NIP-13 Conventions for e and p tags in text events --- e-and-p-tags.md => 13.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) rename e-and-p-tags.md => 13.md (91%) diff --git a/e-and-p-tags.md b/13.md similarity index 91% rename from e-and-p-tags.md rename to 13.md index 447f9f85..75f802d3 100644 --- a/e-and-p-tags.md +++ b/13.md @@ -1,4 +1,12 @@ -# On `e` and `p` tags in Text Events (kind 1). +NIP-13 +====== + + +On `e` and `p` tags in Text Events (kind 1). +-------------------------------------------- + +`draft` ~`mandatory`~ `author:unclebobmartin` + ### A recommendation for clients. The following seems to be the conventions that are used by `Branle`, `Damus`, and `more-speech` for referencing From bd4a81a6042534fd88cb590ddf0524f5a8fe10bb Mon Sep 17 00:00:00 2001 From: "Robert C. Martin" Date: Wed, 4 May 2022 15:14:49 -0500 Subject: [PATCH 4/4] rename NIP-13 to NIP-10 --- 13.md => 10.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) rename 13.md => 10.md (93%) diff --git a/13.md b/10.md similarity index 93% rename from 13.md rename to 10.md index 75f802d3..c43aa938 100644 --- a/13.md +++ b/10.md @@ -1,4 +1,4 @@ -NIP-13 +NIP-10 ====== @@ -7,18 +7,18 @@ On `e` and `p` tags in Text Events (kind 1). `draft` ~`mandatory`~ `author:unclebobmartin` -### A recommendation for clients. +### A Conventional use of `e` and `p` tags within clients. The following seems to be the conventions that are used by `Branle`, `Damus`, and `more-speech` for referencing events and authors when building a reply. These conventions help clients build event threads, and alert authors of replies. -## Definitions: +### Definitions: * A reply chain is the list of events from the root event to a specific reply. * A reply thread is the tree of events consisting of all replies beginning at the root. * An event id is a 32 byte number in lower-case hexidecimal. -## The `e` tag +### The `e` tag Used in a text event contains a single event id. ["e", "`hex-number`"] * No `e` tag: @@ -34,7 +34,7 @@ The id of the event to which this event is a reply. There may be any number of `mention-ids`. These are the ids of events which may, or may not be in the reply chain. They are citings from this event. `root-id` and `reply-id` are as above. -## The `p` tag +### The `p` tag Used in a text event contains a list of pubkeys used to record who is involved in a reply thread. When replying to a text event E with `p` tags P, the replying event's `p` tags should contain P as well as the pubkey of the of the event being replied to.