Replying to Avatar ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ

now i think about it, i think i need to extend that feature to tombstone the replaced ones as well, so they don't get resurreted after deleting the newest version

i also have to account in there for the time of the delete so the tombstones can eventually be pruned off after a substantial time passes (like 6+ months)
Avatar
ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

oh yes, i also needed to mention that it keeps and will return the kind 5 delete events as well, these also can be removed after a time as part of the garbage collection process

still more things to get right, right now on that project i'm building out a follow/mute list based access control system that makes it really easy to control access to relays without making any new interface

Reply to this note

Please Login to reply.

Discussion

Avatar
jimbocoin 🃏 1y ago

IMO, you can’t safely prune the kind=5 delete events* because your relay could later receive again the event that was supposed to have been deleted.

* unless you know that the previously deleted event had a created_at stamp that’s outside the relay’s retention policy window.