What about a tool to send delete requests to all known relays except a specified list? #asknostr Or actually this would require a nip change... So the delete can specify relays that don't have to delete. #nostr #dev I know I want to clean up my relay list and I want to tell a bunch of old relays I don't want them storing my notes any more but I want to keep them on my new list.
Discussion
No need for a new nip, that is done by the client, but any delete request it's not guaranteed that it is done.
You do need a nip for what I'm suggesting. As it stands a kind5 would tell all relays to delete that note. It's not selective.
You just send the delete request to the relays you want and don't send to the one you don't want, but either way, you don't control anything about deletes.
If the ones you don't want still receive the request, (which is likely because clients are supposed to broadcast them when a relay signals they don't have a deletion request when they should) they would delete them when you don't intend for those relays to delete them.
I'm well aware, I made a relay implementation from scratch in go.
Or I can draft up a change to Nip9
Why have relays delete at all? Someone is just going to run a scrapper at some point and redistribute them back out
That doesn't mean we shouldn't implement delete at all. Also, deletion events are broadcast everywhere and relays store them.
Yeah but most relays will only store them for so long so if a bot is just going around rebroadcasting the original events it could reseed the network after the delete event gets purged. Speaking of purge where does purge rank on GRAIN's todo?