How can I set up system-wide ad-blocking?
-The recommended approach to system-wide ad-blocking is setting up domain-based
- ad-blocking as part of DNS resolution. You can do this by
- choosing a Private DNS (DNS-over-TLS) server with support
- for blocking ad domains. As an example, AdGuard DNS can be used by setting
- dns.adguard.com as the Private DNS domain. In the future, GrapheneOS
- plans on adding back an efficient
- user-defined blacklist for the local DNS resolver. This feature used to be
- included by the project many years ago, but it needs to be reimplemented, and it's a
- low priority feature depending on contributors stepping up to work on it.
The recommended approach to system-wide ad-blocking is setting up
+ domain-based ad-blocking as part of DNS resolution. You can do this by
+ choosing a Private DNS (DNS-over-TLS) server with
+ support for blocking ad domains. As an example, AdGuard DNS can be used by
+ setting dns.adguard.com as the Private DNS domain. This feature
+ used to be included by the project many years ago, but it needs to be
+ reimplemented, and it's a low priority feature depending on contributors
+ stepping up to work on it.
Apps and web sites can detect that ad-blocking is being used and can determine - what's being blocked. This can be used as part of fingerprinting users. Using a widely - used service like AdGuard with a standard block list is much less of an issue than a - custom set of subscriptions / rules, but it still stands out compared to the default - of not doing it.
+Apps and web sites can detect that ad-blocking is being used and can + determine what's being blocked. This can be used as part of fingerprinting + users. Using a widely used service like AdGuard with a standard block list is + much less of an issue than a custom set of subscriptions / rules, but it still + stands out compared to the default of not doing it.