4 ms·

What is it about manifest v3 that would make blocking youtube ads impossible, but would continue to be possible with manifest v2?

tomrod 3y ago
As a user of their service, rather than a developer of ads or their service, it isn't incumbent on me to care about their approach. Rather, it is incumbent on me to exercise caveat emptor, and understand that Google has both exercised nefariously in prior activities and that ads are how they choose to make revenue. Ergo, trust is low.
Scion9066 3y ago
It isn't the manifest version directly that is doing this, just the permissions/api changes that are happening at the same time. Firefox for example is keeping the old style as an option while still implementing support for MV3 and the declarative option: https://blog.mozilla.org/addons/2022/05/18/manifest-v3-in-firefox-recap-next-steps/ https://blog.mozilla.org/addons/2022/05/18/manifest-v3-in-fi... Mozilla will maintain support for blocking WebRequest in MV3. v3's has declarative blocking/redirecting of things vs v2's read/write access to all network requests on any page. https://developer.chrome.com/docs/extensions/migrating/blocking-web-requests/ https://developer.chrome.com/docs/extensions/migrating/block... Manifest V3 changes how extensions handle modification of network requests. Instead of intercepting network requests and altering them at runtime with chrome.webRequest, your extension specifies rules that describe actions to perform when a given set of conditions is met. Do this using the Declarative Net Request API. https://developer.chrome.com/docs/extensions/mv3/manifest/declarativeNetRequest/ https://developer.chrome.com/docs/extensions/mv3/manifest/de... Using declarativeNetRequest, you can block or modify network requests by specifying declarative rules. This lets extensions modify network requests without intercepting them and viewing their content, providing more privacy.

tomrod 3y ago

As a user of their service, rather than a developer of ads or their service, it isn't incumbent on me to care about their approach. Rather, it is incumbent on me to exercise caveat emptor, and understand that Google has both exercised nefariously in prior activities and that ads are how they choose to make revenue. Ergo, trust is low.

Scion9066 3y ago

It isn't the manifest version directly that is doing this, just the permissions/api changes that are happening at the same time. Firefox for example is keeping the old style as an option while still implementing support for MV3 and the declarative option: https://blog.mozilla.org/addons/2022/05/18/manifest-v3-in-firefox-recap-next-steps/ https://blog.mozilla.org/addons/2022/05/18/manifest-v3-in-fi... Mozilla will maintain support for blocking WebRequest in MV3. v3's has declarative blocking/redirecting of things vs v2's read/write access to all network requests on any page. https://developer.chrome.com/docs/extensions/migrating/blocking-web-requests/ https://developer.chrome.com/docs/extensions/migrating/block... Manifest V3 changes how extensions handle modification of network requests. Instead of intercepting network requests and altering them at runtime with chrome.webRequest, your extension specifies rules that describe actions to perform when a given set of conditions is met. Do this using the Declarative Net Request API. https://developer.chrome.com/docs/extensions/mv3/manifest/declarativeNetRequest/ https://developer.chrome.com/docs/extensions/mv3/manifest/de... Using declarativeNetRequest, you can block or modify network requests by specifying declarative rules. This lets extensions modify network requests without intercepting them and viewing their content, providing more privacy.