diff options
| author | pablof7z <pfer@me.com> | 2025-01-10 08:27:14 -0600 |
|---|---|---|
| committer | pablof7z <pfer@me.com> | 2025-01-10 08:27:14 -0600 |
| commit | 1f8bbbfb50150644c0bb56229394aca95310f7a8 (patch) | |
| tree | 3ed5ff1d340d0b414d07ceaab9a690946725d356 | |
| parent | 2561566af79e6cd6dd82c4980a711847f27dba3f (diff) | |
specify magic-wanded protected events should not be stringified in a repost
| -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 | [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 | |||