You can easily see that this person was welcomed in the rooms. No one went against it and the CalyxOS developers started going along with it.
>They'd also be used on GrapheneOS, and anywhere else basically. The issue is that you're giving Google services privilege and integration not available to other apps.
No, giving criticism of an OS is not attacking it. You'll see that strcat only responded to places where GrapheneOS was mentioned. You'll see that there was misinformation being spread about GrapheneOS, whether…
See grapheneos.org/history/copperheados and verify it for yourself using Github graphs and other resources. A better description would be "One person handled development of the project and other person CEO'd the sponsor…
>How can you claim that we're the ones shipping proprietary service integrations when we ship an open source implementation, and you're the ones shipping an integration for the proprietary implementation. Play Services…
He's not "the GrapheneOS developer", he's the lead developer and one of many developers. It's a collaborative open-source project which has made a production-grade OS and whose contributions have been upsteamed for AOSP.
Pixels are pretty much the only Android phone that supports full verified boot with custom keys, meaning verified boot of the entire base system works no matter what OS you're booting (as long as your OS supports…
By that definition, Linux, Chromium, and lots of other software isn't Google-free. But that's ridiculous. Android does not contain any tracking code, and at most uses Google servers as the default for network…
And if you flash a good custom OS like GrapheneOS, maybe LineageOS without microG, then Google doesn't track you even if you use their hardware. Even better if you use a secure OS like GrapheneOS or standard AOSP…
Not giving Google a few hundred dollars (or if you buy a used phone, $0) isn't going to hurt them.
You can easily see that this person was welcomed in the rooms. No one went against it and the CalyxOS developers started going along with it.
>They'd also be used on GrapheneOS, and anywhere else basically. The issue is that you're giving Google services privilege and integration not available to other apps.
No, giving criticism of an OS is not attacking it. You'll see that strcat only responded to places where GrapheneOS was mentioned. You'll see that there was misinformation being spread about GrapheneOS, whether…
See grapheneos.org/history/copperheados and verify it for yourself using Github graphs and other resources. A better description would be "One person handled development of the project and other person CEO'd the sponsor…
>How can you claim that we're the ones shipping proprietary service integrations when we ship an open source implementation, and you're the ones shipping an integration for the proprietary implementation. Play Services…
He's not "the GrapheneOS developer", he's the lead developer and one of many developers. It's a collaborative open-source project which has made a production-grade OS and whose contributions have been upsteamed for AOSP.
Pixels are pretty much the only Android phone that supports full verified boot with custom keys, meaning verified boot of the entire base system works no matter what OS you're booting (as long as your OS supports…
By that definition, Linux, Chromium, and lots of other software isn't Google-free. But that's ridiculous. Android does not contain any tracking code, and at most uses Google servers as the default for network…
And if you flash a good custom OS like GrapheneOS, maybe LineageOS without microG, then Google doesn't track you even if you use their hardware. Even better if you use a secure OS like GrapheneOS or standard AOSP…
Not giving Google a few hundred dollars (or if you buy a used phone, $0) isn't going to hurt them.