Will ManifestV3 actually kill ad-blocking or is it just Any Forums spewing out ridiculous amounts of FUD?

will ManifestV3 actually kill ad-blocking or is it just Any Forums spewing out ridiculous amounts of FUD?

Attached: 1494893557494.gif (500x384, 986.06K)

Other urls found in this thread:

github.com/gorhill/uBlock/wiki/uBlock-Origin-works-best-on-Firefox
twitter.com/SFWRedditImages

kill, no, make it more inconvenient to use for the average retard, yes

Manifest v3 refers to the next major revision of Chromium's browser extension framework. The concern for adblockers is what Google is doing with the webRequest set of APIs. webRequest allows extensions to control every step of the request, from creation to completion and everything in between. It's very powerful and allows for very good content blockers, developer tool add-ons, etc. Google is replacing it with DNR, instead of allowing extensions to modify requests directly, DNR forces the extension to simply hand its filters to the browser, and it needs to trust the browser to execute them. The actual filter types it supports are very basic and it has extreme limitations

This is bad, not only because it weakens adblockers significantly, but because it creates a single, stable target for ad networks to bypass, effectively killing the "adblocker arms race" that was only possible with a general interface like webRequest.

bravechads we cant stop winning

not my problem nigger
github.com/gorhill/uBlock/wiki/uBlock-Origin-works-best-on-Firefox

not my problem nigger
>Brave Shields is implemented in natively compiled Rust and C++ (which is even more efficient than WebAssembly), is able to load rules before making any network requests, uses a compressed filter list data representation, and prefetching is disabled entirely in Brave. The only thing currently missing from that list is HTML filtering, which is fairly rare in practice and generally has fallback rules in popular lists anyways.

>no procedural filters
Dropped

kek, this filter will not work in brave
www.google.com##a:matches-css(white-space:nowrap):has-text(Carbon neutral since 2007)

>he uses Jewgle in the first place

>he thinks Firefox won't eventually remove webRequest too