easylist VS adblock-nocoin-list

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.

Its something 🤷‍♂️ only browser based miners you could block with pi-hole. But not IPs of miners malware. But In addition to the blocklist I shared earlier, you can also add the 'No Coin' blocklist (https://github.com/hoshsadiq/adblock-nocoin-list/) to your Pi-hole, as well as the following regex rule:

NoCoin Filter List

NoCoin

You can use this list with the blocking software of your choice: https://github.com/hoshsadiq/adblock-nocoin-list

uBlock Origin - with most relevant adblocker filters installed, including custom ones like NoCoin, SMASHBLOCK, and others.