Earlier quoted context omitted.
Though it is less of an issue for those two, given that they have built-in adblocking. Still a laudable effort.
At this point, I wonder why Firefox doesn't have a vivaldi-like tracker and ad block interface. Perhaps it has to do with being a Google-funded browser. I wonder how hard that would be to implement for someone who knew how to do it? Or if the code for that in vivaldi is open source?
"Begin disabling installed extensions still using Manifest V2 in Chrome stable"
281–290 of 490 posts
Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"
#282Can't we avoid the Manifest bullshit altogether? I remember how IE plugins roles: just dll inject into the process.
https://blog.chromium.org/2017/11/reducing-chrome-crashes-ca...
Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"
#283"browsers using the ExtensionManifestV2Availability policy will be exempt from any browser changes until June 2025" To extend ManifestV2 in Chrome, add the text below to a text file, saving and running it as a .reg will create and add a value of 2 to "ExtensionManifestV2Availability" in the HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome key (When you open/run a .reg file, it updates your registry, usually preceed…
And IIRC including the quotes in a filename in a save dialog, líke "manifestv2.reg" (incl quotes), will save it with the extension you typed, so you won't end up with 'manifestv2.reg.txt'. So you skip a potentially otherwise needed rename step.
Also, just for clarification:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome]
"ExtensionManifestV2Availability"=dword:00000002
Apparently, the line Windows Registry Editor Version 5.00 is necessary at the beginning of the .reg file. This line indicates the format version for the registry file and tells Windows that it is compatible with the current registry editor (according to GPT). This worked for me.Save the file as:
EnableExtensionManifestV2.regRe: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"
#284Earlier quoted context omitted.
> tech nerds you would be surprised how many devs these days have drunk the big tech coolaid. leetcode all the time and dream of working at google and using chrome and writing javascript. if the tech nerds took a stand and used firefox en masse, we wouldn't have this problem. unfortunately it is now normie season. we have to travel through these dark times.
There's still hope. I would like to draw a parallel to Microsoft Windows, with my own narrative added over. Tech nerds mostly knew that Windows was not a good server operating system. It was also not a fantastic software development environment unless you were using a big, all-inclusive, IDE that was probably aimed specifically at developing Windows libraries and applications. But, Windows was (and still is) the choi…
Agreed 100% with this.
Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"
#285Earlier quoted context omitted.
Are you certain? The last I heard about it from Vivaldi[0], they were only going to keep the MV2 code around so long as it's in the upstream codebase: > We will keep Manifest v2 for as long as it’s still available in Chromium. We expect to drop support in June 2025, but we may maintain it longer or be forced to drop support for it sooner, depending on the precise nature of the changes to the code. Note that June 2025…
Vivaldi team does not respond to any comments asking about ongoing v2 manifest support; safe to assume it's gone as soon as it's out of Chromium upstream. Given Tetzchner's continual messaging on how important user privacy is to Vivaldi it seems like a strange decision, but I don't know how much effort would be required to maintain the support. They're a small team, so it would be understandable if they would just sa…
Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"
#286Earlier quoted context omitted.
> It's worth noting that the maintenance of the "lite" version is at some nonzero risk of burnout for its developers, ironically in part due to Mozilla being unnecessarily hostile: Why would you even use the lite version on firefox when the original works?
The "original" UBO is basically the mother of all supply chain vulnerabilities and whenever the inevitable exploit happens, everyone who thought they were a connoisseur of privacy is going to get completely pwned. UBO Lite works without being a gigantic security vuln.
Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"
#287Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"
#288I've finally switched (back) to firefox today. I switched from firefox to chrome for their superior devtools a few years back, but hopefully firefox has had time to catch up. Everything old is new again!
IMO they are still not as good although they have improved. I just develop in chrome and use Firefox for everything else.
Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"
#289Every time I try to migrate my very large bookmark collection to another browser, it either misbehaves and partially loses some data or fails completely.
Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"
#290Earlier quoted context omitted.
To my knowledge the “big” chrome engine alternatives aren’t either. I know that Vivaldi and Brave plan on keeping around v2 as long as it is economically feasible
This sounds like Android phone manufacturers making fun of apple for removing the headphone jack and then doing it themselves a year later. Are they seriously going to maintain V2 support for a relatively small percentage of Powerusers which probably are mostly already using Firefox anyways? The point of being economically infeasible is probably in a month or so.