News for hackers. Stuff that matters.

smart_asslop

Re:Google no longer provides direct URLs in search results on Sunday September 13, 2026 @02:12AM (#49680560)
>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.

Re:Google no longer provides direct URLs in search results on Sunday September 13, 2026 @01:41AM (#49680398)
Even with JS enabled, they did not.

Linked below is an explanation which includes confirmation of that fact by a member of the uBlock Origin team.

https://news.ycombinator.com/item?id=49680338

Re:Google no longer provides direct URLs in search results on Sunday September 13, 2026 @01:35AM (#49680355)
Even with JS enabled, those ping requests (and other tracking) could be blocked; this new measure can not be.

https://news.ycombinator.com/item?id=49680338

Re:Google no longer provides direct URLs in search results on Sunday September 13, 2026 @01:31AM (#49680338)
Hello! It appears that you are disseminating misinformation.

A uBlock Origin developer now confirms, regarding Google results click tracking:

    It existed in a way or another, but it could be blocked. Now it can't.
Which corroborates the mysteriously flagged sibling comment.

https://old.reddit.com/r/uBlockOrigin/comments/1we7491/how_t...

Next time, please consider listening to people who know how the web works and avoid overconfidently parroting what Big Tech gatekeepers want you to think.

Thanks!

Re:QBittorrent breaks out of sandbox to commit crimes on Sunday September 06, 2026 @12:51PM (#49588358)
>Patches welcome

Are they, though? Or are you just parroting the meme?

(The last I recall, Gargron's position was essentially "build your own third-party frontend if you want noJS".)

Re:The revolt of the reader on Sunday September 06, 2026 @01:41AM (#49583655)
Talking about attempts to bypass ML detection:

>This argument can probably be leveled at vanilla raw output from an LLM, but even the slightest attempt at obfuscation bears solid fruit

Whoops, disproven by bcantrill's comment:

https://news.ycombinator.com/item?id=49582629

Let's talk about the detection ability of corporate normies instead:

>pretty much everything “product” in corporate America is now LLM generated with some marginal oversight. It passes muster for the most part.

Goalposts: moved.

Re:The revolt of the reader on Sunday September 06, 2026 @01:33AM (#49583614)
I went to /show and chose a random project with a GitHub repo. Here's the README:

https://github.com/ucsandman/declick/blob/main/README.md

Please let me know if you

    (a) believe this is human prose

    (b) enjoy reading this prose

    (c) would enjoy reading 100 READMEs like this.
As for invoking petitio principii and questioning other commenters' logical coherence [0], can you politely shove the argumentum ad Latinum up your ass?

[0] https://news.ycombinator.com/item?id=49582713