What I mean is that while none of these lists are enabled by default, they are pre-configured in the settings. In other words, these lists are recommended for use β you just enable what you need, and itβs supposed to work. My point is: if you recommend something, you should be confident in it. Plus, it still doesn't explain why specific entries in the list would block the update process.
P.S.
I have replaced the default URL with the one you suggested, and the package updated successfully. Thanks! Perhaps the author should consider making this change as well. Just a suggestion.
The pre-defined version had about 380000 entries. The one I posted only has 180000 due to the removal of unnecessary sub domains. Perhaps it was a memory issue, but I cannot say that with any confidence.
No. There was a syntax error in the list itself. Unfortunately, I didn't save a screenshot. Before this incident, the list hadn't caused any crashes; the only thing I noticed was that its size would fluctuate between 9 MB and 3 MB, which was suspicious but didn't lead to failures.
I am currently using Version 1.2.2-r16. After adding a domain to the blacklist, I am still able to access it. The blacklist only takes effect after I restart OpenWrt.
Looking for anyone using Adblock-fast on main snapshots with dnsmasq 2.92 to test whether allowlisting works with this dnsmasq version for an exact match of a blocked domain. I'm not on snapshots to test myself, but I've been following a similar report on another forum for another router platform where dnsmasq 2.92+ doesn't behave the same as 2.91 and earlier when using the common syntax:
server=/ads.example.com/#
local=/ads.example.com/
On the newer dnsmasq version the first entry isn't honored. Just looking to see if anyone on snapshots can reproduce this. Thanks.