Merge pull request #397 from arthurfranca/repost-res

This commit is contained in:
fiatjaf_ 2023-03-29 19:37:13 -03:00 committed by GitHub
commit 599e131323
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 27 additions and 0 deletions

25
18.md Normal file
View File

@ -0,0 +1,25 @@
NIP-18
======
Reposts
-------
`draft` `optional` `author:jb55` `author:fiatjaf` `author:arthurfranca`
A repost is a `kind 6` note that is used to signal to followers
that another event is worth reading.
The `content` of a repost event is empty. Optionally, it MAY contain
the stringified JSON of the reposted note event for quick look up.
The repost event MUST include an `e` tag with the `id` of the note that is
being reposted. That tag MUST include a relay URL as its third entry
to indicate where it can be fetched.
The repost SHOULD include a `p` tag with the `pubkey` of the event being
reposted.
## Quote Reposts
Quote reposts are `kind 1` events with an embedded `e` tag (see [NIP-08](08.md) and [NIP-27](27.md)).
Because a quote repost includes an `e` tag, it may show up along replies to the reposted note.

View File

@ -18,6 +18,7 @@ NIPs stand for **Nostr Implementation Possibilities**. They exist to document wh
- [NIP-14: Subject tag in text events.](14.md)
- [NIP-15: End of Stored Events Notice](15.md)
- [NIP-16: Event Treatment](16.md)
- [NIP-18: Reposts](18.md)
- [NIP-19: bech32-encoded entities](19.md)
- [NIP-20: Command Results](20.md)
- [NIP-21: `nostr:` URL scheme](21.md)
@ -51,6 +52,7 @@ NIPs stand for **Nostr Implementation Possibilities**. They exist to document wh
| 3 | Contacts | [2](02.md) |
| 4 | Encrypted Direct Messages | [4](04.md) |
| 5 | Event Deletion | [9](09.md) |
| 6 | Reposts | [18](18.md) |
| 7 | Reaction | [25](25.md) |
| 8 | Badge Award | [58](58.md) |
| 40 | Channel Creation | [28](28.md) |