|
|
|
|
|
by 28220968
1772 days ago
|
|
Can someone explain this to me -- The whole premise is that Google and Facebook and everyone else are just doing this on the unencrypted photos you upload, in their cloud, with their own (presumably, but correct me if I'm wrong) undocumented algorithms and datasets. Now here comes Apple, documenting almost everything except the dataset itself, and everyone is freaking out because it's happening on your own device. But then it's encrypting the whole thing and uploading it to Apple where they presumably do no additional scanning. What is the actual difference if it's being looked for on-device vs. by the provider? Supposedly in preparation for a bigger push of encryption of the photos themselves, if they are not already encrypted in the cloud. Am I missing something more than "but it's happening on-device!"? |
|
Also, it's actually pretty easy to mess with Android and get it un-googled. Google don't make most Android phones, so there's less hardware-level enforcement of rules, and more independent alternatives. This is less so for Apple devices. If Apple decides to do something you don't like to your phone, you are SOL; you can only accept it or ditch Apple and switch to Android/something else.