NIP-62 feels like an awesomely horrible idea 😅😅😅😅

Reply to this note

Please Login to reply.

Discussion

elaborate?

it's a single event that is (supposed to) permanently and irrevocably make your pubkey unusable

that sounds awesomely horrible indeed, but why would any nip wanna do that?

I think most likely is to get appstore approvals

I don't think it's relevant for appstores. To "delete" an account clients can just trash the nsec, to remove content we have NIP-05.

I think just locally deleting the privkey is enough; that's why damus added that thing that mangles your kind:0 and other stuff iirc

You mean "it's *not* enought", right?

Probably you are right.

yes, that's what I meant -- "it's not enough"

I guess the use case for if you leaked your nsec?

I think the use case is more to be able to credibly get approved by app stores 😂

Do you prefer deleting events one by one with nip 05?

it's kind 5.👀

Only if I get to compute each signature by hand

now more seriously, I understand the need, I just think it's too big of a footgun and that at least it should require a lot of PoW or a NIP-70 + an OTA so the person with the privkey must be the one sending it and the event is only valid for some time; I don't know, something like that that reduces the effect of the event

A 24h (or more) delay in the execution and a undo event is what is needed, imo.

why?

Interesting discussion. How do you square Nostr's censorship resistance with this apparent "right" to vanish? As mentioned in the thread, there is a risk here of a malicious client nuking all your posts. But isn't a bigger danger that it could be coerced, e.g. by a state actor?

nostr:nevent1qvzqqqqqqypzp75cf0tahv5z7plpdeaws7ex52nmnwgtwfr2g3m37r844evqrr6jqyxhwumn8ghj7e3h0ghxjme0qyd8wumn8ghj7urewfsk66ty9enxjct5dfskvtnrdakj7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uqzq5p9c32qxgjeg95yu4j4x5psdtft4zt25tadkxprcszks8hmgcsgrvvzqg