4 ms·

Unfortunately, "Trust me bro, they care" isn't good enough. Database corruption can't explain how the photos can return to an iPad after wiping, if the encrypt

Unfortunately, "Trust me bro, they care" isn't good enough. Database corruption can't explain how the photos can return to an iPad after wiping, if the encryption key has been changed as their documentation claims. Unless the photos are actually linked to the device and not the actual account, which would be stupid and not how they described it works... or if it isn't encrypted at all - also not how it was marketed/described to work. A pathetic one-line non-explanation for such a giant bug, that doesn't even align with the facts of what actually happened, is not congruent with the actions you'd expect from a company that cares about privacy. They need to make a statement explaining how that could happen, and what they've done to prevent it happening again.

khazhoux 2y ago
> A pathetic one-line non-explanation for such a giant bug, that doesn't even align with the facts of what actually happened, is not congruent with the actions you'd expect from a company that cares about privacy. I disagree. External statements are guided by legal and comms departments (along with Engineering of course, but eng never has final say on what goes out). External statements don't necessarily have any relation to how things are being handled internally. And this fuck-up (assuming it's as described) also doesn't reflect whether the eng team made a genuine best effort to ensure full privacy. Teams make mistakes, even huge ones. From personal experience, the biggest bugs come from the smallest root cause -- that single typo in a single file that somehow snaked a narrow path through every test on the production pipeline. Now, is Apple working hard to fix this? I have no idea. All I know (and my original assertion) is that when I worked there not long ago, privacy was genuinely a Very Big Deal that was a top (often the top) company-wide north star.
- brokenmachine 2y ago
  So privacy is (was?) the highest priority, but when there's a massive privacy failure, the legal and comms departments will say anything that denies liability, regardless of the veracity or facts of the matter. Got it.

khazhoux 2y ago

> A pathetic one-line non-explanation for such a giant bug, that doesn't even align with the facts of what actually happened, is not congruent with the actions you'd expect from a company that cares about privacy. I disagree. External statements are guided by legal and comms departments (along with Engineering of course, but eng never has final say on what goes out). External statements don't necessarily have any relation to how things are being handled internally. And this fuck-up (assuming it's as described) also doesn't reflect whether the eng team made a genuine best effort to ensure full privacy. Teams make mistakes, even huge ones. From personal experience, the biggest bugs come from the smallest root cause -- that single typo in a single file that somehow snaked a narrow path through every test on the production pipeline. Now, is Apple working hard to fix this? I have no idea. All I know (and my original assertion) is that when I worked there not long ago, privacy was genuinely a Very Big Deal that was a top (often the top) company-wide north star.

brokenmachine 2y ago
So privacy is (was?) the highest priority, but when there's a massive privacy failure, the legal and comms departments will say anything that denies liability, regardless of the veracity or facts of the matter. Got it.