3 ms·

This has always been the case when uploading something to the cloud unencrypted. You never had any privacy in the first place.

by selsta 5y ago

vineyardmike 5y ago
But this isn't uploaded to the cloud. Its your device.
- axoltl 5y ago
  It’s only done to pictures that you’re about to upload to the cloud.
  - torstenvl 5y ago
    A claim that can't be independently verified by the owner of the device. Apple isn't exactly known for software transparency or allowing software that monitors iOS internals.
    - nicce 5y ago
      With that argument, how do you know that Apple hasn't been doing this already for years? You either fully trust Apple and use their devices, or not.
      - vineyardmike 5y ago
        Now we know that the technology is built, so while we don't know what they use this for, they've told us they have it and its used for something. Its not hard to assume they'd be less vocal about future changes.
  - vineyardmike 5y ago
    The point is that its done on our end, not apple's end. Many reasons this is bad. Obviously the "Slippery slope" argument around it scanning more in future and being abused by the state. There is the possibility that its exploited/bug that sends data when it shouldn't or falsely reports you (not a collision). Eg. a bug that reports all photos as bad instead of listening to results of scan. Obviously the possibility of collision sucks. But thats somewhat constant across implementation options. It wastes your CPU resources and network resources to do something that only benefits apple. It's a bad precedent because other companies will likely do this now, repeated the above arguments with increasingly less trustworthy companies.
    - nicce 5y ago
      Bugs are kinda slippery slope arguments as well, since they are impossible to prevent or measure with 100% accuracy. These are stopped in human review. (Hopefully) It seems that this system might be extremly resistant for collision to prevent them ending up to human review. https://news.ycombinator.com/item?id=28305946 https://news.ycombinator.com/item?id=28305946 > It wastes your CPU resources and network resources to do something that only benefits apple Okay, how practical is this problem? iCloud already scans your files to know whether they are need to be synced. And this scan applies lesser times, only once before upload per file. Encryption does not mess with the filesize, so we are talking about few bytes of extra metadata per image here. Regular image with raw format is tens of megabytes.
      - vineyardmike 5y ago
        > Okay, how practical is this problem? Mobile phones operate off battery and can be very important tools for safety and navigation. Every wasted minute of battery is important. > Encryption does not mess with the filesize No but giant bloom filters take storage.
    - snet0 5y ago
      Only benefits Apple?

This has always been the case when uploading something to the cloud unencrypted. You never had any privacy in the first place.

by selsta 5y ago

This has always been the case when uploading something to the cloud unencrypted. You never had any privacy in the first place.

vineyardmike 5y ago

But this isn't uploaded to the cloud. Its your device.

axoltl 5y ago
It’s only done to pictures that you’re about to upload to the cloud.
- torstenvl 5y ago
  A claim that can't be independently verified by the owner of the device. Apple isn't exactly known for software transparency or allowing software that monitors iOS internals.
  - nicce 5y ago
    With that argument, how do you know that Apple hasn't been doing this already for years? You either fully trust Apple and use their devices, or not.
    - vineyardmike 5y ago
      Now we know that the technology is built, so while we don't know what they use this for, they've told us they have it and its used for something. Its not hard to assume they'd be less vocal about future changes.
- vineyardmike 5y ago
  The point is that its done on our end, not apple's end. Many reasons this is bad. Obviously the "Slippery slope" argument around it scanning more in future and being abused by the state. There is the possibility that its exploited/bug that sends data when it shouldn't or falsely reports you (not a collision). Eg. a bug that reports all photos as bad instead of listening to results of scan. Obviously the possibility of collision sucks. But thats somewhat constant across implementation options. It wastes your CPU resources and network resources to do something that only benefits apple. It's a bad precedent because other companies will likely do this now, repeated the above arguments with increasingly less trustworthy companies.
  - nicce 5y ago
    Bugs are kinda slippery slope arguments as well, since they are impossible to prevent or measure with 100% accuracy. These are stopped in human review. (Hopefully) It seems that this system might be extremly resistant for collision to prevent them ending up to human review. https://news.ycombinator.com/item?id=28305946 https://news.ycombinator.com/item?id=28305946 > It wastes your CPU resources and network resources to do something that only benefits apple Okay, how practical is this problem? iCloud already scans your files to know whether they are need to be synced. And this scan applies lesser times, only once before upload per file. Encryption does not mess with the filesize, so we are talking about few bytes of extra metadata per image here. Regular image with raw format is tens of megabytes.
    - vineyardmike 5y ago
      > Okay, how practical is this problem? Mobile phones operate off battery and can be very important tools for safety and navigation. Every wasted minute of battery is important. > Encryption does not mess with the filesize No but giant bloom filters take storage.
  - snet0 5y ago
    Only benefits Apple?