Kevin Karhan 
I still think that #GrapheneOS should not chain themselves to a single vendor but rather release actual proper specs for support.
- Otherwise we'll continue to see lazy ripoffs / rebadgings of their #ROM / #Android - #distro instead.
I also doubt that #Motorola will release any affordable device with @GrapheneOS support.
- And I'm not even talking about their ≤€250 retail budget phones they neglect and refuse to update, but rather anything in the ≤ €500 price bracket.
- Pretty shure only ≥ €1k devices will get any chance of that, making it even more classist.
And unlike @tails_live / @tails / #Tails dropping #32bit support amidst the fact that there are almost no #32bitOnly machines that can run it, I don't see the benefit of trusting into an unauditable blackbox of a "#SecurityChip".
- I'm shure @stman could run entire semester-long classes at a university explaining why this blatant violation of #KerckhoffsPrinciple is irredeemably bad, but I digress…
GrapheneOS (@[email protected])
@[email protected] GrapheneOS has an official long term partnership with Motorola and will support many of their future devices, not one. It will support multiple new Motorola devices every year. We aren't lowering our security requirements but rather their devices are being improved to meet our requirements. The reason GrapheneOS won't support their currently available devices is because those don't meet our security requirements. Currently, only Pixels meet our requirements. https://grapheneos.social/@GrapheneOS/116159602850585685
matthew - retroedge.tech
Andrea Instone
bjb 
Daniel
Areeb Soo Yasir
jose
Rex Banner
arnoldmelm