He had a delete script, too, that ran on nostr-tool, but it doesn't work right now.
I can just download the full nostr.watch API list, like he did and run through it. Didn't want to do that, if I can avoid it, as it spams everyone's relays, but oh well.
I did mine in batches of 256, so I sent fewer than 50 queries to each relay. That shouldn’t bother relays. If it does, we have a bigger problem.
Here’s my script if you want to compare it to what you wrote.
https://gist.github.com/SamSamskies/0088e7a14f3df37550c796481b54d0fe
Just upped it to 1000 per batch. Heh. YOLO, baby.
I did 256 cause I think some relays have that cap on event tags or at least they used to
I think everyone upped it because of follows. 😅
That name! 🤣
That was the hashtag I used for the nukening of my old profile and notes. I think @liminal was the only one that noticed me do this. 😂
Here's how I get around using blastr. I looked where he gets the relay list from. He just uses the API from Nostr.Watch.
```
// download a list of active relays
$url = "https://api.nostr.watch/v1/online";
$page = file_get_contents($url);
$requestedRelays = json_decode($page, true);
sort($requestedRelays);
```
From the results, it looks like some of the relays are rejecting notes from npubs without a valid NIP-05.
It’s possible they don’t have the note to delete then. If they do, just add a nip-05 on the npub. Once you’re done deleting the notes, you can remove the nip-05 or just nuke the kind 0.
They probably don't have it, since I never had a NIP-05 on that npub and haven't used it in half a year.
Just thought it was interesting that not having a NIP-05 might prevent you from persistently deleting your own events.
Oddbean new post about login | logout