Add List “1Host (Pro)” about hostlistsregistry HOT 12 OPEN

@badmojr 1Hosts lists are effective as hell. They are one of the must have lists for me. The Lite version for everyone and the Pro if it may be a little more aggressive. Yes there are some domains that restrict functions, but what you need to whitelist is relatively manageable.

I agree with @ameshkov, in AdGuardDNS should be introduced a category "aggressive" to point out to the user that these are not lists that you just take in if you do not know what you are doing.

I would appreciate it very much if the Pro is included.

from hostlistsregistry.

Please add "1 Host Pro", even though it affects FB or some other UI, it's the user's own desire to turn it on. And anytime they can turn off them if required.

from hostlistsregistry.

I stumbled upon this issue since I also miss more restrictive filter lists:
#335

I'm really embarassed now to see this issue here, how is it even possible this issue is open for more than one year and nothing happened with it? It's a filter list to add, nothing more. Instead this issue was completely ignored now with the excuse that it might produce too many false positives. Experienced people choose restrictive lists on purpose and know how to whitelist false positives, either via allow lists or manually.

To me it seems like more restrictive blocklists are missing on purpose, why was only HaGeZi's Normal list and 1Hosts Lite and Mini added for example? I would never choose them personally if I want to reduce tracking. Please @ameshkov let us know if more restrictive lists will be supported in future. If they won't be supported I'm switching back to NextDNS and I'm sure it's a showstopper for most people new to Adguard DNS.

Probably a feature that allows to add custom blocklist URLs can be added like in Adguard Home to let the user decide?

from hostlistsregistry.

Shaking my head that after two years, it's still not implemented. @brokoler yeah, if this doesn't happen, I'll move to rethinkDNS

from hostlistsregistry.

Here's what Reddit has to say about Pro: https://socialgrep.com/search?query=1hosts%2Cpro

from hostlistsregistry.

uniqueness : https://github.com/badmojr/crosscheck/blob/main/results.md#httpso0pagesdevprodomainstxt

from hostlistsregistry.

+1 I would really like to see this list added. It is very well maintained and been my daily driver for a while now.

from hostlistsregistry.

We're a bit afraid that the Pro version completely breaks Facebook apps. There's no such concern with the Lite version and so it was included without questions.

With Pro we'll need to indicate in the UI that this blocklist will break lots of popular stuff.

from hostlistsregistry.

will break lots of popular stuff.

Really?

from hostlistsregistry.

@badmojr well, Facebook apps are pretty popular so yeah, breaking them = breaking popular staff.

The point is that people who should know about this beforehand. Currently, the UI in both AG DNS and AG Home does not indicate any potential issue the user may face after enabling the blocklist.

from hostlistsregistry.

@badmojr well, Facebook apps are pretty popular so yeah, breaking them = breaking popular staff.

The point is that people who should know about this beforehand. Currently, the UI in both AG DNS and AG Home does not indicate any potential issue the user may face after enabling the blocklist.

I believe if one log in to the apps prior to enabling the Pro version, they should find the apps to work just fine.

from hostlistsregistry.

As I recall from blocking graph.facebook.com, that's not the case. At some point the app will need to connect there again.

But don't get me wrong, I don't propose unblocking it or changing anything in the list. Blocking graph.facebook.com makes sense, it is used to load third-party ads and track people by tons of other apps. What I am saying is just that we at AdGuard should do some improvements to our products UI before adding this blocklist.

from hostlistsregistry.