3 ms·
FWIW Microsoft already does this for photos you store on OneDrive: https://www.theregister.com/2014/08/07/ms_tip_off_child_abuse_arrest/ https://www.theregister
by oakfr 5y ago
FWIW Microsoft already does this for photos you store on OneDrive: https://www.theregister.com/2014/08/07/ms_tip_off_child_abuse_arrest/ https://www.theregister.com/2014/08/07/ms_tip_off_child_abus...
- oauea 5y agoThat's great but irrelevant. This discussion is about scanning them locally on your device.
- oakfr 5y agoIndeed. Thanks for pointing this out. Scanning on device is a different story.
- deleted 5y ago[deleted]
- zimpenfish 5y agoWell, it's semi-relevant, isn't it? Because it's only scanning photos that are being uploaded to iCloud Photos - they've just moved the scanning portion down one level. If your photos never go to iCloud, they won't be scanned.
- cageface 5y agoSo what's the point of doing this client side then? It seems like they're deliberating paving the way for doing this on all client side material.
- zimpenfish 5y ago> So what's the point of doing this client side then? Not a clue. Maybe they're going to make iCloud Photos fully E2E and this is the only way they can keep the CSAM scanning alive? Or maybe they just want to avoid it arriving on their servers at all (but I don't think anything has said matching CSAM photos will not be uploaded?) Or they just want to save some CPU on the iCloud side by punting that down to the phones themselves? (Or, yeah, this is just the precursor to doing more client-side scanning and the slippery slope cassandras will be proven correct.)