nitter-redirect VS easylist

There is an extension that redirects all twitter links to nitter:

https://chrome.google.com/webstore/detail/nitter-redirect/mo...

https://addons.mozilla.org/en-US/firefox/addon/nitter-redire...

https://github.com/SimonBrazell/nitter-redirect

For anyone who would further like to reduce the data they're feeding twitter + traffic, I would recommend you install the "Nitter" addon that redirect twitter pages to open-source self-hostable front-end. https://github.com/SimonBrazell/nitter-redirect

I've been using https://github.com/SimonBrazell/nitter-redirect for ages. My only gripe is these extensions aren't on mobile.

Nitter Redirect on GitHub.

Hop, voilà !

Not for safari, but for chrome and firefox: https://github.com/SimonBrazell/nitter-redirect

depending on your browser there may already be an extension

https://github.com/SimonBrazell/nitter-redirect

"Injustice anywhere is a threat to justice everywhere. We are caught in an inescapable network of mutuality, tied in a single garment of destiny. Whatever affects one directly, affects all indirectly." -MLK

Overall, I'd like to see something other than pure convenience factor in. I think there's a moral (ethos) & logical (logos) cause here, working against the single garment of identity being turned into a corporate run straight-jacket of dominion, and accepting some responsibility, some charge for helping push us towards better, to positively affecting each other, is to me what life is about.

Personally, on extensions versus logins, this doesn't seem like a big ask. Getting a private, non-aggressive, non dark-pattern website is a huge upgrade, for very little cost. Having links I can share easily is a huge upgrade versus linking people to partial fragments & concealed login-walls.

The description for this extension says it only affects Twitter. This is fairly easy to validate in devtools, or if you trust it you can go read the open source, which also proves this claim to be true. This extension will not slow down any other site. This would be great information for the extension stores to make known! Personally I hadn't heard the complaint about extensions slowing things down before. That's a shame. It'd be great for the browser to make more information visible to end-users about the performance impact of extensions. Anyhow, I was able to find this core evidence in less time than it takes a gmail tab to open: https://github.com/SimonBrazell/nitter-redirect/blob/5b997ea...

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?