Replying to @⁨Resonosity@lemmy.dbzer0.com⁩

I can’t see how that is possible without compromising on their security requirements. The hardware isn’t the problem here, that could be overcome, the extremely rapid firmware updating reqirement is. That needs huge resources, hence they are using so far a device from the huge comoany behind the Android ecosystem. Already Motorola, another huge compaby is stretchung that requirement, as tgey are not sitting at the source of that ecosystem.

Again, I am not defending GrapheneOS’ choice, just describing their dilemma

Replying to @⁨exu@feditown.com⁩

Short-sighted goal in my opinion. They could be the leader in privacy for smartphones from the bottom up, including hardware and software.

GOS’s work with Motorola might just lead Motorola to be that group as they always have for decades, so my issues might go away anyways.

Just getting arrogant, self-isolating vibes when they have soooo much good will with the tech community on building privacy from the ground up in some of the most important intelligent devices in our lives.

Why can’t GOS join a working group with ISO or IEC or IEEE or other groups to create roadmaps and tiers of compliance so that other manufacturers have means and methods of approaching GOS’s lofty goals.