zlacker

>>joseph+(OP)
This story with restricting users is a similar one to Manifest V3 in Chromium.

But we don't have anything like FF as an alternative to go from Android. Especially considering banks require "certified OS".

>>zx8080+E7
I switched to a Linux smartphone because I've had enough of the duopoly.

I also switched banks so I can use my bank card as the 2FA device, similar to CAP. [0]

[0]: https://en.wikipedia.org/wiki/Chip_Authentication_Program

>>Hackbr+Wd
Which one?

>>russne+7h
It’s a Librem 5. I’m looking for a more powerful model that can also run mainline(-ish) Linux.

>>Hackbr+si
Seeing as GrapheneOS appear to be recommended on the newest Pixel models, I wonder if it shouldn't be too difficult to get Arch Linux running on them with the AUR plasma-mobile?

>>russne+9k
Run away from Graphene, it is suspicious at best scenario and dangerous at worst.

Just observe that the key factor is to be independent from Google and then the only recommended devices from their side are exactly google devices where nobody here can have an idea of what is modified inside them.

You'd be better off supporting other distributions like Calyx, which have no problems in supporting other devices like the fairphone and so on.

>>nunobr+gl
No, the "key factor" of GrapheneOS is to provide a secure OS on a secure hardware. If the "key factor" was to be independent from Google, they wouldn't support Google devices at all. But since the Pixel phones are the only ones with secure enough hardware, GrapheneOS supports them.

They even tell you in their usage guide that it's more secure to use Google's app store than e.g. F-Droid (which neglects several good security practices for an app store), and that it's not a good idea to blindly aim for "degoogling" at all costs.

Go away with your baseless FUD.

>>pferde+zn
> it's not a good idea to blindly aim for "degoogling" at all costs

Why not ? This seems to be exactly the push that was needed.