nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-09-20 14:55:49 -04:00
Code Issues Actions Packages Projects Releases Wiki Activity

Apply suggestions from code review

Browse Source 
Co-authored-by: Semisol <45574030+Semisol@users.noreply.github.com>
This commit is contained in:
Alex Gleason 2023-03-21 12:21:45 -05:00 committed by GitHub
parent a55077fb93
commit 8f822946d4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 8 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
69.md
View File

@ -1,8 +1,8 @@
NIP-69
======
Deleting a Pubkey
-----------------
Public Key Revocation
---------------------
`draft` `optional` `author:alexgleason`
@ -12,11 +12,13 @@ Events of [kind `5`](09.md) may contain a "p" tag instead of "e" tags. The "p" t
Clients which recieve a pubkey deletion event SHOULD treat all events from that pubkey as if they were deleted in accordance with [NIP-09](09.md).
Clients may give users the option to "Delete your account" with this type of event. Clients SHOULD display a prominent message explaining that the action is not reversible, and SHOULD require special confirmation such as requiring the user to type a message.
Clients may give users the option to "Revoke your public key" with this type of event. Clients SHOULD display a prominent message explaining that the action is not reversible, SHOULD explain that this does not guarantee their posts are deleted forever, and SHOULD require special confirmation such as requiring the user to type a message.
Clients MUST NOT show the content field in the event for security reasons.
### Relay behavior
Relays receiving a pubkey deletion event MUST mark the pubkey as deleted, and MUST stop delivering events from this pubkey to clients, EXCEPT for events of kind `5`. Relays MAY delete events by this pubkey from their database, and SHOULD reject future events from the pubkey.
Relays receiving a pubkey revocation event MUST mark the pubkey as revoked, and MUST stop delivering events from this pubkey to clients, EXCEPT for events of kind `5`. Relays MAY delete events by this pubkey from their database, and SHOULD reject future events from the pubkey.
Relays SHOULD preserve events of kind `5` from the pubkey, as well as continue to collect and distribute events of kind `5`.
@ -29,7 +31,7 @@ Relays SHOULD preserve events of kind `5` from the pubkey, as well as continue t
"tags": [
["p", "6027adac157831dfe9d2f988c1b8b7a75d9296a7d42a0f9ed056a320925b0e13"],
],
"content": "", // optional message, same as NIP-09
"content": "",
// ...
}
```

2
README.md
View File

@ -38,7 +38,7 @@ NIPs stand for **Nostr Implementation Possibilities**. They exist to document wh
- [NIP-57: Lightning Zaps](57.md)
- [NIP-58: Badges](58.md)
- [NIP-65: Relay List Metadata](65.md)
- [NIP-69: Deleting a Pubkey](69.md)
- [NIP-69: Public Key Revocation](69.md)
- [NIP-78: Application-specific data](78.md)
## Event Kinds