[mbjdesign]

I think they’ll regret more than the confusion they’ve caused after the dust settles. Regardless of the security and privacy implications of their changes and how I feel about those; I have never associated Apple with CSAM more than I do now, and I’m sure it’s the same for many others that have been following this story.

The “think of the children” might have been a good wedge if their long term agenda involves expanding this kind of scanning, but it’s creating some strong ties between CSAM and their usually very “clean” brand.

If their aim was to comply with their reporting requirements and demonstratively prove that this kind of content can’t hide within Apple’s ecosystem (a huge advantage in many peoples eyes) then surely they should have opted for the least controversial option? From reading comments, I think very few would have pushed back against comparing image hashes on their servers after upload, even if that became a blocker to E2EE - that we don’t have, and might not ever get anyway.