News for hackers. Stuff that matters.
Re:uBlock Origin: Address first-party tracker blocking by pythux on Wednesday November 20, 2019 @11:35AM (#21585377)
Once Manifestv3 is rolled-out, Chrome will not support uBlock Origin at all.
Re:uBlock Origin: Address first-party tracker blocking by arthurfm on Wednesday November 20, 2019 @01:53PM (#21587113)
The developer of Nano Adblocker (which is a fork of uBlock Origin) may continue working on a manifest v3 compatible adblocking extension for Chromium-based browsers.

https://github.com/NanoAdblocker/NanoCore/issues/238

Re:uBlock Origin: Address first-party tracker blocking by jackdh on Thursday November 21, 2019 @09:15AM (#21594164)
I look it up but I can't see a clear answer of why?
Re:uBlock Origin: Address first-party tracker blocking by newscracker on Thursday November 21, 2019 @10:53AM (#21595367)
Manifest V3 doesn’t allow requests to be intercepted and modified by extensions, which is something uBlock Origin requires to block ads and elements on a page.

The proposed way for content blocking in Manifest V3 is how Safari on iOS implemented it a few years ago — a declarative list of URLs to be blocked is provided by the extension and the browser engine looks that up and blocks them. The extension doesn’t see the actual page URLs or requests, leave alone block them.

This is a positive for privacy since the browsing behavior of the user is not exposed to malicious extensions. But uBlock Origin is not some-random-extension-that-wants-to-steal-information. Treating uBlock Origin like any other extension isn’t good. Since Google makes money by selling ads, there will likely not be any concessions on this front.

Re:uBlock Origin: Address first-party tracker blocking by dannyw on Saturday November 30, 2019 @08:30PM (#21673218)
Manifest v3 still allows browser extensions to observe web requests. It just stops web extensions from blocking them.

There is no win for privacy here.