Ah yes good point. Perhaps we should both experiment with different lists and try to work out what works best for a good default. Stopping those stupid cookie consent things would be terrific. Those have spoilt browsing experience for years.
@Wizballs I agree we are almost in a position where we can call it a day for a while, but two more things come to mind.
Firstly, since we added support for an allowlist (default path /root/adblock-lean/allowlist) shouldn't we add support for a manual blocklist (default path /root/adblock-lean/blocklist)? That would just be a case of appending the manual blocklist to the downloaded blocklist part(s), and then business as usual, right?
Secondly, what about pixelserv? pixelserv is used a lot by the AsusWrt Merlin users and serves up a transparent pixel in place of adverts:
What's the status of pixelserv in OpenWrt I wonder? @stangri?
I just came across this thread by @kvic:
Amusingly, the second link in that old opening post now leads to spam.
There is also this:
but that is pretty old.