This NIP doesn't actually change the existing delete functionality, it just pushes the work of deleting each note in a batch process onto the relay and adds an air of legal formality that can't be easily enforced.

Solution without a problem, that just adds complexity for relay operators, IMO, but whatever.

Reply to this note

Please Login to reply.

Discussion

Storing Delete Events for each note when the user wants o delete the whole account is a burden to any relay. My delete events alone are already 5 MBs or so.

On the enforcement side, as a person manages HIPAA-compliant data in Nostr relays, I strongly disagree. Enforcement is just one fuck up away.

Okay, yes, this could hit the OtherStuff, since they often have to be audited or certified.

That's a good argument.

Didn't realize the data size.

Seems like an inefficiency, to have to keep everyone's delete events forever. Even this change wouldn't completely solve for that, as some people are rotating fast through keys or auto-deleting on a script, but not "burning" the npub.

Maybe we should make more use of NIP-40. If someone is delete-happy, couldn't they just have a client setting that causes their notes to expire after about 3 months. Then you don't have to retain an event, after deleting.

https://github.com/nostr-protocol/nips/blob/master/40.md