nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-11-12 15:09:07 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

Clarifies the behavior when referencing a tags.

Browse Source
This commit is contained in:
Vitor Pamplona 2024-03-29 10:20:12 -04:00
parent 7bfc5116de
commit 41ecd11cb5
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
09.md
View File

@ -6,9 +6,11 @@ Event Deletion
`draft` `optional`
Event kind `5` describes a deletion event. It MUST contain a list of one or more `e` or `a` tags, each referencing the events the author is requesting to be deleted.
Event kind `5` describes a deletion event. It MUST contain a list of `e` or `a` tags, each referencing the events the author is requesting to be deleted.
The `.content` MAY contain the reason for the deletion. One or more `k` tags MAY be added to describe the kind of the referenced events.
`a` tags request the deletion of all past versions of a replaceable event: all versions whose `.created_at` is less or equal the deletion request's `created_at`.
The `.content` MAY contain the reason for the deletion. `k` tags MAY be added to describe the kinds of the referenced events.
```
{
@ -17,7 +19,8 @@ The `.content` MAY contain the reason for the deletion. One or more `k` tags MAY
"tags": [
["e", "dcd59..464a2"],
["e", "968c5..ad7a4"],
["k", "<kind>"],
["k", "<kind of dcd59..464a2>"],
["k", "<kind of 968c5..ad7a4>"],
["a", "<kind>:<pubkey>:<d-identifier>"]
],
"content": "these posts were published by accident",
@ -27,8 +30,6 @@ The `.content` MAY contain the reason for the deletion. One or more `k` tags MAY
Supporters MUST verify if the `pubkey` of the Deletion event is the same as the `pubkey` of the referenced events.
Deletion events referencing an `a` tag delete all the referenced events up to the deletion event's `created_at`.
Relays SHOULD delete or stop publishing any referenced events of the deletion request.
Relays SHOULD continue to publish/share the deletion events indefinitely, as clients may already have the event that's intended to be deleted.