4 ms·
Raymond Hill, the developer of uBlock Origin said that "removing the blocking ability of the webRequest API means the death of uBO" in this comment https://git
by ayushnix 4y ago
Raymond Hill, the developer of uBlock Origin said that "removing the blocking ability of the webRequest API means the death of uBO" in this comment
https://github.com/uBlockOrigin/uBlock-issues/issues/338#issuecomment-456179825 https://github.com/uBlockOrigin/uBlock-issues/issues/338#iss...
You can follow the issue tracker for any progress related to MV3 development of uBO but from what I can see, there isn't much interest yet in porting uBO to MV3 because it's not worth it.
This EFF article also goes into details about why MV3 is harmful for adblockers.
https://www.eff.org/deeplinks/2021/12/googles-manifest-v3-still-hurts-privacy-security-innovation https://www.eff.org/deeplinks/2021/12/googles-manifest-v3-st...
- ehsankia 4y agoThat comment you link is from 2019, and Google has made many substantial changes to MV3 since in response to the feedback. It obviously still doesn't give as much power as WebRequest API, but they still addressed many complaints and increased a lot of the limits.
- ayushnix 4y agoThe EFF article is pretty recent and it doesn't look good either. I haven't come across ongoing work for a port of uBO to MV3. If there isn't, that says a lot as well. Whatever MV3 may offer, I for one do not want adblockers to be compromised. If anything, they should be more powerful rather than less. Hypothetically and optimistically speaking, even if a MV3 port of uBO offers 80% of the current functionally, it would still be detrimental for browsing the "modern" web.