summaryrefslogtreecommitdiff
path: root/static/faq.html
diff options
context:
space:
mode:
authorDaniel Micay <danielmicay@gmail.com>2021-06-13 04:08:54 -0400
committerDaniel Micay <danielmicay@gmail.com>2021-06-13 04:08:54 -0400
commitec352372ce4aa312aa1f720b67a470db778026fa (patch)
tree3bffd4eff035c10358aa3c61fd6f7c8e0c53aa53 /static/faq.html
parent1fa6cc2a2507da63f6f0cf12abcaf5426f208c3a (diff)
stop linking no longer planned feature
Diffstat (limited to 'static/faq.html')
-rw-r--r--static/faq.html28
1 files changed, 13 insertions, 15 deletions
diff --git a/static/faq.html b/static/faq.html
index cc41d023..8aa4081d 100644
--- a/static/faq.html
+++ b/static/faq.html
@@ -967,22 +967,20 @@
<article id="ad-blocking">
<h3><a href="#ad-blocking">How can I set up system-wide ad-blocking?</a></h3>
- <p>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
- <a href="#custom-dns">choosing a Private DNS (DNS-over-TLS) server</a> with support
- for blocking ad domains. As an example, AdGuard DNS can be used by setting
- <code>dns.adguard.com</code> as the Private DNS domain. In the future, GrapheneOS
- plans on adding back <a
- href="https://github.com/GrapheneOS/os_issue_tracker/issues/184">an efficient
- user-defined blacklist for the local DNS resolver</a>. 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.</p>
+ <p>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
+ <a href="#custom-dns">choosing a Private DNS (DNS-over-TLS) server</a> with
+ support for blocking ad domains. As an example, AdGuard DNS can be used by
+ setting <code>dns.adguard.com</code> 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.</p>
- <p>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.</p>
+ <p>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.</p>
</article>
<article id="ad-blocking-apps">