easylist VS brave-browser

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...

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?

There's also the easylist version available here: https://easylist.to/

Its a EasyList issue. Got fixed now in the EasyList filterlist https://github.com/easylist/easylist/commit/3ea2c063a2d44a8ed64c1c89ddee14b3a86ec0af

brgm.fr https://github.com/easylist/easylist/commit/1203d9b78a4ee073c0649b253d13d853430010c6

https://github.com/easylist/easylist/issues/16372#issuecomme...

> Stupid example of why it may matter: say you installed LAMP on your computer several years ago, you're not using PHP frequently, and you haven't kept it up to date (so it probably contains a few nasty security vulnerabilities), but it still opens up on boot and listens on localhost.

> Now you open some website, it accesses 127.0.0.1, check for the LAMP vulnerability and exploit it if found.

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

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

I don't know why they went with patch files instead of forking chromium and rebasing the changes via git.

They document how developers should "rebase" chromium:

https://github.com/brave/brave-browser/wiki/Chromium-rebases...

And it looks like way more work than doing it with git via

  git rebase chromium/master

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.

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.

careful with brave https://www.ghacks.net/2023/10/18/brave-is-installing-vpn-services-without-user-consent/?amp https://github.com/brave/brave-browser/issues/33726 among other things like the most popular browser compare site being owned by brave employees https://privacytests.org/ i guess when they say privacy they mean it, keeping things private from you too

https://github.com/brave/brave-browser/issues/33726

or how the most popular browser privacy test is run by a brave employee.. hmm guess which browser scores the highest and a favorable testing environment with the settings

Browser:- - Brave - Open source chromium browser with built-in adblocker

I know we like to get the pitchforks out, but, it appears to be accidental:

https://github.com/brave/brave-browser/issues/33726