They chose to create requirements in which the only option was the Google Pixel. Its completely their choice. They could have had different the requirements, but they didn’t.
Yes, like airplane manufacturers could have less stringent requirements for the materials with which they build their planes, doesn’t make it a good idea.
I don’t know why the language surrounding this debate always gets twisted. GrapheneOS wants to continue following their own requirements which point to Google Pixels only, more than they want to open up and support other platforms, some more ethical/moral, open, and not crafted by a company directly opposed to their goals.
So your argument is to lower security requirements so they can provide a less secure system in favour of more phone options.
To what end ? Their whole schtick is maximum security possible, there are plenty of alternatives if you want less security (for a given idea of security).
Lowering their security requirements is also directly opposed to their goals, so what is it that you are suggesting as a solution?
It sounds like you know the answer so stop complaining around it and just tell us.
They would have to lower standards in order to support a different phone. That’s the whole point. They’re not sticking it to anyone. Just trying to provide as secure of an OS as possible.
You’re not understanding. It has to do with specific hardware features not available elsewhere. The latest snapdragon SoC will support memory tagging and what-not. Previous generations did not. This isn’t some shitlib corpo looking to make a dollar.
Yes, like airplane manufacturers could have less stringent requirements for the materials with which they build their planes, doesn’t make it a good idea.
So your argument is to lower security requirements so they can provide a less secure system in favour of more phone options.
To what end ? Their whole schtick is maximum security possible, there are plenty of alternatives if you want less security (for a given idea of security).
Lowering their security requirements is also directly opposed to their goals, so what is it that you are suggesting as a solution?
It sounds like you know the answer so stop complaining around it and just tell us.
I made no such argument. My comment plainly explains my issue with the language around this discussion. It doesn’t take a side nor propose a solution.
That’s fair, you were just complaining about something for which you have no constructive input…
right up until you hit this part.
That’s a clear indication of a position, “more ethical” (correct or otherwise) implies an opinion on relative morality.
The general statement is a whole lot of speculation, but that’s the only part that veers in to actual sides.
Feel free to reply to any of the rest of the reply, or just continue to ignore it, that works as well.
You should simply read my words rather than read something into them.
You are free to disprove my statements.
When a significant portion of its merit relies on something I already replied to, then there is no need.
They would have to lower standards in order to support a different phone. That’s the whole point. They’re not sticking it to anyone. Just trying to provide as secure of an OS as possible.
so, if googledaddy makes changes that no longer allow Graphene to be installed on Pixels, what option do they have?
and if you seriously think that Motorola won’t roll over for a google contract, you’re just lying to yourself.
google has perceived Graphene and all ASOP forks as serious competition, that’s why they are locking boot down.
Does Debian consider Ubuntu to be a competitor?
This is a strange argument. I’m not sure where you’re wanting to go with it.
It’s a pretty big deal that the snapdragon SoC will meet the requirements for a reasonably secure OS.
so, if googledaddy makes changes that no longer allow Graphene to be installed on Pixels, what option do they have?
not much, that’s a large part of the original post…no ?
Oh , absolutely , motorola will capitulate at the slightest sniff of anything touching their bottom line.
Except that some context around security is threat model. There are people who view it as a significant security issue to be using Google hardware.
Security cannot so simply be boiled down to a one dimensional axis of more or less secure.
You’re not understanding. It has to do with specific hardware features not available elsewhere. The latest snapdragon SoC will support memory tagging and what-not. Previous generations did not. This isn’t some shitlib corpo looking to make a dollar.
Evidently it’s not for you. Move on.
None of what you said addresses my statement about threat model.