Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

"Begin disabling installed extensions still using Manifest V2 in Chrome stable"

developer.chrome.com

Post reply on HN
Print view View original

131–140 of 490 posts

Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"

#131

Post by EasyMark »

Rychard wrote: post #42
sho wrote: post #25

Hopefully 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…

The widespread adoption of Chrome was largely driven by word of mouth, people like you and I installing it on our friend's/relative's computers and telling them it was safer/faster/better. Nothing stops us from doing the same thing again. I've been recommending Firefox to all my family/friends/colleagues for years (ever since I've seen the writing on the wall for Chrome). While Firefox isn't perfect, it's in a much b…

Did you miss the barrage of ads for Chrome that google played for literally years on the internet and television?

Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"

#132

Post by wtallis »

lapcat wrote: post #111
wtallis wrote: post #96

Earlier quoted context omitted.

They said "we have started disabling Manifest V2 extensions on pre-stable channels", and the "Chrome canary" referenced in the submission title is a pre-stable channel. The submission title is accurate, but narrowly highlighting only one facet of Google's update statement.

That's old news, as noted in my other comment: https://news.ycombinator.com/item?id=41810420 The change here is actually about the stable channel. Also, the title makes it sound like MV2 code has been removed from the source, but that's not the case.

> That's old news, as noted in my other comment:

None of your comments have actually provided evidence for this assertion, and the previous update dated June 3rd 2024 says users will start seeing a warning. So when between June 3 and October 9 did Google start actually disabling MV2 extensions, and where was it publicized prior to their October 9 update?

Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"

#133

Post by wooque »

sho wrote: post #25

Hopefully 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…

I'd argue it won't make a dent in Chrome market share.

People who really care about this (tech minded people) are not using Chrome anyway, others (regular people) will switch to less powerful Manifest V3 adblockers that would probably be good enough and won't switch from Chrome.

Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"

#134

Post by undercut »

freedomben wrote: post #68
undercut wrote: post #61

Earlier quoted context omitted.

>The widespread adoption of Chrome was largely driven by word of mouth No, it was driven by having a banner in the most privileged spot of the Internet, Google.com (the most visited site in the world with 0 ads on the homepage) saying that was faster and more secure than the alternatives. In fact Firefox benefited from some free ads on Google.com against Internet Explorer before Google developed Chromium.

It was kind of both, depending on the timeline. Early on it was word of mouth, then Google saw they had momentum and they capitalized on it with the banners and aggressive marketing.

It was a long time ago but I'm 99% sure that there was a banner for Chrome on Google.com since the first public release.

Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"

#135

Post by grounder »

varun_ch wrote: post #15
Kelteseth wrote: post #2

https://www.mozilla.org/en-US/firefox/new/

Chrome to Firefox is a relatively easy switch, especially for those that don’t depend on Google sync. The main sources of friction for me were the lack of a good profile switching UI (solved with a browser extension that mimics the Chrome menu), and weird security requirements for homemade extensions (IIRC if you want to have the extension persist after restarting Firefox, you need to sign the extension, which is a p…

I don't know much about Arc. But Arc users could give Firefox "Nightly" a try to preview new features coming up. It has vertical tabs and you can "pin" a few tabs at the top. Nightly also has containers already built-in, so you can have multiple accounts open for the same site in different container tabs.

Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"

#136

Post by eek2121 »

michaelt wrote: post #67
kccqzy wrote: post #9

Earlier quoted context omitted.

I have been using the Firefox version of it for more than a year by now, basically as soon as it came out. I commented on HN that I was going to do it: https://news.ycombinator.com/item?id=37219071 There's no difference whatsoever. And it's not surprising because on my iOS device I've been using similarly architected content blockers since 2015. There's no issue with declarative ad blocking. Of course this differs wi…

> And it's not surprising because on my iOS device I've been using similarly architected content blockers since 2015. There's no issue with declarative ad blocking. Really? Because I find adblockers on iOS are nowhere near as good - they let far more ads through, and they leave far more sites broken so I have to disable the ad blocker for the site to work.

That is the fault of the blockers themselves. The one I use (https://apps.apple.com/us/app/1blocker-ad-blocker/id13655310...) works extremely well and even uses a local VPN setup for app ad-filtering.

Twitter and YouTube ads are blocked.

The drawback? It isn’t free.

Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"

#137

Post by EasyMark »

Izkata wrote: post #62
Rychard wrote: post #42

Earlier quoted context omitted.

The widespread adoption of Chrome was largely driven by word of mouth, people like you and I installing it on our friend's/relative's computers and telling them it was safer/faster/better. Nothing stops us from doing the same thing again. I've been recommending Firefox to all my family/friends/colleagues for years (ever since I've seen the writing on the wall for Chrome). While Firefox isn't perfect, it's in a much b…

I swear I also remember it getting included in installation wizards for unrelated software (on Windows), so people would end up with Chrome/Chromium without even realizing it.

I’ve been out of the windows game for so long I forgot all that malware that was installed by various installer engines and was so relieved when I found portable apps and oldversion.com and ninite. And now I guess there are things like chocolaty that do similar things. Switching to Mac and Linux I don’t really miss it at all

Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"

#138

Post by kstrauser »

bdcravens wrote: post #75

Anyone using a PiHole to block on their network? I've been aware of it, but honestly, ad blocking was good enough that I didn't go down that route. Is PiHole good enough? Is there a big problem with false positives?

Yep, and it's great. Beyond ads, you can also configure it to block malware. Got a phishing email from scammer.ru? Nothing happens even if you to click the link in it because that name won't resolve. There were a very short list of exceptions, maybe 2 or 3, I had to add to ours over the years, mainly for hostnames like tracking.shippingcompany.com that got added by mistake.

Note that it does nothing to block DNS over HTTPS lookups. If your browser insists on going around your LAN's DNS setup, Pi-hole can't help you.

Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"

#139

Post by EasyMark »

freedomben wrote: post #17

Notably, Firefox is not removing v2 support (at least for now as of March 2024) > Firefox, however, has no plans to deprecate MV2 and will continue to support MV2 extensions for the foreseeable future. And even if we re-evaluate this decision at some point down the road, we anticipate providing a notice of at least 12 months for developers to adjust accordingly and not feel rushed. [1] [1]: https://blog.mozilla.org/a…

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

Re: "Begin disabling installed extensions still using Manifest V2 in Chrome stable"

#140

Post by paulryanrogers »

Gimpei wrote: post #100

What does this mean for browsers derived from chrome, like Arc? I heard they plan on continuing to support Manifest v2, but will ublock continue to be maintained for chrome?

MV2 code should remain well into 2025 since enterprises can still enable MV2 extensions. After that they may have to hard fork, which could become increasingly costly. Though they could coordinate to minimize duplicated efforts.
Post reply on HN