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.
Dropbox spooks users with new AI features that send data to OpenAI when used (arstechnica.com)
Google Chrome will limit ad blockers starting June 2024 (arstechnica.com)
The “Manifest V3” rollout is back after letting tensions cool for a year.
BattleBit Remastered is dominating Steam because there's no catch: it's just a lot of game for $15 (www.pcgamer.com)