Wait.

If the relay honors delete, then the client has nothing to display because the event is deleted, no?

If there is something to display then it’s not deleted.

Isn’t it more “disrespectful” for a client to say your data is deleted when it actually isn’t? You know like our data harvesting Big Tech services?

Maybe I’m not seeing the big deal here.

Reply to this note

Please Login to reply.

Discussion

There could just be a delete micro-app where you give it a note id and it send the delete requests. Putting “delete” into the app is just way too misleading imo. Users will expect it to work the same as centralized delete, but it’s fundamentally different.

I like this idea and it’s trivial to build. I’d actually be surprised if it didn’t exist already…

😂 exactly

https://nostr-delete.vercel.app

It does have a faq explaining that deletes are best effort. The template engine just has this hidden.

Welp that was fast!

It was a Nostr bounty that Fiatjaf set. And a way for me to learn Svelte :)

Really cool little app! Nice work on the simple UX of it 👏

Beauty of Nostr

It's not just a client issue. The user also needs to check their relays implement NIP-09.... not all do.

you’re confusing permanence with a lack of user control of their own data. nostr does not guarantee permanence nor ephemerality. you just hand your data over to nodes and they do whatever they want with it.

hopefully this will push people to realize the pointlessness of unencrypted notes and encrypted will become the default.

posting is just a “request” too though. and it also does not work like centralized posting.

damus doesn’t know if any relay will honor *any* request, right? why is a delete request special in this regard?