upleb.uk

Public git repos — served from a NIP-34 GRASP relay at git.upleb.uk

summaryrefslogtreecommitdiff
path: root/18.md
diff options
context:
space:
mode:
authorAlex Gleason <alex@alexgleason.me>2026-04-10 13:31:37 -0500
committerAlex Gleason <alex@alexgleason.me>2026-04-10 13:31:37 -0500
commit5e1e24766910fc07cb61a049aed2623987458ec2 (patch)
treeb7588f61fddf9374268d5cd6f4e3f2655d7c840a /18.md
parentb8782df594b4e7e8f088869134908eed58be6078 (diff)
parent3465f540e3eaedccb5309711b502f0febf56b52f (diff)
Merge nip44-big-payloads into bigger-nip44bigger-nip44
Diffstat (limited to '18.md')
-rw-r--r--18.md24
1 files changed, 12 insertions, 12 deletions
diff --git a/18.md b/18.md
index 5d55f84..3b94df8 100644
--- a/18.md
+++ b/18.md
@@ -21,18 +21,12 @@ reposted.
21 21
22## Quote Reposts 22## Quote Reposts
23 23
24Quote reposts are `kind 1` events with an embedded `q` tag of the note being 24Mentions to [NIP-21](21.md) entities like `nevent`, `note` and `naddr` on any
25quote reposted. The `q` tag ensures quote reposts are not pulled and included 25event must be converted into `q` tags. The `q` tag ensures quote reposts are
26as replies in threads. It also allows you to easily pull and count all of the 26not pulled and included as replies in threads. It also allows you to easily
27quotes for a post. 27pull and count all of the quotes for a post. The syntax follows
28 28
29`q` tags should follow the same conventions as NIP 10 `e` tags, with the exception 29`["q", "<event-id> or <event-address>", "<relay-url>", "<pubkey-if-a-regular-event>"]`
30of the `mark` argument.
31
32`["q", <event-id>, <relay-url>, <pubkey>]`
33
34Quote reposts MUST include the [NIP-21](21.md) `nevent`, `note`, or `naddr` of the
35event in the content.
36 30
37## Generic Reposts 31## Generic Reposts
38 32
@@ -40,6 +34,12 @@ Since `kind 6` reposts are reserved for `kind 1` contents, we use `kind 16`
40as a "generic repost", that can include any kind of event inside other than 34as a "generic repost", that can include any kind of event inside other than
41`kind 1`. 35`kind 1`.
42 36
43`kind 16` reposts SHOULD contain a `k` tag with the stringified kind number 37`kind 16` reposts SHOULD contain a `"k"` tag with the stringified kind number
44of the reposted event as its value. 38of the reposted event as its value.
45 39
40When reposting a replaceable event, the repost SHOULD include an `"a"` tag with
41the event coordinate (`kind:pubkey:d-tag`) of the reposted event.
42
43If the `"a"` tag is not present, it indicates that a specific version of a replaceable
44event is being reposted, in which case the `content` field must contain the full
45JSON string of the reposted event.