oh, you are entirely out of luck if you want to know about relays that actually implement delete, as far as i know, almost none do

blasting out delete events for your entire event set would work, where it is honored, you have to gather the entire set of event IDs to do it, for good reason there is no blanket delete ability in delete events

Reply to this note

Please Login to reply.

Discussion

Well, there is the NIP PR for a blanket-delete, but it's permanent.

it's a stupid idea

it's a big red button with a flimsy shield around it that malicious parties will use to harass users with when the client has a vulnerability

Well, Vitor needs it for some particular health application, for compliance. 🤷🏻‍♀️

yeah, i think GDPR or whatever acronym shit from the EUSSR

it's a nice feature but it is just a query strategy and follow that up with a set of delete events crafted from the IDs

i forgot the third one

https://youtu.be/3UDa6o6zsUE

literally three of my all time favourite music artists all converged on this one subject

i will say though, that Snog was 10 years ahead of them both, muse and combichrist only did theirs during the lockdowns, when the word was very hot

David Thrussel lives in Hellstralia where they do everything 10 years before the rest of the world, or even sooner

this track from combichrist is really more in the vein of Icon of Coil though... and i don't understand what the inverted crosses in the video are about, some hipster shit

this is again a muddled-domain architecture issue

like nip-86, this is mostly stuff that can be done with existing data structures or interfaces, or is at the level of the database or relay service provision tooling

i also have to be careful with muddling domains up, i can't emphasise enough the importance of respecting domains and not crossing the lines between them because almost all bugs and vulnerabilities come from it