madaidans-insecurities.github.io VS Armada

Recommend reading the Linux sections on https://madaidans-insecurities.github.io/

That's somewhat telling and can be used to "track" you, consider reading on non-Reddit privsec learning resources like Privacy Guides itself which you already know, PrivSec.Dev, madaidan's Insecurities and the like.

Considering the offer is legitimate (something I won't comment on), you shouldn't do most of these things, in my opinion. Don't mess with what'll be other people's phones. Sell them Pixels pre-installed with GrapheneOS and print papers with Auditor attestation instructions and maybe a few QR codes directing them to relevant documentation and privsec learning resources, such as the GrapheneOS documentation first and foremost, Privacy Guides, madaidan's Insecurities, PrivSec.dev, Seirdy's Home, Wonderfall's Lab, etc...

i never used it myself. only learned about it from security experts like madaidan or hardening guides like this one.

For some excellent advice on security and privacy based on thoroughly researched technical concerns rather than speculation or blind trust in your corporation of choice, see here: https://madaidans-insecurities.github.io/

Similarly there exist systems for giving formal assurances about concurrent C code, but that's not something the language itself offers.

Even there it depends. 'Programming practices' is vague. Even C can be tamed, at great expense, using formal methods techniques. [0][1][2][3] Adoption of such methods can give a solid assurance of the lack of UB, like use of a safe language. Weaker measures, like adopting MISRA C, don't provide such strong assurances (although they can eliminate certain categories of errors), and as you indicate, their real value is a bit more subjective. Mandating a bad programming style could actively make things worse.

[0] https://trust-in-soft.com/

[1] https://www.eschertech.com/products/perfect_developer.php

[2] https://github.com/microsoft/Armada

[3] https://www.microsoft.com/en-us/research/project/vcc-a-verif...