←back to thread

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

(developer.chrome.com)
552 points freedomben | 1 comments | 11 Oct 24 14:20 UTC | HN request time: 0.2s | source
Show context
sho ◴[11 Oct 24 14:49 UTC] No.41809962[source]▶
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 did with IE.

replies(14): >>41810044 #>>41810118 #>>41810304 #>>41810320 #>>41810359 #>>41810375 #>>41810472 #>>41810519 #>>41810553 #>>41811938 #>>41812626 #>>41813079 #>>41813685 #>>41822203 #
matheusmoreira ◴[12 Oct 24 20:22 UTC] No.41822203[source]▶
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 maintain ad blockers after all.

replies(2): >>41823854 #>>41823952 #
1. quotemstr ◴[12 Oct 24 23:54 UTC] No.41823854[source]▶
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.