So I’m going to do an experiment. I’ve posted an event:5 post requesting relays delete / drop an earlier post of mine and stop replicating it. Some people weren’t happy with my disparaging their religious holidays. There’s no need to leave that up. So let’s use this an experiment to see how delete requests work today in reality.

https://github.com/nostr-protocol/nips/blob/master/09.md

Reply to this note

Please Login to reply.

Discussion

I had a feeling that post was going to end up being a test case for post deletion 🙂

The prophet one?

Yep.

I still see it. I broadcasted it through mutiny relay so it should’ve went to about 300 relays.

You broadcasted the original post or the event:5 delete request?

The original

That does bring up a good point, it's hard to 'see' a delete event in most clients, and it probably does need to be broadcast more widely than most events.

That’s what I’m thinking too. Would be interesting to see what happens if the deletion event is sent through a blastr relay.

Where's the blastr url.. i'm only finding the code to setup my own with cloudflare...

wss://nostr.mutinywallet.com

I think #[7]​ made a microapp for this

Not sure if you’ve seen this. I wrote it recently for a bounty.

https://cdn.nostrgraph.net/public/delete.html

The GitHub version has a couple extra features to load your relays. https://github.com/blakejakopovic/nostr_delete

Yep. Shared it somewhere in this thread.

It has the mutiny blaster relay in the default list. In practise I’ve found it doesn’t reach 300 relays.. it’s closer to 30-40. Maybe rate limiting, ip blocks, dead relays, not sure specifics.

#[8]

Also. From around 80-90 relays being aggregated, here is which relays at least saw your deletion event.

https://api.nostrgraph.net/beta/events/9d0da9ce8d33da90a55cb8a7598c7f7b579093e9c945a11f7d6812fafacb29b7.json?pretty=true

And lastly.. here is a timeline of the original event. Deletion isn’t shown.. maybe I should add :)

Yeah the delete message seems worth adding… ;-D

Done. In purple.

Nostr graph is super helpful. I like the way it gives me the files via a DM after confirmation.

Thanks. It’s a few months old now, before browser extensions and relay AUTH.

I chose the chatbot approach to prevent DDOS, and downloading others people’s events - mostly DMs and deleted events. It works well, and is backed by my event driven backend - so adding more bots is easy.

I still see it also. #[5]​ and I were talking about creating a new image, note-image that will look like regular text, but you can delete (since it is an image). The user would toggle a button, and what they type is screen-shot when ‘posted’, and the screenshot is posted, that can later be deleted…. Just an idea.

Yes, the assumption #[5]​ temporary image approach is that a CDN or other automated or manual service or process does not auto-copy the image elsewhere from the original host.

There is also local client caching, which likely varies from client to client.

From the experimenting I did with a few hosts;

- If you saw the image-note and I deleted it, you would still see it on your device until it’s local cache was deleted.

- If you had never seen the note, and it was deleted, you never will see it

If you could get your hands on extra spare android phone, you can Delete straight inside Amethyst client (wasn't sure if you were aware)