4 ms·
Are we going to need to reverse engineer every single Apple update to make sure the feature hasn't creeped into non-iCloud uses? Is the inevitable Samsung versi
by sigmar 5y ago
Are we going to need to reverse engineer every single Apple update to make sure the feature hasn't creeped into non-iCloud uses? Is the inevitable Samsung version of this system going to be as privacy-preserving? How are we sure the hash list isn't tainted? All of these problems are solved by one principle: Don't put the backdoor code in the OS to begin with.
- slg 5y ago>Are we going to need to reverse engineer every single Apple update to make sure the feature hasn't creeped into non-iCloud uses? Did we do this already? If not, why did we assume this didn't exist previously? >Is the inevitable Samsung version of this system going to be as privacy-preserving? I don't see how this is Apple's fault. Be angry at Samsung for their system. I don't blame Snap if I have a problem with Instagram Stories. >How are we sure the hash list isn't tainted? How did we know the hash list wasn't tainted when doing this comparison on Apple's servers? >All of these problems are solved by one principle: Don't put the backdoor code in the OS to begin with. Apple controls the hardware, software, and cloud services. The backdoor didn't need to exist in the OS for there to be a backdoor.
- sharken 5y agoAt this point it will be the OS without on-device scanning that wins for me. It's amazing that Apple is still thinking about moving this idea forward, but they must think they are untouchable and can do what they want. And it adds insult to injury that two very different images can generate the same NeuralHash value.