5 ms·
Apple PR is clearly working overtime trying to spin this as a "misunderstanding" and "confusion".
by paxys 5y ago
Apple PR is clearly working overtime trying to spin this as a "misunderstanding" and "confusion".
- boardwaalk 5y agoAre they wrong? It seems like most people don’t understand that Apple was already scanning iCloud Photos on their servers like Google scans Google Photos, they’re just going to be doing it client side now. I’m not defending Apple, I wish they wouldn’t do this, but I see section 230 levels of lack of understanding out there.
- UseStrict 5y agoWhy move it on-device then? They've made no announcement or attempt to encrypt iCloud backups, so they are free to keep scanning on their servers. Moving it on-device has zero value-add for iPhone users, it only serves as a Trojan Horse for any future "scanning" projects that they may adopt, willingly or otherwise.
- boardwaalk 5y agoI wasn’t commenting on the why. I’m just saying that all the words in the phrase “Apple regrets confusion” are probably true: There is a lot of confusion, and Apple’s PR is probably really regretting it right now. If people understood what was going on, would they be as upset? I don’t know. Apple doesn’t seem to think so.
- UseStrict 5y agoI think the point is people do understand - and are still upset.
- notJim 5y agoThey actually weren't. They wanted to start, and they thought this way of doing it was more privacy-friendly. Craig says all this, but apparently listening to what he says is forbidden.
- boardwaalk 5y agoI didn’t see that. Do you have a link? I only was able to find Jane Horvath (Apple Chief Privacy Officer) saying they were already scanning photos using PhotoDNA at CES 2020 [1]. [1] https://www.engadget.com/2020-01-07-apple-facebook-ces-privacy-panel.html https://www.engadget.com/2020-01-07-apple-facebook-ces-priva...
- notJim 5y agoThis article just says "iCloud," not specifically Photos. My understanding is that they previously scanned iCloud Mail, but not iCloud Photos. I don't have a link handy unfortunately, and don't have time to dig it up again.
- nix23 5y agoWhy then do it on the device when you can do it on the backend with much less publicity and constantly updating it? >but I see section 230 levels of lack of understanding out there. Mirror mirror on the wall....
- boardwaalk 5y agoIf you have an example of my lack of understanding, please show it to me. Also, your snark is below this forum.
- insulanus 5y agoThere was a lot of confusion. Caused by Apple trying to slip this feature under the radar, and omitting information.
- OrvalWintermute 5y agoLet us hope a rollback on this bad idea will remedy the confusion
- system2 5y agoI bet you my life it will not happen.
- Animats 5y ago"Sow confusion, and reap inaction" - common military tactic. If what you're doing is too big to hide, you also cause visible activity in multiple places, so the enemy can't decide where to send reinforcements. The Normandy invasion had quite a bit of that. The enemy was confused for days about where the main attack was hitting, and didn't commit reserves until it was too late.
- notapenny 5y agoIt's sadly typical of their apologies. The "I'm sorry you feel that way" apology. As a long time customer its beginning to annoy me. You fucked up. Say "we fucked up" and move on.
- tgsovlerkhgsel 5y ago> Say "we fucked up" That would require them actually changing their plans though, and it doesn't seem like they're willing to do that (yet).