Add a "Common misconceptions" section

[codenyte]

Consider adding a section to some part of the website, for example the FAQ, or creating a new page specifically meant to address the most common myths and misconceptions about GrapheneOS. These could easily be shared in social media/forum/chat room discussions, in order to prevent the spread of false information about the project.

Some good examples are:

• "Notifications aren't working properly"
  -> Battery optimization needs to be disabled for Google Play Services, in order to prevent the background process from getting killed, to ensure that push notifications via FCM can always be delivered
• "Google Pay isn't supported"
  -> GrapheneOS supports all technical aspects required for Google Pay to work. The only reason it doesn't work, is because Google doesn't allow it, because they use a strict whitelist approach for OS compatibility.
• "GrapheneOS doesn't pass Play Integrity Attestation because it's insecure"
  -> GrapheneOS is considerably more secure than the Stock Pixel OS and basically every other Android-based OS. The purpose of the Play Integrity API is not to protect the end user, but rather to protect Google's monopolistic business interests.

I believe this is a very important step in the constant battle against misinformation and harassment, and could significantly help the project tackle these issues.

[thestinger]

We have an FAQ section for notifications already:

https://grapheneos.org/faq#notifications

[codenyte]

The "Common misconceptions" section could also include links to other parts of the documentation on the website. I still think it's important to address these myths directly, otherwise misinformed users will spread them, damaging the project and its reputation.

[jermanuts]

@thestinger You said yourself it is a good idea tho

https://x.com/GrapheneOS/status/1857482073855889907

https://xcancel.com/GrapheneOS/status/1857482073855889907#m

EDIT: There will be no problem with adding such topics to the site, instead of searching through X's terrible search functionality for tweets relevant to a topic, as long as it is well written, without a harsh tone or direct attacks on any projects, etc. Also, any claims should be backed up with sources and clear.