Live data from Hacker News

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

developer.chrome.com

91–100 of 490 posts

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

#91

Earlier quoted context omitted.

Agreed on hoping this is the inflection point, but only partial agreement that it's about adblock. For sure Google wants adblock to die, but I think it goes even deeper than that. I think it's part of a much bigger trend in tech in general but also in Google: Removing user control. When you look at the "security" things they are doing, many of them have a common philosophy underpinning them that the user (aka device…

yes, iOS now restricts Apps from getting blanket access to their contacts, photos, and even clipboard. On the one hand, it does protect the user from malicious Apps that trick users into giving blanket access. On the other hand, they could have atleast done it like location access - where user still has an option to give blanket access. It is not fair that Siri is the only one that can access these things now.

It can. You can still give apps access to all of it with a single press.

And manifest v3 makes things a bit more tedious but not impossible. There are other adblockers which still function just fine

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

#92
post #65

Earlier quoted context omitted.

It’s similar, but not the same. Safari lets you dynamically generate rules that are then compiled for privacy and efficiency. The limits were increased to 150000 rules per content blocker due to user demands [1]. And each extension can have multiple content blockers. MV3 has a measly 30000 static rule limit. These rules are included with the extension and cannot be updated dynamically. And a 5000 dynamic rules limit.…

The limit is 330000 rules: "Based on input from the extension community, we also increased the number of rulesets for declarativeNetRequest, allowing extensions to bundle up to 330,000 static rules and dynamically add a further 30,000." https://blog.chromium.org/2024/05/manifest-v2-phase-out-begi... .

It looks like it’s a shared quota now with a minimum per extension [1].

Still sucks that the rules are static though. AdGuard devised a method to diff ruleset changes with the built in rules to generate dynamic rules between extension updates. So, I guess it works.

[1] https://developer.chrome.com/docs/extensions/develop/concept...

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

#93
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…

> everyone knows this is solely about making adblock less effective I thought I knew that. Then I switched from uBlock Origin to uBlock Origin Lite in Chrome, which is compatible with Manifest v3. I was prepared for the horrible onslaught of ads, expecting at least a quarter would start getting through, ready to switch to Firefox... ...and didn't notice a single change. Not a single ad gets through. And at the same t…

It makes things a bit more annoying? But in v3 you can still do everything you need to do to block ads

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

#94

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?

Id argue pihole is roughly equivalent to what you can do with manifest v3 based afld blockers. I use it as my primary ad blocker as well, and don't really understand why folks are upset about losing V2 that much. It seems like removing root in favor of more granular permissions which is generally a good thing.

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

#95
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…

> 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"

#96
post #84

This submission title does not appear to be accurate. Here's what was actually said: > October 9th 2024: an update on Manifest V2 phase-out. > Over the last few months, we have continued with the Manifest V2 phase-out. Currently the chrome://extensions page displays a warning banner for all users of Manifest V2 extensions. Additionally, we have started disabling Manifest V2 extensions on pre-stable channels. > We wil…

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.

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

#97
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 like to think that's true, but I don't know, because people seem to have a very high tolerance for advertisements. Surprisingly so. I have a very low tolerance, and do what I can to get rid of them. But then, every once in a while I use someone else's computer and see how they live with them. I say "I can show you how to get rid of those ads," but they usually just don't care enough to do it. I bet the majority of people are like that—maybe the vast majority—and Google is probably making the same bet, but with even more information. My prediction is that if (God willing) Chrome loses significant market share, it'll be for some other reason than this.

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

#98
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…

> everyone knows this is solely about making adblock less effective I thought I knew that. Then I switched from uBlock Origin to uBlock Origin Lite in Chrome, which is compatible with Manifest v3. I was prepared for the horrible onslaught of ads, expecting at least a quarter would start getting through, ready to switch to Firefox... ...and didn't notice a single change. Not a single ad gets through. And at the same t…

> ...and didn't notice a single change. Not a single ad gets through.

When I tried UBO Lite recently it couldn't block YouTube ads, not sure if that's impossible with Manifest V3, or if UBO Lite just isn't updated regularly like UBO to defeat the YouTube anti-ad-blocking updates.

Update: looks like it's fixed now, not bad :)

Post reply on HN