The guide is well tested and verified, and can be implemented by anyone, and so it can be tested as well. If the guide had issues, I would not be doing months of testing and publishing such a guide.

Again, as I have said many times, GrapheneOS itself is probably a fine custom ROM, but the developer’s vision is not exactly the best and I have plenty criticisms of it that many people tend to agree on. And the community is unhelpful and toxic, and everyone knows that well. This is enough to understand that there is almost no ROM support for its end users if they need to ask questions, because it will be considered “spam” and “petty trolling” and “character assassination” and whatever buzzwords GrapheneOS and PrivacyGuides admins/mods come up with.

Telling the less technical masses about how big bad bloody war it was to develop a feature that is essentially controlling app package permissions and working around Android System’s location module is very, very cheesy. I must admit, the advantage taken of masses’ ignorance here is exemplary. chef’s kiss

The purpose of the guide has been achieved largely, and will be achieved even further. My aim was to destroy privacy elitism and gatekeeping and the mentally taxing paranoia, and the popular notion among ordinary people that achieving great privacy, security and anonymity requires custom ROMs, not using any common apps, rooting, insane technical knowledge and lots of time investment. Ordinary people can enjoy same benefits as the “privacy elitists” without losing their minds and participating in cult worship of “privacy elitists”. (Oh, BTW here is a little bonus, I work with people that are far more “experts” than these two weird communities, including both people who actively use and who have stopped using GrapheneOS and have Pixels. And we do not like people messing around with privacy community.)