# Facebook Ads Turned an Open-Source Filter Into a Staffing Problem **Summary:** uAssets maintainers say they will stop chasing Facebook's filter evasions; my read is that this exposes an asymmetric maintenance fight, not the end of uBlock Origin on Facebook. - Canonical: https://markhuang.ai/news/facebook-ad-blocking-became-a-labor-problem - Language: en - Author: [Mark Huang](https://markhuang.ai/about) - Published: 2026-08-12 - Section: News - Tags: uBlock Origin, Facebook, Ad Blocking, Open Source, Browser Privacy - Source: [Neowin](https://www.neowin.net/news/facebook-ads-are-so-hard-to-block-that-ublock-origin-stopped-filtering-them/) - License: https://creativecommons.org/licenses/by-nc/4.0/ --- ![A small red filter shield is repaired by mechanical tools while a vast blue stream of content tiles continually changes shape around it](https://cdn.markhuang.ai/news/facebook-ad-blocking-became-a-labor-problem/hero.webp) *A platform can change the feed again and again. Every response asks maintainers to spend another hour repairing the filter.* [Neowin reported on August 12, 2026](https://www.neowin.net/news/facebook-ads-are-so-hard-to-block-that-ublock-origin-stopped-filtering-them/) that uBlock Origin had stopped filtering Facebook ads after years of chasing the site's countermeasures. The sharper version is narrower: maintainers of uBlock Origin's default uAssets filters said they would stop supporting Facebook-specific fixes. The extension itself has not acquired a universal Facebook exception. That distinction changes my read of the story. Facebook did not solve ad blocking once and for all. It made each successful block temporary, while the people maintaining a public filter list had to decide whether one site deserved another round of unpaid work. This is a staffing problem disguised as a filter problem, and large platforms have the easier side of it. ## The headline hides an important boundary The [August 5 post in r/uBlockOrigin](https://www.reddit.com/r/uBlockOrigin/comments/1vgcjg5/about_disgusting_facebook_devs/) was blunt: "We won't support facebook any more." Neowin read that as uBlock Origin deciding to stop blocking Facebook ads entirely. But discussion around the post supplied a useful clarification. The maintainers are stepping away from Facebook work in the default uAssets filters. Users can still apply custom rules, and other lists may continue to supply Facebook filters. This is more than pedantry. uBlock Origin is an engine that applies several filter lists, not one centrally authored list with a single switch for every site. The [uAssets repository](https://github.com/uBlockOrigin/uAssets) describes itself as the home for uBlock Origin and uBlock Origin Lite filter resources. It also says EasyList-compatible fixes should preferably land in EasyList. uAssets handles cases that need uBlock's extended syntax, along with exceptions such as ad reinsertion, anti-blocker behavior, breakage, and video ads. So the immediate outcome can vary. A Facebook ad may still disappear because an existing rule still matches, another enabled list catches it, or a user adds a custom filter. What is disappearing is the expectation that this volunteer-maintained default list will keep answering Facebook's next move. ## Facebook only has to break the latest rule Neowin describes the contest as a repeated cycle: filter authors find a stable signal for an ad, then Facebook changes how that signal appears. Its most concrete example comes from the Reddit discussion, where participants describe the visible "Sponsored" label being split across elements, with letters reordered or padded with decoy characters. Neowin says a uBO team member described versions of that technique as roughly five years old. I would not treat those implementation details as a complete technical account of Facebook's current ad delivery. They come from a public thread, not a reproducible test case. They do illustrate the maintenance asymmetry. uAssets is developed in public because users need to inspect, improve, and distribute the rules. A platform can inspect those same changes and alter its markup. The defenders publish a fix; the target learns exactly what the fix sees. This cycle predates the present dispute. A [2016 measurement study of ad blocking and counter-blocking](https://arxiv.org/abs/1605.05077) found anti-adblocking scripts on at least 6.7% of the Alexa Top 5,000 sites it examined. The numbers are old and should not be mistaken for today's web, but the paper's description of an arms race still fits the structure here: blocking produces counter-blocking, which produces another response. > **Info:** > > The scarce resource is not the ability to write one more rule. It is sustained maintainer attention after the platform changes again. ## The retreat does not make Facebook unusable Facebook's own [help page about ad blockers](https://www.facebook.com/help/920247859773192/) warns that blocking software may stop parts of the service from working properly. That is the other cost filter maintainers carry. An aggressive rule can remove an ad and break the feed along with it. In one [July 2025 report](https://www.reddit.com/r/uBlockOrigin/comments/1m2r832/facebook/), a user said Facebook would load one post and then show an error while uBlock Origin was enabled. The obvious response is to leave Facebook. Some commenters said exactly that. Others in a [Firefox discussion of the news](https://www.reddit.com/r/firefox/comments/1vm7xlv/ublock_origin_will_no_longer_block_ads_on_facebook/) pointed to family contacts, local groups, hobby communities, and businesses that only maintain a Facebook presence. I find that part of the reaction more useful than the victory laps. A platform can be unpleasant and still be costly to leave when the people or information someone needs remain there. For those users, I would not uninstall uBlock Origin because of a broad headline. Existing and third-party filters may continue to work, though their behavior can change. If a custom rule breaks the feed, remove it before assuming the extension itself has failed. I would also be wary of anyone promising a permanent Facebook-ad fix. The public evidence points to recurring maintenance, not a finished technique. ## My read: budget for the chase I sympathize with the maintainers' decision. Open source does not create infinite labor, and a project is allowed to decide that one adversarial target consumes too much of its attention. What sticks with me is how finished the software can feel while its reliability still depends on people repeatedly absorbing someone else's changes. That should affect how I judge any tool built around public rules against a responsive platform. Who maintains the rules? How quickly will anyone notice breakage? Can another list take over if the current maintainers walk away? Filter syntax matters, but it cannot manufacture a maintenance budget. Facebook ads may still be blocked tomorrow. The promise that uAssets maintainers will keep fighting for that result is what changed. Neowin's headline captures the frustration, but the narrower story is more revealing: Facebook made the chase expensive enough that volunteers chose to spend their time elsewhere.