diff options
| author | arthurfranca <arthur.a.franca@gmail.com> | 2023-03-25 11:58:31 -0300 |
|---|---|---|
| committer | arthurfranca <arthur.a.franca@gmail.com> | 2023-03-29 14:11:14 -0300 |
| commit | 197b6ea206611e751cb73c2e04a12b371674a109 (patch) | |
| tree | 0718a8fca50559a30fb8222841b19aa00de3c49e | |
| parent | 133faa07636fff9f8e91c69cb9e3a5cce459b241 (diff) | |
Bring back NIP-18
| -rw-r--r-- | 18.md | 19 | ||||
| -rw-r--r-- | README.md | 1 |
2 files changed, 20 insertions, 0 deletions
| @@ -0,0 +1,19 @@ | |||
| 1 | NIP-18 | ||
| 2 | ====== | ||
| 3 | |||
| 4 | Reposts | ||
| 5 | ------- | ||
| 6 | |||
| 7 | `draft` `optional` `author:jb55` | ||
| 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. | ||
| 13 | |||
| 14 | The repost event MUST include an `e` tag with the `id` of the note that is | ||
| 15 | being reposted. That tag SHOULD include a relay URL as its third entry | ||
| 16 | to indicate where it can be fetched. | ||
| 17 | |||
| 18 | The repost SHOULD include a `p` tag with the `pubkey` of the event being | ||
| 19 | reposted. | ||
| @@ -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) |