←back to thread

401 points Bluestein | 1 comments | | HN request time: 0s | source
Show context
stiray ◴[] No.44363735[source]
I am still waiting for Fairphone and Graphene OS collaboration. This is match made in heaven.

Any Fairphone/GrapheneOS developer reading this? Just do it, document if something is not secure enough for you, but do it. Nothing to think about, you fit together like hand and a glove and any seconds thoughts are depriving the planet of THE PHONE!

Pick the cash we will throw at you and make second generation with the cpu GrapheneOS wants, that will make the /r/GrapheneOS members eyes shine, drooling and crying of joy at the same time. +throw them in a few hardware switches for camera, mic, connectivity,... disabling. No need to wait to be perfect in first iteration (and due to that craziness and perfectionism will never happen), to gain the possibility to be perfect in second or third.

I would love so much to stop buying Google Pixel phones just to install Graphene OS and protect myself from Google and its ecosystem, it seems so counterproductive.

replies(4): >>44363775 #>>44363839 #>>44364179 #>>44364441 #
WhyNotHugo ◴[] No.44364441[source]
I recently suggested that GrapheneOS support devices with average security on Mastodon. Much like yourself, I think "moderately okay security" is better than "just use Google's spyware infested OS".

The GrapheneOS folks replied in disagreement, insisting that this is a terrible idea because security would be less than perfect. They then started making up stories about me and throwing around unfounded accusations. I don't trust them in the slightest, and strongly recommend staying away from them.

replies(4): >>44365722 #>>44366110 #>>44380726 #>>44380887 #
1. agile-gift0262 ◴[] No.44366110[source]
> I recently suggested that GrapheneOS support devices with average security on Mastodon. Much like yourself, I think "moderately okay security" is better than "just use Google's spyware infested OS".

For most use cases, like mine, I agree. But I understand GrapheneOS disagreeing with that statement. "average security" is not their goal, nor the use case they are working for. GrapheneOS' focus is security. They just happened to make the best AOSP version there is out there. So lots of us wish they better support our use cases disregarding the use case they work for. But they obviously don't want to spend resources on it, and I'd assume they wouldn't even accept extra resources to do those things, as it would dilute their "most secure mobile OS" brand by having less secure versions of it.

For those of us who don't need the best security, another fork of AOSP that incorporates many of the features GOS has, like sandboxed Google Play and contact and storage scopes would do. But we can't expect GOS to be the one doing that.