4 ms·
Both statements are correct--for now. It runs locally on device for photos synced to iCloud. Presumably it's a slow boil: they'll make it run on all photos in a
by CGamesPlay 5y ago
Both statements are correct--for now. It runs locally on device for photos synced to iCloud. Presumably it's a slow boil: they'll make it run on all photos in a year or so, once the press from this one has blown over.
- shishy 5y agoThanks (to you and the other responders) for clarifying; that makes sense. Bit of a shame... I wish it just sat elsewhere on their server before cloud syncing and then I could just disable cloud sync + use the phone without worrying.
- jnwatson 5y agoThere's the rub. I think folks would feel better about if Apple-owned equipment was doing the scanning, even though arguably it is worse for privacy.
- notJim 5y ago> Presumably it's a slow boil: they'll make it run on all photos in a year or so, once the press from this one has blown over. What is the basis for this assumption?
- tick_tock_tick 5y agoHistory....
- notJim 5y agoBut this move matches Apple's current stance on backups. They have access to iCloud backups, but do not have access to local ones. This has been the case for a while now. This mirrors the situation with iCloud photos. In other words, maintaining the privacy of non-synced photos would be consistent with their previous stance on local backups.