Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I don't know how you can include "Apple" and "privacy" in the same sentence without some kind of source code to back it up.


How does source code backs Google privacy claims?

AOSP so different than even Google own pixel phones it's code is basically irrelevant.


It's an option. AOSP isn't identical to OEM-distributed ROMs, but it's certainly a great basis for private OSes like CalyxOS and GrapheneOS. For individuals that are serious about privacy, there aren't any options to compile your own iOS with Apple services disabled.

I'm not saying that the AOSP absolves all of Google's server-side behavior (or even that it proves they're benevolent; neither company is). My point is that Google presents a realistic threat model to their users, that takes them seriously and even provides escape hatches for any potentially concerning features. iOS presents a comparatively cartoonish outlook that relies more on the strength of their marketing than the self-evidence of their security. Apple's position is indefensible but claims to be altruistic; Google's position is honest, so much that it treats themselves as a threat.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: