Palisade

Palisade blocks ads and trackers, hides whatever is left over, and tells you what it did. It reads uBlock Origin's filter syntax, so the lists you already trust work here without changes. Nine of them come switched on: EasyList, EasyPrivacy and the uBlock Origin set among them. Four more are a checkbox away. Together that is over 200,000 filters. WHY ANOTHER BLOCKER Why not just use uBlock Origin? On Firefox, go and do that. It is the more mature extension and this is not trying to pretend otherwise. Chrome is where the gap is. Chrome changed its extension platform and the blocking API that ad blockers were built on went with it. The blockers that stayed had to ship reduced versions of themselves, and what got dropped was mostly the part you would notice: filter lists frozen until the extension itself updates, no way to add a rule of your own, and no log or element picker. Palisade kept those. Your own filters apply as soon as you save. Lists refresh on their own schedule rather than waiting on an extension update. The picker lets you click something you want gone and decide how broad the rule should be before you commit to it, which is very useful when a site has reused the same class name for both its ads and its article body. The log tells you what was blocked and which filter is responsible, and that is usually the only thing you have to go on in order to work out why a page broke. Per site you get four settings, from normal filtering down to off. WHAT IT DOES ON A PAGE The request is stopped first, so the ad never downloads; whatever survives that gets hidden, which is what keeps a blocked slot from leaving a hole in the layout. Some sites try to detect blockers, and those get small page fixes. The toolbar icon keeps a count. BUILT TO STAY OUT OF THE WAY Chrome puts a cap on the number of blocking rules an extension is allowed to have. Palisade compresses the default lists to fit well inside that cap (Peter Lowe's list goes from 3,517 rules down to 8), so it is not competing with all of your other extensions for room, and you can run something else alongside it without either one breaking. Element hiding only considers the rules that could plausibly match the page you are on. A page never pays for the tens of thousands that have nothing to do with it. STRAIGHT ABOUT THE LIMITS Chrome cannot express every filter option as a rule. Roughly 3% of the network filters in the bundled lists do not convert. Which ones? There is a page in the settings that names every one of them, along with the reason. Nothing is quietly dropped. For the same reason, blocked requests appear in the log as rule identifiers rather than full addresses. The browser is the thing doing the blocking, and that is all it hands back. Element hiding is logged properly. PRIVACY Nothing is sent anywhere. There is no account, no sign-in, and no telemetry of any kind. Filter lists are downloaded from the people who publish them, and all of the rest stays on your computer. Your settings, your own filters and your per-site choices export to a file whenever you want them out. How would you know? The source is public. OPEN SOURCE https://github.com/TiltedLunar123/palisade Licensed GPL-3.0-or-later. The bundled filter lists remain the property of their authors and are used under their own licences, which the settings page lists for each subscription.