From a45cf22ed6bd760ec0188b8d35a09a37a8ba385a Mon Sep 17 00:00:00 2001 From: Alex Gleason Date: Tue, 21 Mar 2023 12:24:02 -0500 Subject: [PATCH] NIP-69: deletion --> revocation --- 69.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/69.md b/69.md index 510c6310..7ca4c9d7 100644 --- a/69.md +++ b/69.md @@ -10,7 +10,7 @@ Events of [kind `5`](09.md) may contain a "p" tag instead of "e" tags. The "p" t ### Client behavior -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 which recieve a pubkey revocation 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 "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. @@ -34,4 +34,4 @@ Relays SHOULD preserve events of kind `5` from the pubkey, as well as continue t "content": "", // ... } -``` \ No newline at end of file +```