Earlier quoted context omitted.
Still a shit poor pathetic excuse to screw over the userscript/grease monkey users. The browser is called a user agent, but this shift to absolute security no matter what, no say about it is a shift to native apps, is a shift to the developer is in control, is a shift to this being Google and the sites browser, not ours, and that being done unilaterally with nearly no opt outs is the sort of mega tectonic shift that…
> Still a shit poor pathetic excuse to screw over the userscript/grease monkey users. Tampermonkey still works fine with MV3 > We cannot pander to imagined ever worsening users forever. The most popular software/hardware will always pander to the most users. That’s why they’re the most popular. You can’t complain about the most popular option pandering to the most users. Well, you can complain, but you might be in th…
"Begin disabling installed extensions still using Manifest V2 in Chrome stable"
421–430 of 490 posts
Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"
#422When the hell will firefox have a decent profile manager?? It's the one thing that is preventing me from switching over. No, container tabs are NOT it.
Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"
#423When the hell will firefox have a decent profile manager?? It's the one thing that is preventing me from switching over. No, container tabs are NOT it.
Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"
#424Earlier quoted context omitted.
> People--especially tech nerds--didn't have to switch to the closed source, conflict-of-interest, browser. Do you not remember all the ads promoting chrome? First was chrome-frame IE extension, then came all the ads - then tie-ins where you got Chrome in addition when you really wanted some other app. They pushed it hard because they knew they had no real competitors and could eat up marketshare.
Chrome won because it was more performant (read: only point of interest for Joe Average) and it was modern and cool (read: only point of interest for nerds). Firefox failed because it stagnated on performance and code quality (read: memory leaks for daaaaaaaaays) and ultimately because Mozilla was corrupted by Mitchell Baker and still is to this very day driving away nerds and engineers by the truckload. Lest we forg…
Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"
#425Earlier quoted context omitted.
Brave is an odd one. They've publicly stated[1] they plan to support parts of Manifest v2 for a handful of popular addons (uBlock Origin included) by making limited patches, but they make no promises. It seems Shields was their main focus for MV3 mitigation, much like Vivaldi's now native content blocker made for the same reason (though Vivaldi has said[2] they won't be supporting MV2 past the last Chromium build tha…
Why use uBlock on Brave when Brave already blocks ads natively?
Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"
#426Hopefully this is the inflection point for Chrome. Despite all their made-up "security" reasons, everyone knows this is solely about making adblock less effective. For many users, adblock is what makes chrome bearable - and if they make it unbearable, then those users will leave. Slowly but surely. Google seems much too sure of itself making this change. I hope their arrogance pays off just the same as Microsoft's di…
> Hopefully this is the inflection point for Chrome. Here is one empirical data point. I switched over to Firefox this morning and will advocate for it. I've considered it for a while, but I never felt motivated to make the switch. It took me a good half hour to set it up the way I like it.
Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"
#427Earlier quoted context omitted.
But... what could possibly be the point of using a chromium based browser that is not Chrome, if not for MV2 support?
In case of Vivaldi, it's features like vertical tabs, and extreme customizability for the built-in stuff (for tabs alone the options dialog is like 3 pages of checkboxes for all the various aspects of how they behave). Also for those who use cloud bookmark/history/tab sync, people might just not want Google specifically to have that data; Vivaldi does its own sync.
Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"
#428Earlier quoted context omitted.
MS Edge, Arc, and Sidekick have features Chrome doesn't such as split screen, side panels, and vertical tabs. Likewise for Firefox forks such as Zen.
None of those things are anything close to killer features much less reasons to switch. Verticle tabs, seriously?
Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"
#429Earlier quoted context omitted.
Though it is less of an issue for those two, given that they have built-in adblocking. Still a laudable effort.
While adblocking has gotten most of the focus, it isn't the only functionality that is being limited or made more complicated. One of my favorite extensions is still not available for MV3 because of complications: https://github.com/openstyles/stylus/issues/1430
Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"
#430Earlier quoted context omitted.
MS Edge, Arc, and Sidekick have features Chrome doesn't such as split screen, side panels, and vertical tabs. Likewise for Firefox forks such as Zen.
None of those things are anything close to killer features much less reasons to switch. Verticle tabs, seriously?