Conversation

This Tweet was deleted by the Tweet author. Learn more

Replying to

and

> the most degoogled AOSP version on the market AOSP doesn't have Google apps and services in the first place. GrapheneOS is a privacy/security research and engineering project, not a "degoogling" project. I think you're confused about what the project develops and provides.

Replying to

and

I ain't confused. I love the idea behind the project. Not being a developer, I'm worried about is google phone and google's power to plant something on a hardware level. Another question. How can I contribute to the project?

Replying to

and

> Not being a developer, I'm worried about is google phone and google's power to plant something on a hardware level. I don't understand your tunnel vision focus on Google. There are a bunch of companies involved in manufacturing any given smartphone. Foxconn assembles them.

Replying to

and

What kind of hardware is it you want supported that would make you feel better? I can't think of anything that would be more trustworthy, and anything else would offer less privacy/security. So far, no one has even identified another device with non-broken support for other OSes.

9:02 AM · Feb 21, 2020Twitter Web App

Replying to

and

It doesn't appear that there are going to be many options suitable for GrapheneOS. Custom hardware would be nice, but there are still going to be a bunch of trusted parties involved in manufacturing components along with the manufacturer. It would mostly be a reference design.

Replying to

and

A benefit of custom hardware would be for GrapheneOS to have control over SoC firmware, which would reduce attack surface and allow lower-level hardening. It would be possible to make some changes improving hardware security but it would be difficult just to match Pixel security.

Show replies