Oddbean new post about | logout
▲ ▼
elsat | 9 months ago (raw) | root | parent | reply | flag +2 
 Rabble and co are doing a job in convincing me as well. I like the term retract.

Allow me to challenge. 

A unique characteristic about nostr relative to twitter is that the note lives on in one or more relays, and local client databases.

So if a note has been published across various machines, and we are optimizing for user choice, should the nostr user on the receiving end of the note have the option of honoring (or not) deletion requests?
▲ ▼
UCantDoThatDotNet | 9 months ago (raw) | root | parent | reply | flag 
 https://image.nostr.build/547df7e725fee5046afce4d8b588d1ed0ee46030601577098e0f3414025a9126.png
▲ ▼
frphank | 9 months ago (raw) | root | parent | reply | flag +1 
 Your ambitions to be a North Korean dictator are kind of cute but in the real world the user decides what choices they have.
▲ ▼
angela | 9 months ago (raw) | root | parent | reply | flag 
 I think that’s what occurs, @rabble correct me if I’m wrong. @elsat I’ve used the delete feature on @nos.social and it’s worded in such a way that the relay owners are being asked to delete the note. Based on the current wording, it doesn’t sound like nos is promising (nor would
It make sense that they could promise) the relays will actually delete it. 

To that end though, I think it’d be cool if there were a way to let the requestor know which relays didn’t choose to delete as requested. It would help the requestor determine if they want to continue to use that relay or not; keenly if it’s one they pay into.
▲ ▼
elsat | 9 months ago (raw) | root | parent | reply | flag +2 
 Yes, if you assume clients don’t store notes long term, then it comes down to relay choice.