3 ms·
What a strange concern. Sending hashes of images as you take them to a remote server is very easy to do in any OS update, if they really wanted to betray their
by infotogivenm 4y ago
What a strange concern. Sending hashes of images as you take them to a remote server is very easy to do in any OS update, if they really wanted to betray their customer base's privacy expectations like that.
IMO the more logical guess as to the actual reason Apple wants to do this - to approach e2e encrypted iCloud photos in a LE-friendly way.
- philistine 4y agoThe thing is they never announced e2e iCloud photos with the new process. So we could presume, but I honestly believe they never intend to give it to us.
- hamandcheese 4y agoiCloud backups are not e2e encrypted, though. And I don’t think anyone was suggesting that Apple would secretly betray users. The concern is normalization of the notion of on-device scanning before (publicly) expanding the scope to all images.
- j16sdiz 4y agoIf are talking about the whole device backup, Most of it are encrypted with your phone unlock pin or recovery code. Only iMessages (iirc) are not e2ee.
- infotogivenm 4y agoI was not suggesting this either... And yes, iCloud backups if you choose to use them are mostly not e2e encrypted (some important bits like iCloud keychain etc aside). In any case, I think this concern of yours is unfounded, as echoed by many in the other comments below, and you should rethink it before continuing to push it. The amount of scanning has not changed since the invention of corporate image hosting on the internet; you still cannot use iCloud to host known illegal content - they just moved where the scanning takes place. I don't see how this makes it any more likely or normalized to scan your non-iCloud photos.