diff options
| author | fiatjaf_ <fiatjaf@gmail.com> | 2023-03-29 19:37:13 -0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-03-29 19:37:13 -0300 |
| commit | 599e131323d1db908fd2a545e77722c1ef5fcfc1 (patch) | |
| tree | bce3cc22601b049a4ebda6bd412f7a26686106de | |
| parent | 133faa07636fff9f8e91c69cb9e3a5cce459b241 (diff) | |
| parent | 800c0d0cd397eb4b043ef0cdaefd0bad18cb1cd5 (diff) | |
Merge pull request #397 from arthurfranca/repost-res
| -rw-r--r-- | 18.md | 25 | ||||
| -rw-r--r-- | README.md | 2 |
2 files changed, 27 insertions, 0 deletions
| @@ -0,0 +1,25 @@ | |||
| 1 | NIP-18 | ||
| 2 | ====== | ||
| 3 | |||
| 4 | Reposts | ||
| 5 | ------- | ||
| 6 | |||
| 7 | `draft` `optional` `author:jb55` `author:fiatjaf` `author:arthurfranca` | ||
| 8 | |||
| 9 | A repost is a `kind 6` note that is used to signal to followers | ||
| 10 | that another event is worth reading. | ||
| 11 | |||
| 12 | The `content` of a repost event is empty. Optionally, it MAY contain | ||
| 13 | the stringified JSON of the reposted note event for quick look up. | ||
| 14 | |||
| 15 | The repost event MUST include an `e` tag with the `id` of the note that is | ||
| 16 | being reposted. That tag MUST include a relay URL as its third entry | ||
| 17 | to indicate where it can be fetched. | ||
| 18 | |||
| 19 | The repost SHOULD include a `p` tag with the `pubkey` of the event being | ||
| 20 | reposted. | ||
| 21 | |||
| 22 | ## Quote Reposts | ||
| 23 | |||
| 24 | Quote reposts are `kind 1` events with an embedded `e` tag (see [NIP-08](08.md) and [NIP-27](27.md)). | ||
| 25 | Because a quote repost includes an `e` tag, it may show up along replies to the reposted note. | ||
| @@ -18,6 +18,7 @@ NIPs stand for **Nostr Implementation Possibilities**. They exist to document wh | |||
| 18 | - [NIP-14: Subject tag in text events.](14.md) | 18 | - [NIP-14: Subject tag in text events.](14.md) |
| 19 | - [NIP-15: End of Stored Events Notice](15.md) | 19 | - [NIP-15: End of Stored Events Notice](15.md) |
| 20 | - [NIP-16: Event Treatment](16.md) | 20 | - [NIP-16: Event Treatment](16.md) |
| 21 | - [NIP-18: Reposts](18.md) | ||
| 21 | - [NIP-19: bech32-encoded entities](19.md) | 22 | - [NIP-19: bech32-encoded entities](19.md) |
| 22 | - [NIP-20: Command Results](20.md) | 23 | - [NIP-20: Command Results](20.md) |
| 23 | - [NIP-21: `nostr:` URL scheme](21.md) | 24 | - [NIP-21: `nostr:` URL scheme](21.md) |
| @@ -51,6 +52,7 @@ NIPs stand for **Nostr Implementation Possibilities**. They exist to document wh | |||
| 51 | | 3 | Contacts | [2](02.md) | | 52 | | 3 | Contacts | [2](02.md) | |
| 52 | | 4 | Encrypted Direct Messages | [4](04.md) | | 53 | | 4 | Encrypted Direct Messages | [4](04.md) | |
| 53 | | 5 | Event Deletion | [9](09.md) | | 54 | | 5 | Event Deletion | [9](09.md) | |
| 55 | | 6 | Reposts | [18](18.md) | | ||
| 54 | | 7 | Reaction | [25](25.md) | | 56 | | 7 | Reaction | [25](25.md) | |
| 55 | | 8 | Badge Award | [58](58.md) | | 57 | | 8 | Badge Award | [58](58.md) | |
| 56 | | 40 | Channel Creation | [28](28.md) | | 58 | | 40 | Channel Creation | [28](28.md) | |