News for hackers. Stuff that matters.
Re:Android 13 requires devices to have more than 2GB RAM and... by hamandcheese on Saturday September 10, 2022 @03:23AM (#32788608)
The only reason to design a system like Apple’s is so that it is impossible to opt out of once it is rolled out to non-iCloud photos.

iCloud photos are not e2e encrypted. If only iCloud photos were the true final target, there is absolutely no need for on-device scanning.

Re:Android 13 requires devices to have more than 2GB RAM and... by JimDabell on Saturday September 10, 2022 @07:20AM (#32789632)
> The only reason to design a system like Apple’s is so that it is impossible to opt out of once it is rolled out to non-iCloud photos.

This doesn’t make any sense because this system cannot be rolled out to non-iCloud photos. They would have to redesign how it worked. So the whole idea that Apple designed it this way for reasons that only kick in when it’s rolled out to non-iCloud photos is incoherent. If Apple were designing it for that purpose they would have picked a design that actually worked in those circumstances.

Re:Android 13 requires devices to have more than 2GB RAM and... by hamandcheese on Saturday September 10, 2022 @01:32PM (#32792701)
What about the design makes this only possible for iCloud? The scanning occurs on device. What limits it to only iCloud photos?
Re:Android 13 requires devices to have more than 2GB RAM and... by JimDabell on Sunday September 11, 2022 @01:04AM (#32796978)
Well it’s quite clearly integrated into the iCloud system. Why would you think that it works for local photos without iCloud?

A known CSAM photo gets added to photos on an iPhone with iCloud disabled – what happens next? What do you think is the mechanism for that getting reported?