-
Notifications
You must be signed in to change notification settings - Fork 613
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
Open
vitorpamplona
wants to merge
16
commits into
nostr-protocol:master
Choose a base branch
from
vitorpamplona:right-to-vanish
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Right to Vanish #1256
Changes from 14 commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
4d64605
Adds a right to vanish NIP
vitorpamplona 2137719
updates readme
vitorpamplona 609571e
Typos
vitorpamplona 651abea
Update 62.md
vitorpamplona 0162794
Unifies 62 and 63 into one with ALL_RELAYS
vitorpamplona 985388e
Removes 63 from the readme
vitorpamplona 86fc593
wording
vitorpamplona 7521f7a
Changed from delete account to delete my content.
vitorpamplona d9b39fc
- Changed language from Right to Vanish to Request to Vanish
vitorpamplona ab8a580
typos
vitorpamplona 59eb1cc
Merge remote-tracking branch 'upstream/master' into right-to-vanish
vitorpamplona 9601eb2
Update 62.md
vitorpamplona 1cf833d
Update 62.md
vitorpamplona 44d8122
Adds clause to disallow kind5 deletions of kind 62
vitorpamplona 4b73e75
Update 62.md
vitorpamplona 553de66
adjust DM deletion require matching relay service url
vitorpamplona File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,61 @@ | ||
NIP-62 | ||
====== | ||
|
||
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. This procedure is legally binding in some jurisdictions, and thus, supporters of this NIP should truly delete events from their database. | ||
|
||
## Request to Vanish from Relay | ||
|
||
Kind `62` requests a specific relay to delete everything, including [NIP-09](09.md) Deletion Events, from the `.pubkey` until its `.created_at`. | ||
|
||
```jsonc | ||
{ | ||
"kind": 62, | ||
"pubkey": <32-byte hex-encoded public key of the event creator>, | ||
"tags": [ | ||
["relay", "<relay url>"] | ||
], | ||
"content": "<reason or note>", | ||
//...other fields | ||
} | ||
``` | ||
|
||
The tag list MUST include at least one `relay` value. | ||
|
||
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 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.
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 restrict who can post MUST also follow the request regardless of the user's status. | ||
|
||
Kind `5` deletions MUST not delete kind `62`s. | ||
vitorpamplona marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
Clients SHOULD send this event to the target relays only. | ||
|
||
## Global Request to Vanish | ||
|
||
To request ALL relays to delete everything, the event MUST include a `relay` tag with the value `ALL_RELAYS` in uppercase. | ||
|
||
```jsonc | ||
{ | ||
"kind": 62, | ||
"pubkey": <32-byte hex-encoded public key of the event creator>, | ||
"tags": [ | ||
["relay", "ALL_RELAYS"] | ||
], | ||
"content": "<reason>", | ||
//...other fields | ||
} | ||
``` | ||
|
||
Clients SHOULD broadcast this event to as many relays as possible. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this mostly called right to be forgotten in the internet. i think we can consider this as a better name. RTBF.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can do either. I was reticent to use "forgotten" because deleting stuff from relays doesn't mean you will be "forgotten". It just means that your data was deleted from that instance or instances that received this event and comply to it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i agree and it's logical. but i think this is same for other stuff on web and internet, and using
forgotten
just makes it easier ti understand for people from everywhere. im more agree withforgotten
or maybe something between. we can think more about the name.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
found this: https://en.wikipedia.org/wiki/Right_to_be_forgotten.
they call it vanish as well. we can use one of them and include other one on details of standard. maybe.