- May 26, 2014
We will probably not do that, as we see little point in it considering what I mentioned earlier. The major point of ControlD is that we do all the hard work for you and distill it all to a single toggle switch which enables a far better blocklist than what you will find online, as per feedback from people in this thread. You can always make custom rules to add/remove domains to the "house" blocklists.
The entire system was built for speed, especially on the backend. We use Redis as the sole database, so everything has to be in memory. This also includes the servers themselves which run from a live OS image, with no disk access, something we're trialing here and will be deploying to Windscribe servers shortly.
You may notice your custom rule changes are instantly enforced, and the panel should be lightening quick (assuming you're within 50ms of the closest POP). Adding all these extra blocklists is useless to 99% of people because they don't know the difference between StevenBlack, OISD and countless others, and will inevitably ask questions like "which one is better?". We prefer to avoid this confusion by providing 1 good list to rule them all, and it does do that.
I fully understand and respect the decision not to include customized lists for the service.
Generally these lists contain a lot of redundancy and the use of many of them together can substantially increase the number of false positives and thus inoperative services and broken pages for the user.
ControlD's method of prioritizing a "proprietary" and professionally maintained list is commendable and functional, which will ensure a better user experience for a wider range of people.
If the proprietary list offered left something to be desired then it was more than necessary that the third party list was supported, but this is not the case.