zlacker

>>kotaKa+(OP)
Please consider using GrapheneOS. If it gets more momentum and users it's the only option pushing back at these tactics.

>>mapper+GP2
GrapheneOS only supports Google Devices, are you serious?

>>tcfhgj+KR2
The point is that GrapheneOS will continue to allow the sideloading of Android apps (and Google cannot do anything to prevent that).

Just because Google has been generous enough (or inattentive enough) to allow Pixel devices to run alternative OSes is not a reason to avoid GrapheneOS. Also, the Graphene project is in discussions with a manufacturer to produce a non-Pixel phone running GrapheneOS.

>>holler+4S2
Well, there are other smartphone manufacturers which support using alternative operating systems.

And there are other AOSP derivatives which aren't restricted to Google devices.

Why would you buy a Google device as a response to Google restricting user freedom?

>>tcfhgj+Rj3
One reason is that Graphene has much better security than any of the other AOSP derivatives.

I seem to recall that Graphene's leaders maintain that Pixels are more secure when running Graphene than any other smartphone would be (when running Graphene), which is not surprising given how good in general Google is at security compared to other large tech companies.