Drop event copy

18.md

@@ -4,18 +4,22 @@ NIP-18
 Reposts
 -------
 
-`draft` `optional` `author:fiatjaf` `author:arthurfranca`
+`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
-a comment in the same format of a kind 1 note content.
+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 SHOULD include a relay URL as its third entry
+being reposted. That tag MUST include a relay URL as its third entry
 to indicate where it can be fetched.
-When reposting a long-form content use an `a` tag instead.
 
 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.

30.md

@@ -1,21 +0,0 @@
-NIP-30
-======
-
-Event Copy
-----------
-
-`draft` `optional` `author:jb55` `author:arthurfranca`
-
-An event of `kind 9` is used to copy any event from another pubkey. A copy
-allows its creator to keep content around even when the original gets deleted.
-
-The `content` of a copy event MUST be the stringified JSON of the whole original event.
-
-The copy event SHOULD include a `k` tag with the `kind` of the note that is
-being copied. This enables subscribing to a subset of copies.
-
-The copy event SHOULD include an `e` tag with the `id` of the note that is
-being copied. This allows the original author to know a specific event has been copied.
-
-The copy event SHOULD include a `p` tag with the `pubkey` of the event being
-copied to notify original author.

README.md

@@ -28,7 +28,6 @@ NIPs stand for **Nostr Implementation Possibilities**. They exist to document wh
 - [NIP-26: Delegated Event Signing](26.md)
 - [NIP-27: Text Note References](27.md)
 - [NIP-28: Public Chat](28.md)
-- [NIP-30: Event Copy](30.md)
 - [NIP-33: Parameterized Replaceable Events](33.md)
 - [NIP-36: Sensitive Content](36.md)
 - [NIP-39: External Identities in Profiles](39.md)
@@ -56,7 +55,6 @@ NIPs stand for **Nostr Implementation Possibilities**. They exist to document wh
 | 6             | Reposts                          | [18](18.md) |
 | 7             | Reaction                         | [25](25.md) |
 | 8             | Badge Award                      | [58](58.md) |
-| 9             | Event Copy                       | [30](30.md) |
 | 40            | Channel Creation                 | [28](28.md) |
 | 41            | Channel Metadata                 | [28](28.md) |
 | 42            | Channel Message                  | [28](28.md) |
@@ -116,7 +114,6 @@ When experimenting with kinds, keep in mind the classification introduced by [NI
 | g          | geohash                 |                   | [12](12.md)              |
 | nonce      | random                  |                   | [13](13.md)              |
 | subject    | subject                 |                   | [14](14.md)              |
-| k          | referenced event kind   |                   | [30](30.md)              |
 | d          | identifier              |                   | [33](33.md)              |
 | expiration | unix timestamp (string) |                   | [40](40.md)              |