unclutter VS easylist

no a filter for uBO (I do not think it is possible) but I really like this extension: https://github.com/lindylearn/unclutter

Other browsers can use the uncluttered extension.

There already is crowdsourcing of broken page reports: https://github.com/lindylearn/unclutter/issues?q=is%3Aissue+...

And twitter.com is a special case: https://github.com/lindylearn/unclutter/issues/570

I'm working on those, but it's never going to be perfect unfortunately.

Here’s more info: unclutter.lindylearn.io

I'm looking into this: https://github.com/lindylearn/unclutter/issues/661

It all started with a r/chrome post a few months ago, and since then we've added many improvements to our GitHub project.

Hey! This is a reader mode browser extension I built that hides noisy page elements rather than extracting and re-rendering only the page text. The idea is to not make all articles look the same [0], have them still render graphs, and ideally to work in more cases.

There are a few "tricks": patching the site CSSOM to apply simpler mobile styles even at desktop width, detecting the likely main text & removing its non-text siblings, blocklists for classnames that contain words like "sidebar", and testing this on a few hundred popular sites.

I got carried away and also added a dark mode, page outlines, private annotations & inline Hacker News comments.

The last feature works by parsing every top-level HN comment with a quote in it (formatted with > or "") within a few minutes, and anchoring these quotes in the related article HTML. So when you click a link on HN you’ll see the parts people are talking about while reading. [1]

The code is all on GitHub!

[0] Screenshots comparing it to the Firefox reader mode: https://github.com/lindylearn/unclutter/blob/main/docs/compa...

[1] It's fun to try this on some of the "HN classics" that got 30+ quote comments over the years. The list at hn.lindylearn.io/best shows the number of “annotations” an article has beneath its title.

You can also contribute to the existing extension for this: https://github.com/lindylearn/unclutter

More examples: unclutter.lindylearn.io The code: github.com/lindylearn/unclutter

Hey! This is a reader mode browser extension I built that hides noisy page elements rather than extracting and re-rendering only their text content. The idea is to not make all articles look the same [0], have them still render graphs, and ideally to work in more cases.

There are a few "tricks": patching the site CSSOM to apply simpler mobile styles even at desktop width, cleaning up parents of DOM text nodes, blocklists for class names that contain words like "sidebar", plus manual CSS patches for popular sites.

I got carried away and also added a dark mode, page outlines, privates notes & inline Hacker News comments. [1]

The last feature works by parsing every top-level HN comment with a quote in it (formatted with > or "") within a few minutes, and anchoring these quotes in the story article HTML. So when you open a link you'll directly see the parts people are talking about here. [2]

The extension code is all on GitHub: github.com/lindylearn/unclutter

[0] Unclutter vs the Firefox reader mode: https://github.com/lindylearn/unclutter/blob/main/docs/compa...

[1] The linked website show some examples for these.

[2] It's also fun to try this on some of the "HN classics" that got 30+ quote comments over the years. The list at hn.lindylearn.io/best shows the number of "annotations" a link has beneath its title.

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?