Google's "Manifest V2" Chrome extension phaseout next month is expected to impact the original uBlock Origin extension, which still uses the V2 framework and has 37 million users
Starting Monday, users will gradually be warned the end is near
The new MV3 architecture reflects Google's avowed desire to make browser extensions more performant, private, and secure. But the internet giant's attempt to do so has been bitterly contested by makers of privacy-protecting and content-blocking extensions, who have argued that the Chocolate Factory's new software architecture will lead to less effective privacy and content-filtering extensions.
For users of uBlock Origin, which runs on Manifest V2, "options" means using the less capable uBlock Origin Lite, which supports Manifest V3.
I have serious video playing issues on Firefox. I thought it was ublock, so i tried turning it off but video and live streams still take forever to load they freeze, too. My computer is very powerful so that's not the issue. No idea what is.
But I guess that isn't applicable to this post because mobile Chromium doesn't have ublock anyway...
And on linux, I have firefox issues with wayland because of some Nvidia thing. Chromium too, but its less severe and I can actually get GPU acceleration working.
It's a sad state of affairs modern schools have when an instructor tries to pull up a video on YouTube or other sites to use in class, and an entire classroom of children have to sit through the unskippable ads.
I guess I'll take that over the TV documentaries my teachers used to record on VHS that had commercials to fast forward through, but the modern internet truly sucks.
Google's Admin Console has an option to continue enabling Manifest V2 extensions. Most schools would be wise to lock down which extensions they let users install anyway, and the zero trust approach is to just deploy what's needed for access to curriculum.
It is a good point: other platforms [other than iOS] have an easy solution (Firefox), but on Chromebooks you're relatively locked in because you have to jump through hoops installing the Linux environment in order to use it.
Chrome always seemed more of a curiosity than something I needed to use. I never saw the need to switch from Firefox when Firefox did everything I wanted.
I still prefer Chrome over Firefox but I've been running Firefox for over a year now and won't go back to Chrome because fuck Google. Also stopped using Google for searching and not being tracked is very very noticeable.
Tried using chromium based browser instead? You are not mainlined into Google that way. Vivaldi is absolutely great. It's got way better baked in features than chrome which can reduce need for extensions and it has a strong commitment to pushing chromium as far as possible to be privacy conscious. Runs and syncs across Android and pc as well.
Those are all chromium based. They all are connected to google and will all have the manifest v3 change.
That is unless they will support v3 but keep some doors open for content blockers ( this is mozillas plan )
Going to plug Cromite (a continuation of Bromite) for a great Chromium fork with built in adblocking, and no nonsense like Brave or whatever: https://github.com/uazo/cromite
Also great on Android (which it was originally developed for).
Forks maintained by a hero dev are less than ideal (and not sustainable TBH), but this is where we are...
Does Cromite have support for auto-filling from 3rd party password managers? When I last used Bromite, it couldn't so I never ended up using it as my main browser
"Users will be directed to the Chrome Web Store, where they will be recommended Manifest V3 alternatives for their disabled extension.
The most salient of these is the blocking version of the webRequest API, which is used to intercept and alter network traffic prior to display.
Under Manifest V2, it's what extension developers use to stop adverts, trackers, and other content appearing on pages, and prevent certain scripts from running.
The new MV3 architecture reflects Google's avowed desire to make browser extensions more performant, private, and secure.
Li acknowledged the issue by noting the ways in which Google has been responsive, by adding support for user scripts, for offscreen documents that have access to the DOM API, and by increasing the number of rulesets in the declarativeNetRequest API (the replacement for webRequest) to 330,000 static rules and 30,000 dynamics ones.
And by the beginning of 2025, when the API changes have been available for some time in the Chrome Stable channel, Manifest V2 extensions will stop working.
The original article contains 589 words, the summary contains 167 words. Saved 72%. I'm a bot and I'm open source!