Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need Blocklist recommendation #1516

Closed
Krishna-art-dev opened this issue Sep 2, 2023 · 13 comments
Closed

Need Blocklist recommendation #1516

Krishna-art-dev opened this issue Sep 2, 2023 · 13 comments
Assignees
Labels
question Further information is requested

Comments

@Krishna-art-dev
Copy link

What is your recommended Blocklist for most of your user

@Krishna-art-dev Krishna-art-dev added the question Further information is requested label Sep 2, 2023
@hagezi
Copy link
Owner

hagezi commented Sep 2, 2023

My recommendation:

Normal + TIF - If you have no access to the logs and no admin is available to unblock. E.g. in the wider family or for grandma and grandpa.

Pro +TIF - If logs are available and someone is there who can unblock (very rare).

Gerd ;)

@relvinarsenio
Copy link

relvinarsenio commented Sep 2, 2023

If using the light version only, what do you think?
Do you still recommend it for daily use?
@hagezi

@Krishna-art-dev
Copy link
Author

And what's the difference between pro and pro++

@hagezi
Copy link
Owner

hagezi commented Sep 2, 2023

If using the light version only, what do you think? Do you still recommend it for everyday use? @hagezi

Compared to the Light, the Normal also blocks a few more trackers, pop-up ads and more malware domains. I see no reason not to switch from the Light to the Normal, unless you use the Light because of its smaller size.

But I would combine any list, no matter which version, with the TIF if possible.

@Krishna-art-dev
Copy link
Author

If using the light version only, what do you think? Do you still recommend it for everyday use? @hagezi

Compared to the Light, the Normal also blocks a few more trackers, pop-up ads and more malware domains. I see no reason not to switch from the Light to the Normal, unless you use the Light because of its smaller size.

But I would combine any list, no matter which version, with the TIF if possible.

Nextdns TIF is same as yours? Because nextdns doesn't have your TIF in blocklists

While in other hands adguard dns have your TIF and Normal Blocklist

So which dns server you gonna recommend for using nextdns or adguard. if nextdns's TIF is like yours I think then nextdns is better it have your pro Blocklist and and list so have choices

@hagezi
Copy link
Owner

hagezi commented Sep 2, 2023

And what's the difference between pro and pro++

https://github.com/hagezi/dns-blocklists#proplus:

"More aggressive version of the Multi PRO blocklist. It may contain few false positive domains that limit functionality. Therefore it should only be used by experienced users. Furthermore, an admin should be available to unblock incorrectly blocked domains. Reported false positive domains will be removed from the list!"

The Pro++ is a more aggressive list, which means that it partially blocks trackers that can lead to functional restrictions.

@relvinarsenio
Copy link

If using the light version only, what do you think? Do you still recommend it for everyday use? @hagezi

Compared to the Light, the Normal also blocks a few more trackers, pop-up ads and more malware domains. I see no reason not to switch from the Light to the Normal, unless you use the Light because of its smaller size.

But I would combine any list, no matter which version, with the TIF if possible.

How about the comparison of False Positives between Normal and Light?

@Krishna-art-dev
Copy link
Author

And what's the difference between pro and pro++

https://github.com/hagezi/dns-blocklists#proplus:

"More aggressive version of the Multi PRO blocklist. It may contain few false positive domains that limit functionality. Therefore it should only be used by experienced users. Furthermore, an admin should be available to unblock incorrectly blocked domains. Reported false positive domains will be removed from the list!"

The Pro++ is a more aggressive list, which means that it partially blocks trackers that can lead to functional restrictions.

I checked your pro blocklists statistics there I found adguard firstparty ublock origin first party easylist firstparty

And in pro ++ statistics it was adguard multiparty ublock origin multiparty easylist multiparty I was thinking what was it what the difference between it

@hagezi
Copy link
Owner

hagezi commented Sep 2, 2023

Nextdns TIF is same as yours? Because nextdns doesn't have your TIF in blocklists

I don't know which sources NextDNS uses, so I can't make a statement about that. But I think they are similar. NextDNS does not accept combined external TIF lists, they use, according to their statements, only native sources and security services. That is the reason why the TIF is not included.

So which dns server you gonna recommend for using nextdns or adguard. if nextdns's TIF is like yours I think then nextdns is better it have your pro Blocklist and and list so have choices

Both are good services, take what suits you best.

@hagezi
Copy link
Owner

hagezi commented Sep 2, 2023

How about the comparison of False Positives between Normal and Light?

Almost identical.

@hagezi
Copy link
Owner

hagezi commented Sep 2, 2023

And in pro ++ statistics it was adguard multiparty ublock origin multiparty easylist multiparty I was thinking what was it what the difference between it

Multiparty = $third-party, see https://adguard.com/kb/de/general/ad-filtering/create-own-filters/#third-party-modifier

So the multiparty lists contain, also extracted rules with the modifier $third-party.

@Krishna-art-dev
Copy link
Author

Does notracking admin accepted your offer?
Btw I have no more issue you can close this comment

Thanks for replying

@hagezi
Copy link
Owner

hagezi commented Sep 2, 2023

Does notracking admin accepted your offer?

You mean this?
notracking/hosts-blocklists#900 (comment)

I have not received any direct feedback.

@hagezi hagezi closed this as completed Sep 2, 2023
yokoffing added a commit to yokoffing/NextDNS-Config that referenced this issue Sep 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants