(Replying to PARENT post)

Sorry to be a pedantic but: Two People created CopperheadOS, one of them now works on GrapheneOS. The security mitigations developed for those were incorporated upstream into Android, decreasing the attack surface.
๐Ÿ‘คscns๐Ÿ•‘4y๐Ÿ”ผ0๐Ÿ—จ๏ธ0

(Replying to PARENT post)

> Two People created CopperheadOS, one of them now works on GrapheneOS.

No, that's not true. GrapheneOS is the continuation of the project by the original development team. There aren't any developers who stuck with Copperhead. The project was created 1 year before Copperhead existed as a company.

https://grapheneos.org/history

> The security mitigations developed for those were incorporated upstream into Android, decreasing the attack surface.

https://grapheneos.org/features is a list of the current features differentiating it from AOSP. It doesn't list the many things we've gotten into upstream projects, since they aren't differences anymore.

๐Ÿ‘คstrcat๐Ÿ•‘4y๐Ÿ”ผ0๐Ÿ—จ๏ธ0

(Replying to PARENT post)

If I find an exploit in Chrome and I send a patch to Google, it doesn't imply that single handed I can manage the security of a Chrome fork.
๐Ÿ‘คhfkfktnekfm๐Ÿ•‘4y๐Ÿ”ผ0๐Ÿ—จ๏ธ0