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

441–450 of 490 posts

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

#441

Post by quotemstr »

matheusmoreira wrote: post #435
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…

Manifest v3 changes are pretty reasonable. Declarative filtering that prevents untrustworthy software from getting access to data is objectively a good thing. It's just that uBlock Origin is so important and trusted it should have access to everything. Truth be told it should be literally built into the browser itself and deeply integrated with it. Only conflicts of interest prevent that. Can't trust an ad company to…

The problem isn't the declarative filtering per se. The problem is the draconian limit on the number of filters. Given that we can compile regular expressions to DFAs and evaluate them in O(len(url)) time no matter how many patterns we have, there's little reason to place an arbitrary cap on the sophistication of an extension's filtering.

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

#442

Post by quotemstr »

pkasting wrote: post #345
Spunkie wrote: post #277

Earlier quoted context omitted.

Explain to me how uBlock Origin can realistically go from 100,000 to 500,000 dynamic rules down to 30k rules(only 5k of those can be dynamic) in the Lite version without losing the ability to actually block everything? These limits are easy targets for ad networks to overwhelm or outmaneuver. That's what everyone was saying Everyone was saying that the new API is less capable than the old API at blocking things. Decl…

> Explain to me how uBlock Origin can realistically go from 100,000 to 500,000 dynamic rules down to 30k rules(only 5k of those can be dynamic) in the Lite version without losing the ability to actually block everything? I will take this one. First, your limits are out of date. The static minimum is 30k, but can now escalate to an order of magnitude higher depending on how many extensions are installed. The dynamic l…

Google lifting the arbitrary rule count limit would go a long way towards building trust.

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

#443

Post by 10000truths »

matheusmoreira wrote: post #435
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…

Manifest v3 changes are pretty reasonable. Declarative filtering that prevents untrustworthy software from getting access to data is objectively a good thing. It's just that uBlock Origin is so important and trusted it should have access to everything. Truth be told it should be literally built into the browser itself and deeply integrated with it. Only conflicts of interest prevent that. Can't trust an ad company to…

There was already an established solution for running untrusted code - the WebAssembly engine sandbox. Data can't be exfiltrated if imported functions are forbidden, which would be very easy to verify via static analysis of the WASM module. All of this hullabaloo about Manifest v3 could have been avoided if the Chrome team did the sane thing and exposed an API for using a WebAssembly module for filtering.

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

#446

Post by lostmsu »

Dylan16807 wrote: post #348
IncreasePosts wrote: post #324

Earlier quoted context omitted.

Open source also means you're free to fork it or freeze your version

Forking is untenable for individual humans with something so complicated, and freezing is dangerously insecure.

Should we start a HN browser then?

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

#447

Post by Spivak »

Etheryte wrote: post #153
neoromantique wrote: post #3

On Mac OS: https://kagi.com/orion/

I love Kagi, but I wish they focused on their core product first. Search is a hard problem to nail down and there's no shortage of bugs in Kagi right now, their issue tracker is a solid testament to that. When they spread their attention and resources between multiple products, they run the risk of pulling a Mozilla and shooting themselves in the foot multiple times.

They do focus on their core product first. I hang out in their discord, it's first priority always. Their other ventures are in service of the search engine— FastGPT powers quick answers, universal summarizer powers the "summarize this link" feature, small web is their go at an index of their own.

Orion is kind of a stretch I think, but they do see it as being in service of their search product as it's the only way they'll ever be the default search engine anywhere.

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

#448

Post by sockaddr »

btown wrote: post #308
sockaddr wrote: post #296

Earlier quoted context omitted.

I think everywhere that you used “nonzero” you could have also not and it would have still made exactly the same point.

Normally this kind of thing isn’t said in good faith, but it’s actually a way my writing can improve and I appreciate the feedback!

To be honest, the reason I mentioned it at all was because I do the same thing with the same word so it was as much of a comment for your benefit as it was for my benefit haha.

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

#449

Post by igornadj »

igornadj wrote: post #398
chlorion wrote: post #237

Earlier quoted context omitted.

I used the lite version while on chromium for some time. I noticed no difference in terms of blocking ads. The main thing I missed was the ability to block arbitrary elements with the zapper. I use this for more than just ads, so losing it is a real loss in functionality. Otherwise it worked fine.

Yeah the zapper is indispensable. Being able to filter content on platforms by the words in post titles is one of the best ways to not be exposed to toxic content. Never leaving your subscriptions (never using the algorithm recommended feed) is not a solution because of second-hand toxicity, e.g. political posts in meme subreddits in an election year. If anyone knows of a solution that works in Manifest V3 I'd love t…

Found something, a drop-in replacement.

AdGuard AdBlocker (MV3 Beta): https://chromewebstore.google.com/detail/adguard-adblocker-m...

Copy and pasting the ublock custom filters into AdGuard seems to work.

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

#450

Post by damianh »

afranchuk wrote: post #49
varun_ch wrote: post #15

Earlier quoted context omitted.

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…

Note that Firefox profile management is getting an overhaul right now, including an easy profile switching UI. I'm not sure when it will be landing in release, but it is being actively built!

This is insanely overdue.
Post reply on HN