nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqm4a3pdnk9z900h96563pgngwe7udxa96yy645q3ueq2gjsdyknxqxmx9z3 (nprofile…x9z3) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqtva8g98fx0fks0pt38vr75tv02t30qd5ev7n5v7fcpl6t44hf7kq5fm8mr (nprofile…m8mr) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqlykvmmzx8nerkm7qmequkxdj6e2s3xlqqppgl7xf6ekajkj27u5sgvplv4 (nprofile…plv4) Ok there. I'm not affiliated with either /e/ or Graphene. I am currently using an old Oneplus5T running Lineage with MicroG, but full disclosure: I just got my hand on a brand new Pixel 8a tonight, and as soon as it is charged, it will get Graphene.
Example of privacy oriented feature I'm looking forward to use:
Scopes (Contacts, Storage): I use some proprietary apps, and I will be able to restrain their ability to go through my contact list and all data on my phone.
That's one example of one thing you can say about Graphene vs /e/: in /e/, allowing an app to access Contacts give it an unlimited access to all of your contacts, same idea for storage. In Graphene, they access what I will let them see. And no, I can't just not grant permission: some apps will refuse to work if not given the full permissions package.
Now, I agree that repeating over and over that XXX is insecure and is bad for privacy doesn't give anyone the slightest idea about what's wrong with XXX. And the linked comparison table between Android distros is all but straightforward for the vast majority of users and the amount of entries is overwhelming.
(What the hell is PSDS/XTRA? Which of these lines are relevant to my use case??).