2023-03-25 10:58:31 -04:00
|
|
|
NIP-18
|
|
|
|
|
======
|
|
|
|
|
|
|
|
|
|
Reposts
|
|
|
|
|
-------
|
|
|
|
|
|
2023-11-15 19:42:51 -05:00
|
|
|
`draft` `optional`
|
2023-03-25 10:58:31 -04:00
|
|
|
|
2023-06-16 17:16:42 -04:00
|
|
|
A repost is a `kind 6` event that is used to signal to followers
|
|
|
|
|
that a `kind 1` text note is worth reading.
|
2023-03-25 10:58:31 -04:00
|
|
|
|
2024-08-06 10:52:32 -04:00
|
|
|
For security reasons, The `content` of a repost event MUST not be set _the stringified JSON of the reposted note_. It SHOULD always be empty.
|
2023-03-25 10:58:31 -04:00
|
|
|
|
|
|
|
|
The repost event MUST include an `e` tag with the `id` of the note that is
|
2023-03-29 17:45:12 -04:00
|
|
|
being reposted. That tag MUST include a relay URL as its third entry
|
2023-03-25 10:58:31 -04:00
|
|
|
to indicate where it can be fetched.
|
|
|
|
|
|
|
|
|
|
The repost SHOULD include a `p` tag with the `pubkey` of the event being
|
|
|
|
|
reposted.
|
2023-03-29 17:45:12 -04:00
|
|
|
|
|
|
|
|
## Quote Reposts
|
|
|
|
|
|
2024-02-22 14:38:39 -05:00
|
|
|
Quote reposts are `kind 1` events with an embedded `q` tag of the note being
|
|
|
|
|
quote reposted. The `q` tag ensures quote reposts are not pulled and included
|
|
|
|
|
as replies in threads. It also allows you to easily pull and count all of the
|
|
|
|
|
quotes for a post.
|
2023-06-16 17:16:42 -04:00
|
|
|
|
|
|
|
|
## Generic Reposts
|
|
|
|
|
|
|
|
|
|
Since `kind 6` reposts are reserved for `kind 1` contents, we use `kind 16`
|
|
|
|
|
as a "generic repost", that can include any kind of event inside other than
|
|
|
|
|
`kind 1`.
|
|
|
|
|
|
|
|
|
|
`kind 16` reposts SHOULD contain a `k` tag with the stringified kind number
|
|
|
|
|
of the reposted event as its value.
|
