Yes, unfortunately. It’s their con, but also their pro at the same time. It’s bad because they end up isolated from everyone else playing nice with each other, and then no one wants to deal with them, but they also don’t agree on compromises that might hinder security or the stability and development of their project. And I respect that. That is partly a reason why they created probably the most secure and private AOSP distrubution nowadays.
They can, but it’s not their goal. Their goal is to have control over 99% of Android phones produced and not let their users install adblock or NewPipe, or torrent app or whatever.
There’s GrapheneOS that I think would try to address this problem — secure, proper architecture, compatible with some major app stack (e.g. Android apps). It’s AOSP-based, but they’re already thinking ahead up to a point where they would be forced to fork it and even work with OEMs to create their own phone hardware for it. There are a couple of threads on their Mastodon.
I don’t know how much they would be able to achieve, but I would pay for such system.
This. And obviously to ban all the things like adblockers, NewPipe, custom browsers, etc that give people any kind of relief from Google’s digital slavery.
It has nothing to do with KeepassXC, it’s still early development and you won’t be able to backup or extract your passkeys because it stores them in the hardware secure element on the phone (if it’s available), but it works: https://git.noisruker.de/Juhu1705/open-passkey-authenticator
Dude, that’s a pizza cutter…
Well, the answer to that question is extremely easy: “no one” :)
But that’s a nice article, thanks for sharing.