diff options
| author | Oscar Merry <MerryOscar@users.noreply.github.com> | 2024-06-17 13:38:45 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-06-17 13:38:45 +0100 |
| commit | 45351b561dcc15b9d3c09b64967a5e30a80ddabe (patch) | |
| tree | e3bb8995aed591b519d042909eddd7d983bbe56e /09.md | |
| parent | 32004283da0f0893d7b697c9a0b1a1f8611e9929 (diff) | |
| parent | c576737ba42772a561c6ebfd9faf0baae6d19b17 (diff) | |
Merge branch 'nostr-protocol:master' into external-content-ids
Diffstat (limited to '09.md')
| -rw-r--r-- | 09.md | 2 |
1 files changed, 2 insertions, 0 deletions
| @@ -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. |