From a20e4467169b6ed8df9e34898482108b14e999bf Mon Sep 17 00:00:00 2001
From: yokoffing <11689349+yokoffing@users.noreply.github.com>
Date: Wed, 12 Oct 2022 11:15:49 -0400
Subject: [PATCH] Update README.md
---
README.md | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/README.md b/README.md
index 6a0d53a..8bd3d53 100644
--- a/README.md
+++ b/README.md
@@ -125,6 +125,13 @@ Here's a compliation of popular blocklists available in NextDNS:
:bulb: The **Balanced** tier is recommended for the average user, based on my testing and user feedback.[1](https://old.reddit.com/r/nextdns/comments/s2gzc5/oisd_vs_1hostsminiliteproxtra/hsgmp5n/) [2](https://old.reddit.com/r/nextdns/comments/xoyyw2/nextdns_as_a_set_it_and_forget_it_solution/iq1k6tx/) [3](https://old.reddit.com/r/nextdns/comments/vuon2a/one_profile_for_lan_devices_another_profile_for/iffegc5/?context=2) [4](https://old.reddit.com/r/nextdns/comments/vn8olr/please_could_someone_recommend_me_a_good/ie5meel/?context=2)
+:radioactive: You will see many [blocklists in NextDNS](https://github.com/nextdns/metadata/tree/master/privacy/blocklists) and around the web.
+- Some block too much
+- Some block too little
+- Some block everything, including what's needed for functionality
+- A small few are actively maintained and remove false positives
+ - Filtering out false positives is paramount for a good blocklist
+
### Native Tracking Protection [1](https://github.com/nextdns/metadata/tree/master/privacy/native)
Add all the device brands that you use. There's no advantage in adding brands you don't have; however, there’s no disadvantage in adding unused brands, either.