Can Anyone Explain What Manifest V3 Is Like I'm 5?

What the hell is this thing and why are so many people angry about it? Many publications write stories about it and how it's bad for ad blockers, but never explain what it is and why it's bad. What's the big deal about it?

Attached: ManifestDestiny.jpg (1200x630, 156.32K)

Other urls found in this thread:

eff.org/deeplinks/2021/12/chrome-users-beware-manifest-v3-deceitful-and-threatening
youtube.com/watch?v=CqR5Tv1hC2U
twitter.com/SFWRedditImages

shitty tv show about a plane that disappears got canceled and netflix bought the rights

No more AdBlock basically
>Captcha:NSAGYM

Firefox will actually truly be the only option.

>I'm 5
MOOOOOODS

adblockers are heavy extensions, they move to block heavy extensions in the exact way they need to work to block ads.

2 seconds on google:
eff.org/deeplinks/2021/12/chrome-users-beware-manifest-v3-deceitful-and-threatening

>Google's Manifest V3 harms privacy protecting extensions.
>Manifest V3 shrinks extension capabilities and Web users' freedom to customize their browsing experience.

Just more schizo doomposting combined with Firefox shills. Nothing will change for you and Chrome will continue to be the best browser. That's all you need to know.

If you don't know what Manifest V3 is...

Basically, each browser extension ships with a manifest that is used by the browser to load extensions. A manifest declares a bunch of information related to that extension, including the name, a description, the current version, etc., but it also specifies which APIs the extension wants to access, under which conditions the extension should be used, etc. (e.g. access to your browser tabs, specific URLs only, etc.).

With Manifest V3, several things are being changed, about what an extension can and can't do. I think that one of the most important changes is that the chrome.webRequest API will now only be available to extensions when forcefully installed (businesses only, I think); otherwise, in the case of common users, extensions will only be able to use the new chrome.declarativeNetRequest API in Manifest V3. There's a major difference:

With the chrome.webRequest API, you pass a function to the API. This function takes an object that represents a request, and within that function, you can decide whether you will let the request pass, alter it, or block it. Because it's a function, you can call other functions, access data, etc. and do complex stuff.

With the chrome.declarativeNetRequest API, you cannot pass your own function. Instead, you need to declare a static list of conditions in order to decide what to do with a request, and you can only do what the API lets you do.

AdBlockers are too complex to implement with only the chrome.declarativeNetRequest API. This change will severely reduce the effectiveness and functionality of adblockers. Not only that, but the Google developers behind this change falsely claim that this change is supposed to benefit the user's privacy, but that's simply not true.

youtube.com/watch?v=CqR5Tv1hC2U

There's something I dont get... why arent adblockers popular on OS-level? Shouldn't there be some sort of AdBlocker app that you can install in your PC, that automatically blocks certain URLs, no matter what browser you use?

/etc/hosts comes close

Why not though? How does Manifest V3 stop plugins from blocking ads?

Not on Windows operating systems. Ads are built into the fucking kernel.

Use Linux Mint, it's way better.

Does this mean NoScript won't work with Manifest V3? It's the only plugin that blocks other trackers that are not ads by not allowing the connection to outside servers in the first place when the feature is not needed when you visit the website.

Attached: TrackersNotBlockedByAdBlockPlugins.png (960x727, 261.51K)

you can add a (massive) list of domains to your /etc/hosts file. that works for the most part but there's always edge cases where you need to whitelist certain things for certain sites to work. plus sites do a lot of fuckery with elements and shit in the browser so sometimes you need powerful tools to select them.

you can block by ip/dns but the best blockers are able to analyze the content and block it even if it comes from the same source as the content you want.

>Chrome will continue to be the best browser.
Wrong. Chrome will go the way of IE.

And then you woke up.

Because sometimes you want to use Twitter or Facebook to view the occasional viral post or to chat with your friends, but you also don't want their trackers embedded on every other website around the web to load and phone home to them tracking you everywhere you go, such as the Share buttons and other tracking pixels that ad blockers don't block because they're technically, "not ads".

Plugins won't be allowed to manage webrequests anymore, so an adblocker won't be able to block the request (download) for an ad.

Yes, noscript will be affected.