diff options
| author | fiatjaf <fiatjaf@gmail.com> | 2023-01-16 15:58:49 -0300 |
|---|---|---|
| committer | fiatjaf <fiatjaf@gmail.com> | 2023-01-16 15:58:53 -0300 |
| commit | 73496430691befb08c4dd22e4027b86091580e29 (patch) | |
| tree | 9edc3cc4c5d9e30a2792e09622b79164de80b9e2 | |
| parent | be0a426745252eeb420a38e4896b28059b4f7fa5 (diff) | |
remove NIP-18, it is not really a standard.
closes https://github.com/nostr-protocol/nips/issues/173
| -rw-r--r-- | 18.md | 19 | ||||
| -rw-r--r-- | README.md | 1 |
2 files changed, 0 insertions, 20 deletions
| @@ -1,19 +0,0 @@ | |||
| 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,7 +18,6 @@ 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) | ||
| 22 | - [NIP-19: bech32-encoded entities](19.md) | 21 | - [NIP-19: bech32-encoded entities](19.md) |
| 23 | - [NIP-20: Command Results](20.md) | 22 | - [NIP-20: Command Results](20.md) |
| 24 | - [NIP-22: Event created_at Limits](22.md) | 23 | - [NIP-22: Event created_at Limits](22.md) |