diff options
| author | Pablo Fernandez <pfer@me.com> | 2025-01-13 14:35:10 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-01-13 14:35:10 +0000 |
| commit | d96f6f852a080fd84251af6b6d6fb82313b199a8 (patch) | |
| tree | b6a423b93774fa19048369ab55384a43c04d0734 | |
| parent | 1f8bbbfb50150644c0bb56229394aca95310f7a8 (diff) | |
Update 18.md
Co-authored-by: hodlbod <jstaab@protonmail.com>
| -rw-r--r-- | 18.md | 2 |
1 files changed, 1 insertions, 1 deletions
| @@ -10,7 +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 | Reposts of [NIP-70](70.md)-protected events SHOULD always have an empty `content`. |
| 14 | 14 | ||
| 15 | 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 |
| 16 | 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 |