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.

Reply to this note

Please Login to reply.

Discussion

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.