-
Notifications
You must be signed in to change notification settings - Fork 721
Right to Vanish #1256
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Right to Vanish #1256
Changes from 1 commit
4d64605
2137719
609571e
651abea
0162794
985388e
86fc593
7521f7a
d9b39fc
ab8a580
59eb1cc
9601eb2
1cf833d
44d8122
4b73e75
553de66
8e479d5
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
- Added deletion of GiftWrapped DMs - Reduced duplications from the merge of the two separate events in the past.
- Loading branch information
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -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 | ||
vitorpamplona marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| { | ||
|
|
@@ -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. | ||
vitorpamplona marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| 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 | ||
vitorpamplona marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
| 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 | ||
vitorpamplona marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| { | ||
|
|
@@ -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. | ||
|
||
Uh oh!
There was an error while loading. Please reload this page.