easylist VS AdguardFilters

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?

As far as Safari-compatible ad blocking extensions, I've been reasonably satisfied with AdGuard, and it's free with some paid nice-to-haves which I don't use, but hear good things about. It's available on nearly every browser and operating system, including Android and iOS. It's also open source.

https://en.wikipedia.org/wiki/AdGuard

https://adguard.com

https://github.com/AdguardTeam

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

! trusted filter (not sure if it affects the query part) ||amazon.com/*/ref=$urltransform=/\/ref=.*// ! does not require trust, but likely will break stuff (it's too broad) ! you can use "AdGuard URL Tracking Protection" - https://github.com/AdguardTeam/AdguardFilters/blob/fff7e0702850ec9298e7825fc04563990bc40a2e/TrackParamFilter/sections/specific.txt#L1322-L1394 ||amazon.com^$removeparam

Keep in mind that neither of those lists are default lists and neither are maintained by the uBlock Origin team. Issues with those lists should be reported to their maintainers: - AdGuard URL Tracking Protection: https://github.com/AdguardTeam/AdguardFilters/issues - Actually Legitimate URL Shortener Tool: https://github.com/DandelionSprout/adfilt/discussions/163

Issue: https://github.com/AdguardTeam/AdguardFilters/issues/152943

Fixed in AdGuard Spanish/Portuguese list: https://github.com/AdguardTeam/AdguardFilters/commit/03d5583f6a0251b9b9b80280269757f29547c86d