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

- Changed language from Right to Vanish to Request to Vanish

Browse Source 
- Added deletion of GiftWrapped DMs
- Reduced duplications from the merge of the two separate events in the past.
This commit is contained in:
Vitor Pamplona 2024-08-25 09:51:52 -04:00
parent 7521f7a445
commit d9b39fc468
1 changed files with 12 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
62.md
View File

@ -1,16 +1,16 @@
NIP-62
======
Right to Vanish
---------------
Request to Vanish
-----------------
`draft` `optional`
This NIP offers a Nostr-native way to request a complete reset of a key's fingerprint on the web. In some jurisdictions, this is a legally binding procedure and thus supporters of this NIP MUST trully delete events from their database.
This NIP offers a Nostr-native way to request a complete reset of a key's fingerprint on the web. This is a legally binding procedure in some jurisdictions and thus supporters of this NIP should trully delete events from their database.
## Delete My Content
## Request to Vanish from Relay
Kind `62` informs a specific relay to delete everything, including [NIP-09](09.md) Deletion Events, from the `.pubkey` until its `.created_at`
Kind `62` requests a specific relay to delete everything, including [NIP-09](09.md) Deletion Events, from the `.pubkey` until its `.created_at`.
```js
{
@ -30,15 +30,19 @@ Content MAY include a reason or a legal notice to the relay operator.
Relays MUST fully delete any events from the `.pubkey` if their service url is tagged in the event.
Relays MAY store the deletion request for bookkeeping and ensure past events are not re-broadcasted into the relay.
Relays SHOULD delete all [NIP-59](59.md) Gift Wraps that p-tagged the `.pubkey`, deleting all DMs to the pubkey.
Relays MUST ensure the deleted events cannot be re-broadcasted into the relay.
Relays MAY store the signed deletion request for bookkeeping.
Paid relays or relays that have restrictions on who can post MUST also follow the request regardless of the user's status.
Clients SHOULD send this event to the target relays only.
## Right to Vanish
## Global Request to Vanish
Kind `62` can also inform ALL relays to delete everything, including [NIP-09](09.md) Deletion Events, from the `.pubkey` until its `.created_at`
To request ALL relays to delete everything, the event MUST include a `relay` tag with value `ALL_RELAYS` in uppercase.
```js
{
@ -52,14 +56,4 @@ Kind `62` can also inform ALL relays to delete everything, including [NIP-09](09
}
```
The tag list MUST include a `relay` with value `ALL_RELAYS` in uppercase.
Content MAY include a reason to the relay operator.
Relays MUST fully delete any events from the `.pubkey`.
Relays MAY store the deletion request for bookkeeping and ensure past events are not re-broadcasted into the relay.
Paid relays or relays that have restrictions on who can post MUST also follow the request regardless of the user's status.
Clients SHOULD broadcast this event to as many relays as possible.