> It's not like any other device meets their ridiculous standards either
I don't think it's ridiculous to want the ability to relock the bootloader, for instance? Do you realise that if you cannot do that, you just break the whole Android security model right away?
It's a reasonable extrapolation of the current state. They want up to date patches, Google is already winding down open support for that, and it'll release in what, a year or two? Basically guaranteed to have outdated security patches on launch or they'll have to start maintaining their own. Might happen, but it seems unlikely they can hack it, as it were.
There are devices meeting these basic standards right now, and the entire family of them, no less.
GOS are vocal about safety and security of all the devices, not just seriously insecure Fairphones, and this article is about something different altogether, that's misinformation they've been hit with several times.
Fair criticism is fair, but yours is fabrications.
A problem I see is that GrapheneOS has a history of being extremely blunt about the shortcomings of alternatives, and of course alternatives (and users of alternatives) don't like getting that feeling that maybe they have been compromising on... something.
At least that's how I felt when I starting reading more after a few years of using /e/OS on my Fairphone 3. And the more I read, the more I realised that GrapheneOS was usually technically correct (their communication used to be a different story, but recently I feel like it has become a lot more professional, focusing on the technical side).
Really, the vast majority of technical criticisms I see against GrapheneOS are misinformed. I'm not saying that the commenters purposely say lies. Just that it all is technically non-trivial, and I totally understand that most people don't really understand how the Android security model works, for instance.
All that to say: I don't think that there is hypocrisy on the GrapheneOS side. They are very consistent on what they are trying to do.
At the moment there is no other hardware manufacturer making similarly secure android phones.
*NONE*
There is no android hardware coming close. If there is, please name it. As far as I know it's only some unspecified, upcoming Motorola flagships.
If you call the unwilling, pragmatic choice an "intense hypocrisy", it's pretty clear to me you're simply driven by emotions and tribalism, that the facts don't matter.
Are you saying that using Google hardware equals using stock Google os?
You must be a little more.... Coherent with your metaphors :)
> It's not like any other device meets their ridiculous standards either
I don't think it's ridiculous to want the ability to relock the bootloader, for instance? Do you realise that if you cannot do that, you just break the whole Android security model right away?
> neither will their own Motorola whenever they get around to actually making it
Source: You made it up
A quick search would basically disprove everything after your first sentence.
It's a reasonable extrapolation of the current state. They want up to date patches, Google is already winding down open support for that, and it'll release in what, a year or two? Basically guaranteed to have outdated security patches on launch or they'll have to start maintaining their own. Might happen, but it seems unlikely they can hack it, as it were.
[flagged]
There are devices meeting these basic standards right now, and the entire family of them, no less.
GOS are vocal about safety and security of all the devices, not just seriously insecure Fairphones, and this article is about something different altogether, that's misinformation they've been hit with several times.
Fair criticism is fair, but yours is fabrications.
[flagged]
A problem I see is that GrapheneOS has a history of being extremely blunt about the shortcomings of alternatives, and of course alternatives (and users of alternatives) don't like getting that feeling that maybe they have been compromising on... something.
At least that's how I felt when I starting reading more after a few years of using /e/OS on my Fairphone 3. And the more I read, the more I realised that GrapheneOS was usually technically correct (their communication used to be a different story, but recently I feel like it has become a lot more professional, focusing on the technical side).
Really, the vast majority of technical criticisms I see against GrapheneOS are misinformed. I'm not saying that the commenters purposely say lies. Just that it all is technically non-trivial, and I totally understand that most people don't really understand how the Android security model works, for instance.
All that to say: I don't think that there is hypocrisy on the GrapheneOS side. They are very consistent on what they are trying to do.
2 replies →
At the moment there is no other hardware manufacturer making similarly secure android phones.
*NONE*
There is no android hardware coming close. If there is, please name it. As far as I know it's only some unspecified, upcoming Motorola flagships.
If you call the unwilling, pragmatic choice an "intense hypocrisy", it's pretty clear to me you're simply driven by emotions and tribalism, that the facts don't matter.
Are you saying that using Google hardware equals using stock Google os?
You must be a little more.... Coherent with your metaphors :)
3 replies →