On: google.com/goto: Google's anti-scraping update

[brainwad]

It's not misinformation. By default Google has been able to click track with JS. If you disable JS, they don't serve you search (https://serpapi.com/blog/google-now-requires-javascript/). Yes, if you are tricky, you can block just the part of the JS that does click tracking, probably. But most users can't do that. They therefore were already getting 99% complete click tracking before this change. This change is not about click tracking, it's about blocking scrapers.

And btw about the result filtering the uBlock dev wants to do: of course this can still be done, if you preload all the goto links on the page and then inline the real URLs returned by the preload requests. Perhaps not easy to do as an extension but at a browser level (Brave?) totally possible. Though Google might then think your users are scrapers...

[smart_asslop → brainwad]

>By default Google has been able to click track with JS. If you disable JS, they don't serve you search (https://serpapi.com/blog/google-now-requires-javascript/).

This discussion is about search results pages with JavaScript enabled.

>And btw about the result filtering the uBlock dev wants to do

For a long time, uBlock Origin has kept up with blocking Google's click tracking out of the box with the default Privacy filter list (privacy.txt).

https://github.com/uBlockOrigin/uAssets/blob/master/filters/...

This means that all uBlock Origin users (even people with no Google account) would NOT be click-tracked, WITH JavaScript enabled.

You say "They own the JS on the page", so the topic of discussion here is simply whether users could block click tracking on the client side.

And until now, they could have: by installing uBlock Origin or any content blocker with a sane privacy list.

Now, they cannot.