if the relay honors it, and damus doesn’t honor it, then damus is simply behaving badly.

damus is disrespecting the user at that point

Reply to this note

Please Login to reply.

Discussion

If the relay honours it then the note won’t appear in damus, what is the problem ?

The argument I’m making is that calling it delete is a lie, so i will not implement delete. I may implement it as “request delete”. But damus will not pretend it’s deleted when it’s not .

So if I post my toe pics on here I won’t be able to rug people by deleting them after they zap me?

You can delete the image from where it is being hosted

Or change it so it looks like they zapped something really weird...

Now that’s funny

I respect and agree with not generating kind 5s. just a thought, maybe there is a way to display a kind 5 generated else where, sure there is more to pull down, and make sure that gets rebroadcast.

I could imagine an alternate system, where a user who does want to publish on a private relay, or delicate a certain relay to be their confirmation publishing house, where a user could request a check that the note is still “in print”. Maybe wouldn’t want to include that check in damus to remain light weight. Just throwing ideas around.

lol * delegate

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.

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?