I think a lot depends on the messaging that clients provide to users around these actions. Ideally it can be kept as simple as possible without committing to something that a client can’t commit to.
A client can commit to a feature called “edit” without committing that old versions were guaranteed to be removed/buried by all relays.
The internet archive, library of congress, poltiwoops, and others all archived tweets and refused to delete them. I’m sure twitter doesn’t actually delete a tweet from all of their databases and logs either. But you could still delete them from your timeline and that’s a valuable and important feature. Being able to signal that you want this event removed and that most people will honor it is what’s needed.
We might even put a warning up when users in nos start using a relay that doesn’t support delete, so users are aware. Yes the can lie. But we can do some checks. Look at relays, attempt to request events that your peers deleted or set expiration timestamps on, and then rate them as untrustworthy if they continue to serve those events.
For me one of the big advantages of nostr over scuttlebutt is the ability to request deletion.
enjoyed all of these perspectives. thanks gents 🍻
