←back to thread

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

(developer.chrome.com)
552 points freedomben | 2 comments | 11 Oct 24 14:20 UTC | HN request time: 0s | 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 #
1. spankalee ◴[11 Oct 24 19:21 UTC] No.41812626[source]▶
What makes you say the security reasons are made up?
replies(1): >>41815738 #
2. Zak ◴[12 Oct 24 02:03 UTC] No.41815738[source]▶
I can take this question.

They removed webRequestBlocking, used mainly by adblockers, but left webRequest. The security implications are the same for both, but only the former is optimized for content blocking.