HaGeZi Lists and hBlock are added.

I'm using HaGeZi PRO++ without any issues. It blocks twice as much as OISD, with no increase in false positives. OISD itself uses the HaGeZi whitelist (among others) to make itself better, so there will be a big overlap in that whitelisted entries are very similar in OISD and HaGeZi. 

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.

Kind Regards,
Gerd

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.