diff options
| author | Pablo Fernandez <pfer@me.com> | 2025-01-13 14:35:56 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-01-13 14:35:56 +0000 |
| commit | 0f376a7aa455521f3d2f4ec6a8dd1b764ec8d7bb (patch) | |
| tree | c03ba7b078eea415167907447b2dfec52a2274eb /18.md | |
| parent | 76fd221ff1da383546f624615a38b6f961033b37 (diff) | |
| parent | d96f6f852a080fd84251af6b6d6fb82313b199a8 (diff) | |
Merge pull request #1679 from nostr-protocol/reposted-70s
Don't stringify magic-wanded protected events in reposts
Diffstat (limited to '18.md')
| -rw-r--r-- | 18.md | 2 |
1 files changed, 2 insertions, 0 deletions
| @@ -10,6 +10,7 @@ A repost is a `kind 6` event that is used to signal to followers | |||
| 10 | that a `kind 1` text note is worth reading. | 10 | that a `kind 1` text note is worth reading. |
| 11 | 11 | ||
| 12 | The `content` of a repost event is _the stringified JSON of the reposted note_. It MAY also be empty, but that is not recommended. | 12 | The `content` of a repost event is _the stringified JSON of the reposted note_. It MAY also be empty, but that is not recommended. |
| 13 | Reposts of [NIP-70](70.md)-protected events SHOULD always have an empty `content`. | ||
| 13 | 14 | ||
| 14 | The repost event MUST include an `e` tag with the `id` of the note that is | 15 | The repost event MUST include an `e` tag with the `id` of the note that is |
| 15 | being reposted. That tag MUST include a relay URL as its third entry | 16 | being reposted. That tag MUST include a relay URL as its third entry |
| @@ -41,3 +42,4 @@ as a "generic repost", that can include any kind of event inside other than | |||
| 41 | 42 | ||
| 42 | `kind 16` reposts SHOULD contain a `k` tag with the stringified kind number | 43 | `kind 16` reposts SHOULD contain a `k` tag with the stringified kind number |
| 43 | of the reposted event as its value. | 44 | of the reposted event as its value. |
| 45 | |||