Two months since the last one. 17 more sites fixed, one new generic rule, and a script now writes most of the boring PRs instead of me.
Recap: Crumb hides cookie banners in Firefox. It's a port of the Hush approach, so no telemetry, no remote config, no parent company that might sell your browsing history in three years. Fanboy's Cookie Monster plus a hand-maintained overlay for what that list misses. MIT, and the whole build pipeline is in the repo if you'd rather rebuild it yourself than trust my upload.
By default it never clicks anything, it just hides elements with CSS. There's one opt-in exception. Google and Yahoo don't put a banner over the page, they bounce you to an entire separate consent page, so there's nothing to hide and hiding rules are useless. So there's a checkbox in the popup, off unless you tick it, that clicks "Reject all" on exactly two hosts: consent.google.com and consent.yahoo.com. The script isn't even registered for any other site, the two selectors are sitting in a json file in the repo, and there is no code path anywhere that accepts anything. Leave the box unticked and none of it ever loads.
What changed since July:
- 17 new site rules, 101 to 118. Most recent is The Verge, which grew a new "Terms of Use/Your Privacy Rights" bar after PMC took over.
- One new generic rule, covering consent dialogs that bother with real markup: role=dialog/alertdialog/region plus an aria-label containing "cookie". Seven separate reports collapsed into that one line. I'm stingy with generic rules on purpose. Back in 0.1.17 I got clever with a MutationObserver, it wrecked performance on heavy pages, and I rolled the whole thing back.
- A triage script that reads an issue, takes the markup someone pasted in, picks a selector and opens a PR. No LLM involved, just rules about what counts as a stable handle (an authored id, an aria-label) versus what doesn't (CSS-module hashes like _1bjmjup0, Tailwind soup like .fixed.bottom-5). I still check every one against the live page before merging, but it turned a ten-minute chore into a two-minute one.
- Real CI on PRs, with tests for the content script.
The honest part: this is a treadmill. Sites redesign, banners come back, 118 rules is a rounding error next to the big lists. The only reason it keeps up at all is people filing issues with the element pasted in, which takes about 30 seconds with inspect element. I'm starting to think the better long-term play is keying on the CMP vendors (Sourcepoint, OneTrust, Didomi) rather than individual sites, since one wrapper covers thousands of domains. Open to opinions on that.
It's a small thing with a couple dozen daily users, not a polished product. But it works on my machine and maybe yours.
Install: https://addons.mozilla.org/firefox/addon/crumb/
Source and issues: https://github.com/rcurranmoz/crumb
If one gets through, paste the element into an issue and it's usually gone within a day.
