diff options
Diffstat (limited to '09.md')
| -rw-r--r-- | 09.md | 10 |
1 files changed, 6 insertions, 4 deletions
| @@ -6,9 +6,7 @@ Event Deletion | |||
| 6 | 6 | ||
| 7 | `draft` `optional` | 7 | `draft` `optional` |
| 8 | 8 | ||
| 9 | A special event with kind `5`, meaning "deletion" is defined as having a list of one or more `e` tags, each referencing an event the author is requesting to be deleted. | 9 | A special event with kind `5`, meaning "deletion" is defined as having a list of one or more `e` or `a` tags, each referencing an event the author is requesting to be deleted. Deletion requests SHOULD include a `k` tag for the kind of each event being deleted. |
| 10 | |||
| 11 | Each tag entry must contain an "e" event id and/or `a` tags intended for deletion. | ||
| 12 | 10 | ||
| 13 | The event's `content` field MAY contain a text note describing the reason for the deletion. | 11 | The event's `content` field MAY contain a text note describing the reason for the deletion. |
| 14 | 12 | ||
| @@ -21,7 +19,9 @@ For example: | |||
| 21 | "tags": [ | 19 | "tags": [ |
| 22 | ["e", "dcd59..464a2"], | 20 | ["e", "dcd59..464a2"], |
| 23 | ["e", "968c5..ad7a4"], | 21 | ["e", "968c5..ad7a4"], |
| 24 | ["a", "<kind>:<pubkey>:<d-identifier>"] | 22 | ["a", "<kind>:<pubkey>:<d-identifier>"], |
| 23 | ["k", "1"], | ||
| 24 | ["k", "30023"] | ||
| 25 | ], | 25 | ], |
| 26 | "content": "these posts were published by accident", | 26 | "content": "these posts were published by accident", |
| 27 | ...other fields | 27 | ...other fields |
| @@ -32,6 +32,8 @@ Relays SHOULD delete or stop publishing any referenced events that have an ident | |||
| 32 | 32 | ||
| 33 | Relays SHOULD continue to publish/share the deletion events indefinitely, as clients may already have the event that's intended to be deleted. Additionally, clients SHOULD broadcast deletion events to other relays which don't have it. | 33 | Relays SHOULD continue to publish/share the deletion events indefinitely, as clients may already have the event that's intended to be deleted. Additionally, clients SHOULD broadcast deletion events to other relays which don't have it. |
| 34 | 34 | ||
| 35 | When an `a` tag is used, relays SHOULD delete all versions of the replaceable event up to the `created_at` timestamp of the deletion event. | ||
| 36 | |||
| 35 | ## Client Usage | 37 | ## Client Usage |
| 36 | 38 | ||
| 37 | Clients MAY choose to fully hide any events that are referenced by valid deletion events. This includes text notes, direct messages, or other yet-to-be defined event kinds. Alternatively, they MAY show the event along with an icon or other indication that the author has "disowned" the event. The `content` field MAY also be used to replace the deleted events' own content, although a user interface should clearly indicate that this is a deletion reason, not the original content. | 39 | Clients MAY choose to fully hide any events that are referenced by valid deletion events. This includes text notes, direct messages, or other yet-to-be defined event kinds. Alternatively, they MAY show the event along with an icon or other indication that the author has "disowned" the event. The `content` field MAY also be used to replace the deleted events' own content, although a user interface should clearly indicate that this is a deletion reason, not the original content. |