ok so i have been thinking lately that you can do better than just getting other clients to respect an author-initiated delete. you can disavow data and put anyone still peering that data on notice, helping to identify bugs in clients ("hey friend i noticed your peer hasn't dropped from that thing i deleted") and bad actors. in http-land that's hard to do, but it's simple when all your data lives in torrents linking to torrents.
re: thinking about decentralized social media
@darius yeah i started thinking about it when i read the source on how cabal peers do backchannel comms to do handshakes, using a hypercore archive like a meeting point. in the same way an author-peer, having disavowed an archive, can instruct other peers to stop peering / drop cluster or be considered noncompliant. i need to write up the architecture, it's a doozy to try and fit in my head.