GrapheneOS hat eine neue Sektion auf der Website hinzugefügt: Eine Liste von Apps, die explizit die Nutzung von GrapheneOS über die Play Integrity API blockieren, inklusive Links zu den entsprechenden Play Store-Seiten. 👇
https://grapheneos.org/articles/attestation-compatibility-guide#apps-banning-grapheneos
#grapheneos #android #google
@[email protected]
I’m aware of the fact, that almost all app form the Play Store or Aurora store do have one or more tracker build-in. For this reason I self-host a Adguard Home server and my phone is connected via DoT to this server. It’s unbelievable how many crap is filtered every day.
@[email protected] Those DNS filter lists that you’re using are designed to only block connections to domains not used for anything other than ads or tracking. They deliberately do not block connections to dual-use domains needed for real functionality. That heavily limits what can be done that way. If they did block everything used for tracking then a whole lot of mainstream apps would not work anymore so it wouldn’t be usable or truly useful. Protecting privacy from apps requires permission controls.
@[email protected] Android’s permission controls are not good enough. Apps force you to give media, storage and contacts permissions to use them. iOS has solutions for that and so do we. We’re in the process of adding more of these features for Location (to replace global Mock Location), Microphone, Camera and Phone. This is crucial for privacy. You cannot achieve privacy blocking some connections from the client while still allowing apps to connect to their servers and from there share with any 3rd party.