NIP18: Reposts (#140)

Co-authored-by: Leo Wandersleb <leo@leowandersleb.de>

18.md

@@ -0,0 +1,19 @@
+NIP-18
+======
+
+Reposts
+-------
+
+`draft` `optional` `author:jb55`
+
+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.
+
+The repost event MUST include an `e` tag with the `id` of the note that is
+being reposted. That tag SHOULD 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.

README.md

@@ -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-22: Event created_at Limits](22.md)
@@ -38,6 +39,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           | Repost                      | [18](18.md)            |
 | 7           | Reaction                    | [25](25.md)            |
 | 40          | Channel Creation            | [28](28.md)            |
 | 41          | Channel Metadata            | [28](28.md)            |