Repository navigation
Build a block set from a set of categorised publicly available domain lists #768
alistair-low
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
(I searched the existing ideas but couldn't see anything like this posted already)
I use a DNS service to block time-wasting websites at that level, in concert with LeechBlock. Services such as AdGuard DNS and CloudFlare let me choose broad categories of websites to block, which is really handy.
Maybe something similar would make sense in LeechBlock, for example I might want to set up a block set of Distractions that would include all Games, News, Sport and Social domains and allow myself a few minutes per day to look at those, and a block set of Blocked Sites that includes all Adult, Gambling, Weapons domains, which are permanently blocked.
Rather than maintaining those lists of domains myself, I'd like to use publicly available lists and maybe set a few exceptions. So ideally I'd be able to add multiple source URLs to the "Load list of sites from URL" field, covering all of my chosen categories (i.e. each URL points to a list of domains for one category), and then add some custom domains too, without them getting overwritten when the source URLs are refreshed.
I don't imagine that the maintainer(s) of LeechBlock want to be maintaining category lists of URLs so those would presumably be for the user to find themselves. I had a quick search and found some publicly available examples:
Some are domain lists that would be consumable by LeechBlock, others are hosts files where the preceding IP address would presumably have to be removed during parsing. If anyone reading this knows of a repository of domain lists that's highly categorised and well maintained, that would be personally very useful.
A potential issue is that some of these lists could be huge, so they could be more difficult to manage for users or could introduce performance problems in the UI or in URL blocking operation.
This is just an idea and it seems like the scope is large, so it would be interesting to know whether anyone else thinks this is useful. I think it would make setting up blocklists in LeechBlock much quicker, and easier for beginners too.
To summarise concretely, the features I'm suggesting are:
If this was considered to be a useful idea, I could potentially help with some of the implementation.
Thanks for reading!
All reactions