This is very true.
With some rare exceptions (IE legally enforced data deletion upon user request) nothing is ever truly deleted. Any enterprise data warehouse system, at scale, will use “soft deletion” techniques like updating an IS_DELETED flag to TRUE.
I don’t know the intricacies of the deletion NIP… but if the consensus is that the protocol mechanism is good enough, then clients would do well to implement it.
I’ve seen so many people say they won’t use Nostr because we don’t support delete. This is really frustrating, because Nostr DOES support delete, it’s right there in the NIP’s! We’ve got delete in @npub1pu3v...tfch, but most apps don’t expose the functionality to users because they either don’t like the idea of delete or can’t be sure that something is 100% deleted. That misses the point, delete is as much about social signaling as it is about getting rid of the content.
Here’s my argument for how we should think about and support delete in nostr. In case your client doesn’t support long form content, here’s the njump link: https://njump.me/naddr1qq2ksje3g9trxujpxymyxjjlg5ckjmmrtguyxq3qpu3vqm4vzqpxsnhuc684dp2qaq6z69sf65yte4p39spcucv5lzmqxpqqqp65wk06e7u View quoted note →
View quoted note →
