From 1e29e59e13d470df43873d36b0a02f1d2ba68033 Mon Sep 17 00:00:00 2001 From: Gerd Date: Tue, 6 Feb 2024 12:23:24 +0100 Subject: [PATCH] Updated FAQ (markdown) --- FAQ.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/FAQ.md b/FAQ.md index a68d3fc..8ed0b4e 100644 --- a/FAQ.md +++ b/FAQ.md @@ -4,5 +4,5 @@ Network-wide blocking of CMPs (Consent Management Plattform/Provider) used for cookie consent solutions breaks a lot of things and takes away the user's freedom to decide what he wants to allow and what not - blocking usually allows everything ([#1979](https://github.com/hagezi/dns-blocklists/issues/1979#issuecomment-1870498567)). -Blocking or automatic allow/deny is reserved for content blockers with corresponding filter lists. These can be used to decide which sites are excluded from blocking CMP domains and which are not. You only have to look at the exclusions in the known cookie filter lists to see why network wide blocking via DNS is not a good idea. +Blocking or automatic allow/deny is reserved for content blockers with corresponding filter lists. These can be used to decide which sites are excluded from blocking a specific CMP domain and which are not. You only have to look at the exclusions in the known cookie filter lists to see why network wide blocking via DNS is not a good idea.