the federal government has long had hesitance to hold figures like presidents, senators, and supreme court justices to account, and this is just an extension of that.
Because if they start holding others in similar offices to account, they might have to hold themselves as well, and that ain’t happening.
Not really weird. It’s a survival thing. He wants you to watch over him while he’s vulnerable and eating.
I said “average PC,” and you throw out Linux with a hardened browser. That’s not average. But how many people have Linux with a hardened browser? More importantly, how easy is that to set up compared to setting up GOS (I promise GOS is much, much easier to set up and use)?
But if we’re going with extremes like this: no one should use banks on Linux with hardened browsers. Just go in person.
I’d bet that a GrapheneOS phone is more secure than your average PC.
Not sure what you mean by “jailbreak” as that’s rarely a term applied to Androids. On the phone side, you have to have a Pixel (6 and up are recommended due to increase security and longer support) and enable OEM unlocking, which requires no hacking/jailbreaking/rooting. It’s super easy to install.
I did acknowledge what you said by saying Google doesn’t want Graphene not including GMS stuff and won’t whitelist GrapheneOS, despite Graphene’s extra security measures. But this doesn’t change the fact that Google could…but won’t.
Per GrapheneOS, they do not and will not support Fairphone 4. No clue if Fairphone 5 has fixed these issues.
https://www.reddit.com/r/GrapheneOS/comments/10b5x4n/comment/j67pbny/
I’m not being deliberately deceptive. Google absolutely could whitelist GrapheneOS if Google chose to, just like any app developer can as well by checking for the verifiedBootState with proper verifiedBootKey (GrapheneOS attestation link below).
Now, I don’t see Google doing that as GrapheneOS doesn’t and won’t ship with Play Store, Play services, or Service Framework. GrapehenOS actually has a compatibility layer so those don’t get special and device wide privileges like they do on devices that ship with them (sandboxed link below)…which Google probably requires. And I don’t see GrapheneOS budging on this as that’s one of their main selling points for security and privacy.
But I’m always down to learn and I’m not a developer. I don’t suppose you have a link that says the main thing that Graphene is missing is handing over money to Google to get certified, and ideally how much? If that was it, I’d be willing to bet money Graphene would’ve forked over the cash by now.
https://grapheneos.org/articles/attestation-compatibility-guide
That’s a single person on a project with multiple contributors. He’s also since stepped down. You’re acting like he’s the sole guy.
https://discuss.grapheneos.org/d/5235-stepping-down-as-project-leader-of-grapheneos
Depends on how you use your phone. Main thing I miss is Google Pay’s tap to pay (disabled by Google unless you run a Google certified OS…which Google could easily certify Graphene but won’t), but most banking apps NFC tap to pay work.
Android Auto also doesn’t work, but I never used it. Some people might, though.
What’s the big deal? Was he found innocent, like he says he is? Cool, release it. Something something if he has nothing to hide.
Or was he found guilty? Cool, release it.