Apple, the privacy-as-product company of the earlier FBI standoff, announced it would scan photos on-device for child-sexual-abuse material before iCloud upload, using perceptual hashes matched against a known-CSAM database, with human review past a threshold. The backlash from the security community was immediate, near-unanimous, and not about the target (nobody defends CSAM): it’s about the architecture, client-side scanning builds the searching machinery into the device, and the machinery cannot know what database it matches against (today CSAM hashes from NCMEC; tomorrow, any government’s “terrorist content” list, with compliance leverage Apple has already demonstrated bending to in China). The FBI-standoff principle returns inverted: Apple argued then that a capability built for good guys can’t be contained; critics now quote Apple’s own brief back at it. The file’s read: the cryptographic design is genuinely clever (threshold secret-sharing, safety vouchers, the engineers did careful work); the policy architecture is the vulnerability, and “we would refuse such demands” is a promise, not a mechanism (the AUP lesson: capabilities outlive intentions; the sword you forge is the sword that exists). Apple is already in visible retreat under the pressure — clarification FAQs, hastily scheduled briefings — and the file expects a formal pause within weeks. The precedent debate, where does content-matching belong: device, transit, or cloud, is now permanently open, and every E2E messaging platform’s future runs through it.

The fortnight’s crypto absurdity, filed for range: the Poly Network hack, $600M+ drained via a cross-chain contract flaw, the largest DeFi theft ever, resolved with the attacker returning essentially everything, conducting an interview-by-embedded-transaction-notes, claiming it was “for fun” and to expose the bug, and being offered a $500k bounty by the grateful (?) protocol. Code-is-law jurisprudence currently operates at the maturity level of a pirate ship electing its quartermaster (the forever-bugs file: immutable code, negotiable everything else).

TIL: perceptual hashing (NeuralHash) mechanics. Researchers are already extracting the model from iOS betas, and the file pre-registers the obvious: synthetic collisions within the month. Any classifier deployed at civilizational scale becomes an adversarial target at civilizational scale (the confusion-matrix politics; the Tay clause, your users are your red team, forever).