Hacker News Reader

Comment by dessant | Hacker News Reader

We've all been watching with disbelief as Google evolved the narrative around the declarativeWebRequest API, coming up with new angles and changing the goalposts to wear people down as critics have disproved all of Google's reasons for deprecating the blocking capabilities of the webRequest API, and nothing substantial has changed.

It does not matter what any of you think and say to this company.

What you have to do now is organize.

View on HN

Google's strategy is to promise they'll look into changes when their feet are next to the fire, and then when everyone forgets they continue the despicable anti-privacy behavior.

The undisclosed X-Client-Data telemetry, the adblocker-busting Manifest V3 and the new APIs that are used almost exclusively for ad network fingerprinting (AudioContext and others).

Chrome is the DoubleClick browser and now that market share is so strong the facade can lift.

Stop using Chrome. You’ve got Firefox, Safari, Edge, Brave, etc.

There's a good chance that none of those browsers will support the blocking webRequest API in 3 years, and that's because of Google's thumb on the scale. Quitting Chrome solves nothing.

Break up Google.

2/4 of those are Chrome

chromium, with modifications.

And 1/4 (Safari) already only implements declarative request blocking, and has done that for years while being touted as the alternative for privacy conscious folks.

Microsoft begins Manifest v3 tests in Edge that impacts extensions like content blockers

https://www.ghacks.net/2020/10/15/microsoft-begins-manifest-...

Reply on news.ycombinator.com