uAssets VS easylist

Its already been blocked by Ublock filters - badware risks: https://github.com/uBlockOrigin/uAssets/blob/master/filters/...

1. Force uBlock Origin out.

2. Reimplement its features selectively.

uBlock Origin comes with a filter called 'Block Outsider Intrusion into LAN'[0].

[0] https://github.com/uBlockOrigin/uAssets/blob/master/filters/...

Migrate to Firefox and install uBlock Origin, you will have this feature and more.

fixed https://github.com/uBlockOrigin/uAssets/commit/613159034ef6eed417516e90710474dfab42a808

BTW the whole issue was this, https://github.com/uBlockOrigin/uAssets/commit/de85f38ad297a6724d3f06d360f1693ab29599ad

Aternos is problematic. See issue https://github.com/uBlockOrigin/uAssets/issues/13144

Fixing anti-adblock may cause ads or breakages. If you see any issue, please report back the EXACT URL and your country when accessing the URL so volunteers are able to investigate by commenting here or in this thread on github.

Looking at the filters that uBlock is using, it still seems to be some sort of regex on the xhr request/response body [1]. Why can't youtube trivially defeat this by encrypting everything?

[1] https://github.com/uBlockOrigin/uAssets/commit/fb33bb3c1fa99...

a) How does ublock (-the extention-) upgrade . i suppose what that purge caches does is going to the repo and grabs the latest lists/ids etc ... but if during this battle you had to upgrade the extention itself was this done via the extention store or the the extention goes grabs the new version by it self ?

Mega thread issue on GitHub tracking this https://github.com/uBlockOrigin/uAssets/issues/19976

Reddit is not and should not be considered a tech support site.

uBlock Origin has a few 'Annoyances' lists that you can enable in the settings, e.g. Fanboy's list on https://easylist.to/

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