There is ALWAYS FREEDOM to change REVISE a VIEWPONT of published in subsequent note - (leaving aside typo errors) but just like "word spoken out of mouth cannot retracted back" short works the same way. no one can guarantee that someone didnot grab screenshot what u said/posted before in decentralized mesh. just somewhat wayback web machine archive old webpage.
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 nostr:npub1pu3vqm4vzqpxsnhuc684dp2qaq6z69sf65yte4p39spcucv5lzmqswtfch, 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 nostr:note1hldm4z430w76dn2ywzwjnafytnvyt7gsg6nhk3l8a3x8utzl88asl06u8m
Discussion
But the delete request note lets everyone be very clear that the note was retracted. It’s fine for their to be copies and archives, but we need to show, “i want this deleted” and to not show that delete content in the user’s normal profile or threads.
Cool that makes sense - old retracted copy can still be floating somewhere publisher know it.