not that i know of, we should really be sending DMs with expiration tag set
Built a (basic) CLI tool, https://github.com/f321x/nip04-wiper, seems like a bunch of relays ignore the delete request though.
neat script ! i don't see a specific reason why they'd ignore it, it looks correct to me but i guess some relays are just really shitty about that they'd ignore expiration tags for sure, too
There is definitely a narrative that nostr event should be permanent which I guess some relays enforce. Guess that's the most "delete" we can get😃
it won't be that way forever... something i want to do with my relay is have it actually propagate delete events when it receives them so everyone who might actually do it can find out it is requested
This sounds very useful, i also imagine part of the problem is just getting the delete event distributed. For now I used a blaster relay but they also only send to the X biggest relays. Would be cool if clients would rebroadcast important events like delete too.
it's that kind of "everything must be permanent" blockchain mindset that held me back from even trying nostr for a long time it makes sense for public declarations and publishing, but not for day to day private life social media stuff, and even less so for DMs
some relays literally don't have it implemented it requires some extra pieces to work, you have to keep tombstones of the event id to prevent it coming back, and that necessarily implies an eventual need for garbage collection in general and yeah... expiry... i'd implement that on my relay if i knew of a client that i want to use that has it, because that's a cool feature, especially for DMs... it can also function like a dead-man switch too, as part of a system to enable stale follow npubs to be removed (because those damn follow lists seem to be like ratchets, only going in one direction, bigger, because if people don't post they don't see and don't think of deleting