arkenfox / user.js

Firefox privacy, security and anti-tracking: a comprehensive user.js template for configuration and hardening
MIT License
10.24k stars 518 forks source link

Google's "Manifest V3" (aka "Mv3") and its impact on extensions such as uBO (9-Dec-2021) #1302

Closed atomGit closed 2 years ago

atomGit commented 2 years ago

i'm pissed... again (or is it, still?)

i'm hoping someone here with Moz connections might be able to do something with this...

Chrome Users Beware: Manifest V3 is Deceitful and Threatening

Manifest V3 is another example of the inherent conflict of interest that comes from Google controlling both the dominant web browser and one of the largest internet advertising networks.

Manifest V3, or Mv3 for short, is outright harmful to privacy efforts. It will restrict the capabilities of web extensions—especially those that are designed to monitor, modify, and compute alongside the conversation your browser has with the websites you visit. Under the new specifications, extensions like these– like some privacy-protective tracker blockers– will have greatly reduced capabilities.

[...]

Firefox maintains the largest extension market that’s not based on Chrome, and the company has said it will adopt Mv3 in the interest of cross-browser compatibility. Yet, at the 2020 AdBlocker Dev Summit, Firefox’s Add-On Operations Manager said ...

Thorin-Oakenpants commented 2 years ago

closing this as invalid

i'm hoping someone here with Moz connections might be able to do something with this

there is no-one here with such powers

rusty-snake commented 2 years ago

2019/09/03: Mozilla says they will support both Manifest v2 and v3 and own additions. https://blog.mozilla.org/addons/2019/09/03/mozillas-manifest-v3-faq/ 2021/05/27: After two years nothing has changed. Mozilla will still support the webRequset API. https://blog.mozilla.org/addons/2021/05/27/manifest-v3-update/

atomGit commented 2 years ago

a reader of my site just sent me this, for whatever it's worth...

Manifest v3 update (Mozilla Add-ons Community Blog, 27-May-2021)

declarativeNetRequest

Google has introduced declarativeNetRequest (DNR) to replace the blocking webRequest API. This impacts the capabilities of extensions that process network requests (including but not limited to content blockers) by limiting the number of rules an extension can use, as well as available filters and actions.

After discussing this with several content blocking extension developers, we have decided to implement DNR and continue maintaining support for blocking webRequest.

atomGit commented 2 years ago

@rusty-snake - sorry, i didn't refresh the page to see your comment before i posted, but yes, i'm aware of their "promise" - unless someone can add to that we'll have to see what happens because i don't put allot of stock into it

also, Rob Wu, the author, is a "Firefox engineer on the add-ons team at Mozilla." - in other words, he apparently doesn't operate at the corporate level and it is these bunch of clowns that i take issue with and who may have the power to override what the add-on devs do