brave-browser VS easylist

https://github.com/brave/brave-browser/wiki/Patching-Chromiu...

You'll notice the actual patching itself is introduced with the caveat:

Brave browser, which blocks ads and trackers, grew to over 50 million monthly active users in 2023 while enabling privacy-first models to counter Google's search and Chrome browser ecosystem.

Still waiting on the Brave stable release with the patched version of chromium https://github.com/brave/brave-browser/issues/35013

Manually download the standalone version from: https://github.com/brave/brave-browser/releases/tag/v1.61.101 and update it that way.

Upgraded Chromium to 120.0.6099.71. (#34740) (Changelog for 120.0.6099.71)

Brave Github repository

For those looking for a fix: Use the latest Nightly Build for Brave.

~Using privacy plug-ins or browsers. You can block our site from setting cookies used for interest-based ads by using a browser with privacy features, like Brave, or installing browser plugins, like Privacy Badger, Ghostery or uBlock Origin, and configuring them to block third party cookies/trackers.

import { ScreenshotOptions } from "./schema"; import puppeteer, { Page } from "puppeteer"; import { PuppeteerBlocker } from "@cliqz/adblocker-puppeteer"; import fetch from "cross-fetch"; let blocker: PuppeteerBlocker | null = null; async function blockCookieBanners(page: Page) { if (!blocker) { blocker = await PuppeteerBlocker.fromLists(fetch, [ // the list of the cookie banners to block from the https://easylist.to/ website "https://secure.fanboy.co.nz/fanboy-cookiemonster.txt", ]); } await blocker.enableBlockingInPage(page); } export async function render( options: ScreenshotOptions ): Promise<{ url: string }> { const browser = await puppeteer.launch(); const page = await browser.newPage(); if (options.block_cookie_canners) { await blockCookieBanners(page); } await page.setViewport({ width: options.viewport_width, height: options.viewport_height, deviceScaleFactor: options.device_scale_factor, }); await page.goto(options.url); const encodedScreenshot = await page.screenshot({ type: "jpeg", encoding: "base64", fullPage: options.full_page, }); await browser.close(); return { url: `data:image/jpeg;base64,${encodedScreenshot}` }; }

uBlock Origin has a few lists for cookie banners that I always keep on [0][1]

[0] https://github.com/easylist/easylist/tree/master/easylist_co...

[1] https://github.com/AdguardTeam/AdguardFilters/tree/master/An...

I think this is now fixed (or worked around) by https://github.com/easylist/easylist/issues/17937 ?

You mean the VG Wort METIS tracking in order to participate in the German royalty scheme? From a publisher perspective that tracking is necessary, but from a user perspective it's just another example of third party tracking. Thus, it is part of some filterlists that uBlock Origin users can subscribe to, for example the EasyPrivacy list. Talking to the filterlist authors is very unlikely to resolve this: after all, it is tracking, regardless of intention.

Fixed in EasyList: https://github.com/easylist/easylist/commit/859abc79711aa69441e809a394677f6392b8c59a

If I have noticed a new ad, to which list should I report a filter issue? Should I report the new advertisement to the issue tracker at uBlockOrigin/uAssets, or should it be reported to EasyList instead?