HaGeZi Lists and hBlock are added.
I was checking the filters and just saw that the HaGeZi filters that were requested and hBlock is added.
I remember that a lot of people were asking for it and I'm going to test it out to see how it compares to OISD.
I wanted to share it with everyone else so everyone can try it out.
As a quick update on HaGeZi filters the Pro one seems to be quite good but still has some FP's like Lightswitch05 and 1HostLite.
Normal seems to be close to OISD in terms of pure compatibility, I'm going to try running both OISD and HaGeZi Normal to see if I see anything in terms of False Positives but quite an amazing filter, now the second filter in the lists to focus on compatibility.
I take a different approach than the OISD. The OISD is a great list that you can add to, provides good protection, and usually doesn't need any further maintenance. If something causes functionality restrictions somewhere, it goes on the whitelist there as long as it doesn't cause ads to be displayed on multiple pages, for example.
Nevertheless, unblocking is done here with a sense of proportion. There are almost no false positive domains in OISD. This is the strength of OISD. A disadvantage, thereby e.g. the tracker number 1, google-analytics.com was partially unblocked because on the popular page reuters.com some videos do not start.
If you don't mind such things and you want a list that doesn't lead to restrictions in any situation, you will make the best choice with OISD. It is a very well maintained list and the maintainer always has an open ear.
Maintaining such large lists is hard work. One of the main problems is that domains you unblocked a long time ago because they cause functional restrictions on various pages, apps or devices, might be blocked again today because these restrictions no longer exist due to customization. You need to check your whitelist from time to time. That's very time-consuming.
My approach is different, one example, google-analytics.com for example I would only whitelist if it leads to functional restrictions in mass, but not if it leads to functional restrictions on a handful of pages - the tracker is just too popular for that. And I think it's pretty cheeky to link important site functionality to this top tracker. For this kind of trackers, you actually have to get permission beforehand according to the EU data protection directive, but the directive offers loopholes that are of course used, all a matter of interpretation.
Through the different list versions and the different degree of aggressiveness of these, I am able to decide what is whitelisted where depending on what restrictions the blocked domain leads to. So every user should have the possibility to find the right list for him. Example, the top tracker number 2 googletagmanager.com it leads to function restrictions on various pages therefore it is unblocked in Light to Pro, but because it is popular and partly used as a bypass for google-analytics.com, it is blocked in Pro++ and Ultimate. There are many examples of this.
The OISD is a list that must satisfy all user preferences. For more there is the OISD extra, which is unfortunately not available in NextDNS. But it can be combined with the very effective 1Hosts lists, if you don't mind to create your own whitelist.
Apart from the fact that I don't see my lists as competition for other lists, every user should decide for himself what suits him, a block rate comparison between OISD and PRO PLUS is not meaningful for the reasons mentioned above. Probably the block rate of the LIGHT is higher than the OISD in normal operation, but that is due to my chosen approach.
I spent months compiling the lists, they are not just lists compiled from different sources using a whitelist. Each list has its own extension, which I compiled individually using the CISCO Umbrella 1M top lists. But, without the sources used, the lists would simply be nothing. The OISD and 1Hosts have a significant part in this.
I started with the PRO PLUS, I wanted a list with the right balance between aggressiveness and balance. The other versions were then developed from this. For my needs, the perfect list was created with this attempt, the PRO PLUS.
I really like the HaGezi lists.
I use the Ultimate-List and I don´t need any whitelist...until now:
When I open o2online.de , the whole site is just text and some wrong placed images. Normally I will find the "bad" entry in my protocol in my NextDNS account, but this time I failed. Maybe someone here can identify the problem.
FYI: Currently there seems to be a GitHub problem, the RAW links over which the lists are retrieved do not provide the current list versions, but partly only a cached version from yesterday. Currently only the Multi NORMAL version seems to be available. I see this behavior in other Github repositories as well.
I’m not sure if this is a false positive per say but it does seem to break Amazon browsing history. Some may say that’s the very definition of a tracker and you can’t really argue with that but someone might be using it and it can be turned off in an Amazon account.
This is for multiple regions.
When using WOW (Sky streaming) App on tvOS I found nzdsqcybmv.trkcliq.com as a new entry in my logs. The site belongs to Amazon and I can block it without problems to the streaming service.
Both entries are used by the app „Opensignal“. With this entries the networkstatistics (where the average speed of mobile providers were displayed) only shows an error message. The „tiles“-entry is needed for showing the network coverage in a map. I‘ve whitelisted these entries and everything works nice.
It seems, that dpm.demdex.net was added to be blocked to your „Pro++“ list recently (as far as I know, it was only included in your Ultimate list before). It is needed for starting the wowtv streaming service on my AppleTV.
Maybe you could check, if it is possible to remove it or I just keep it whitelisted as long I watch WOW. Thanks
mx.freenet.de is a German email provider.
kiwisearchservices.com is a good browser
revanced.io is a no ads YouTube alternative
All this are just know blocked. Why?
vto.partners-eu.api.ditto.com and bsdk.api.ditto.com are blocked in ULTIMATE. They are needed for testing glasses on misterspex.de.