Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions 09.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,6 +48,12 @@ Clients MAY choose to inform the user that their request for deletion does not g

Relays MAY validate that a deletion request event only references events that have the same `pubkey` as the deletion request itself, however this is not required since relays may not have knowledge of all referenced events.

### Cascading Deletion of Reposts

When a relay receives a `kind 5` deletion request, it SHOULD also delete any `kind 6` or `kind 16` repost events whose `p` tag matches the deletion request's `pubkey` and whose `e` tag references the deleted event. Relays SHOULD perform this cascading deletion even if they no longer hold the original event being deleted.

This prevents reposts — which may contain a full copy of the original event in their `content` field — from continuing to serve content that the original author has requested to be deleted.

## Deletion Request of a Deletion Request

Publishing a deletion request event against a deletion request has no effect. Clients and relays are not obliged to support "unrequest deletion" functionality.