From bd4a81a6042534fd88cb590ddf0524f5a8fe10bb Mon Sep 17 00:00:00 2001 From: "Robert C. Martin" Date: Wed, 4 May 2022 15:14:49 -0500 Subject: [PATCH] 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 75f802d..c43aa93 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.