Technology

37722 readers

58 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

TheRtRevKaiser@kbin.social

232

Google Chrome will limit ad blockers starting June 2024 (arstechnica.com)

submitted 1 year ago by DolphinMath@slrpnk.net to c/technology

80 comments fedilink hide all child comments

The "Manifest V3" rollout is back after letting tensions cool for a year.

you are viewing a single comment's thread
view the rest of the comments

[–] ericjmorey 17 points 1 year ago (2 children)

Mozilla is implementing Manifest V3. They plan to implement it slightly different than Chrome: https://blog.mozilla.org/addons/2022/05/18/manifest-v3-in-firefox-recap-next-steps/

They have published a guide for extension developers: https://extensionworkshop.com/documentation/develop/manifest-v3-migration-guide/

More background on Manifest V3:

https://www.eff.org/am/deeplinks/2019/07/googles-plans-chrome-extensions-wont-really-help-security

https://www.eff.org/am/deeplinks/2021/11/manifest-v3-open-web-politics-sheeps-clothing

https://www.eff.org/am/deeplinks/2021/12/chrome-users-beware-manifest-v3-deceitful-and-threatening

https://www.eff.org/am/deeplinks/2021/12/googles-manifest-v3-still-hurts-privacy-security-innovation

[–] myofficialaccount@feddit.de 30 points 1 year ago

Relevant part from the blog post:

What are we doing differently in Firefox? WebRequest

One of the most controversial changes of Chrome’s MV3 approach is the removal of blocking WebRequest, which provides a level of power and flexibility that is critical to enabling advanced privacy and content blocking features. Unfortunately, that power has also been used to harm users in a variety of ways. Chrome’s solution in MV3 was to define a more narrowly scoped API (declarativeNetRequest) as a replacement. However, this will limit the capabilities of certain types of privacy extensions without adequate replacement.

Mozilla will maintain support for blocking WebRequest in MV3. To maximize compatibility with other browsers, we will also ship support for declarativeNetRequest. We will continue to work with content blockers and other key consumers of this API to identify current and future alternatives where appropriate. Content blocking is one of the most important use cases for extensions, and we are committed to ensuring that Firefox users have access to the best privacy tools available.

load more comments (1 replies)