No thanks, I’d rather use a Google Pixel with GrapheneOS
Image transcription:
buy privacy-first community driven phone look inside closed source OS with no recovery image and outdated dependencies
No thanks, I’d rather use a Google Pixel with GrapheneOS
Image transcription:
buy privacy-first community driven phone look inside closed source OS with no recovery image and outdated dependencies
Making an operable phone would be (relatively) easy enough. The trouble comes with trying to make it compatible with all the apps and app stores out there, because people expect their phones to be able to download and run various apps that every other phone can. Sometimes they need it to.
The apps are a solved problem. It’s the other way around. Getting a phone or tablet with an soc that has mainline Linux support is hard. It takes forever for all that stuff to settle in mainline and manufacturers will not help.
The apps are far from a solved problem. Otherwise, alternative mobile OSes would not have such a hard time, even if you look beyond mainline Linux. The issue are banking and ID apps, which can work but also may not work.
They can work. They are designed not to. Because there are philosophical differences over what kind of access each should have.
Websites still work. You don’t need an app. You need a bookmark.
I know that the could work. But that is a philosophical distinction if they don’t work. You preach to the wrong guy. I removed all these banking and ID apps from my daily driver because I don’t see why I should put that kind of stuff on my phone to begin with but I am a minority. Banking apps require the app, bookmarks won’t cut it and yes they don’t work because some banks (not all mind you) don’t want them to work which makes no difference to the end user though.
We do need an open security standard and then the only way how we could break out of the duopoly is by the EU forcing companies to use that open standard, at least additionally to the US based solutions. That would break the duopoly.