hosts

I been maintaining a little hosts project for blocking ads and trackers [0]. I've casually noticed over the years that a lot of the lists out there combine other people's lists - some are more upfront about it then others. That got me thinking, who was the first list to block domain X? That is where this website comes in. A lot of popular block lists are hosted on GitHub, so that made it really easy to clone the repo and do a full history import of the project. I made a little script that could walk the git history and generate a JSON file containing all the unique versions to import [1]. The oldest lists from Steven Black's popular hosts project: April 2012 [2]. Other lists are harder to find history on, so they just go back as far as this project does. As a test to watch domains from one list get consumed by other lists, I added a fake

Just put Steven Black's host list[1] in to /etc/hosts Not sure what, apart from extra cpu cycles, pihole adds over this. [1] - https://github.com/StevenBlack/hosts

This is great. I do not see WPM and ACC stats though. It just shows empty placeholder for those. I use PiHole and https://github.com/StevenBlack/hosts to block ads. I see that the google analytics is not resolved properly in dev tools. Is that the issue with WPM/ACC stats?

If you want to replicate that kind of configuration that is as painless as possible you just have to go into the extension options/configuration. Head to the "My rules" tab and you will find a rule, towards the top of the rule list, that says: "* * * block" This rule acts as a default blacklist. If you switch it to: "* * * allow" it will allow everything by default (except the blacklisted domains, which overrule this). Then in the "Assets" tab you can configure your blacklists, I can recommend Steven Black's lists. He curates and consolidates several of the most famous ones: https://github.com/StevenBlack/hosts He maintains several variants according to themes you may want to ban (adware, malware, fakenews...). Choose the combination that suits you.

I've used this successfully for years. https://github.com/StevenBlack/hosts While not your traditional ad blocker done via browser extension, it does the job quite well and blocks the requests at the OS level. I'm not the author or maintainer, just a very happy user.

I've opened the following issue to get input about how woke hosts files should treat Plausible and Fathom. I'm interested to hear good takes, if you have any, on the subject of ethical tracking. What to do about Plausible and Fathom? https://github.com/StevenBlack/hosts/issues/1346

I use uMatrix to block scripts on certain domains. I used to use NoScript for this, but switched to uMatrix when I found that it gave me much more fine-grained control over what to allow or block. For ad-blocking, I supplement uMatrix with uBlock Origin. It has its own block lists that it perodically On top of that, I use privoxy as an http proxy. Unfortunately, it can't filter https. Yet another part of my defense is DNS blocklists that I put in to /etc/hosts.[1] Using this combination, I virtually never see any ads. [1] - https://github.com/StevenBlack/hosts

> and I should disable FF's DoH support? yeah there is no reason (I can think of) why you need FF DoH with your setup. In fact if you were to enable DoH in FF it would bypass your pie-hole - so you most certainly want to avoid that. my setup looks pretty much like yours with some additional /etc/hosts blocking[1] on the client just to avoid the round-trip to the pie-hole. it's also a double insulation (but it's more of a performance reason than bc of paranoia). I found that switching off ipv6 dns resolution in FF (`network.dns.disableIPv6` in about:config) has tremendously sped up my DNS lookups in FF (though I haven't had time to analyze why). in case you're worried about homograph phishing attacks you could also add a regex to your pie-hole's dnsmasq (not sure what piehole uses but I know it has a fork of dnsmask that supports regex) so

for good measure, here are 83k additional domains: https://github.com/StevenBlack/hosts

I can see how it might seem that way — I'm Steven Black. I can point to thousands of combined... * issues https://github.com/StevenBlack/hosts/issues?q=is%3Aissue+is%... * ...pull requests... https://github.com/StevenBlack/hosts/pulls?q=is%3Apr+is%3Acl... * ... and commits https://github.com/StevenBlack/hosts/commits/master ...that indicate, it's not so easy. The sources we use are all vetted. Some sources are remarkable in terms of activity, and responsiveness to problems as they occur. Overall I think this area is far more dynamic than many realize. Some good people curate the lists we carry.

This repo has a 3-week track record, by one contributor. Disclosure: Some of us have been actively curating such amalgamated lists for a long time. https://github.com/StevenBlack/hosts

I have been using NextDNS with a few block lists configured at the router level and device level. The internet experience has improved a lot since ads and trackers are blocked system wide. A few block lists that I would recommend: 1. Steven Hosts - https://github.com/StevenBlack/hosts 2. Adguard DNS - https://github.com/AdguardTeam/AdguardSDNSFilter 3. disconnect.me The amount of DNS requests made silently in the background is astonishing across all devices.

Also a shameless plug for the extensible, amalgamated hosts file I actively curate: https://github.com/StevenBlack/hosts

I actually have been doing some work with MaraDNS to have the ability to have a pi-hole sized blacklist. The main source of pi-hole’s blacklist is this Git repo: https://github.com/StevenBlack/hosts That is about 60,000 hosts, so I added MaraDNS support to have up to 500,000 blacklisted names. Since it’s a speed-optimized (not size-optimized) cache, each element takes about a kilobyte of memory, so a blacklist this size takes about 60 megabytes of memory for MaraDNS to store (on a modern Core i7 7600U processor, it only takes about two seconds to load all 60,000 elements in to memory), but it’s very rapid to use. The script to take that blacklist and convert it in to a MaraDNS compatible format is here: https://github.com/samboy/MaraDNS/blob/master/deadwood-githu... There are ways to make the memory footprint of the blacklist smaller, b