Live data from Hacker News

Prevent Google from mangling search result links when click/copying on Firefox

gist.github.com

81–90 of 203 posts

Re: Prevent Google from mangling search result links when click/copying on Firefox

#82

Earlier quoted context omitted.

Note the caniuse link says "While still in the WHATWG specification, this feature was removed from the W3C HTML5 specification in 2010." Another reason I prefer Firefox. Why implement a rejected non-standard feature whose primary purpose is to enable surveillance?

> Why implement a rejected non-standard feature whose primary purpose is to enable surveillance? Something that's in the spec that matters (WHATWG) but not the one that desperately pretends to still have relevance for HTML though it hasn't since it tried to push XHTML 2 (W3C) isn't “rejected” or “nonstandard” in any meaningful sense.

WHATWG, also known as We Have Aligned Totally With Google...

The company that has an effectively complete control over the "standard" and churns it frequently to discourage competition...

Re: Prevent Google from mangling search result links when click/copying on Firefox

#83
post #23

It is really worth it to switch to DuckDuckGo. You can throw a g! at the end of your search if you don't like the results DDG gave and it will redirect you to Google. That was the feature that gave me the confidence to switch over, it's painless to get different results, even on a mobile keyboard.

Or use startpage.com which has Google search results.

( !s via ddg)

Re: Prevent Google from mangling search result links when click/copying on Firefox

#84
post #40

Earlier quoted context omitted.

You do, it's just in the devtools menu. The missing piece is triggering javascript based on the loaded page.

Browser devtools are amazing and do have a Javascript REPL. Do people use it for scripting though? It's always been more of a debugger than a Javascript environment. People install node.js for local scripting even though it's the same Javascript engine. It's also not available on mobile.

It’s great if you’re on an unfamiliar machine and need a calculator with loops. It’s also great to press all the buttons on a website.

Re: Prevent Google from mangling search result links when click/copying on Firefox

#86
post #42
post #14

Earlier quoted context omitted.

Firefox has a browser.send_pings setting to control this, not sending any pings when it is set to false. This is explicitly a valid browser implementation of the ping attribute: https://html.spec.whatwg.org/multipage/links.html#hyperlink-... > 2. Optionally, return. (For example, the user agent might wish to ignore any or all ping URLs in accordance with the user's expressed preferences.) The problem isn't that Firef…

Seems like it's set to false by default. So it's not really a "user request" not to track so much as a "browser request" not to. Reminds me of the situation with the "Do Not Track" header where browsers sending it by default caused the signal to lose all meaning.

Arguably, the user requested it by intentionally choosing to use a browser with that default behavior.

Re: Prevent Google from mangling search result links when click/copying on Firefox

#87
post #78
post #14

Earlier quoted context omitted.

Firefox has a browser.send_pings setting to control this, not sending any pings when it is set to false. This is explicitly a valid browser implementation of the ping attribute: https://html.spec.whatwg.org/multipage/links.html#hyperlink-... > 2. Optionally, return. (For example, the user agent might wish to ignore any or all ping URLs in accordance with the user's expressed preferences.) The problem isn't that Firef…

I noticed this part of the spec too: > When the `ping` attribute is present, user agents should clearly indicate to the user that following the hyperlink will also cause secondary requests to be sent in the background, possibly including listing the actual target URLs. > For example, a visual user agent could include the hostnames of the target ping URLs along with the hyperlink's actual URL in a status bar or toolti…

Third party links won't be "tracked anyway" if you're blocking JS. That's the only reason to have this feature since a site can track activity from its own links via logs.

Re: Prevent Google from mangling search result links when click/copying on Firefox

#88

Earlier quoted context omitted.

I actually prefer short userscripts like this over addons, because I can immediately see it's not doing anything nefarious and I only need to trust the addon that I install the user script with.

> I only need to trust the addon that I install the user script with I wonder why this is even necessary. User scripting should be a standard feature of browsers. We should have direct access to a complete Javascript environment every time we launch a browser. Just like Emacs gives users a Lisp environment.

it was, in Opera up to 12.xx. You just dropped .js files in designated directory and it _always_ ran before executing website js.

Re: Prevent Google from mangling search result links when click/copying on Firefox

#89

While this might solve the problem for the Google search engine it is but a patch to a bigger problem. Instead of applying this patch on each and every device you happen to use it is much more effective to refrain from using these search engines directly by using a meta-search engine like Searx [1]. This not only solves these obnoxious attempts at leaching a bit more data from you, it has an even bigger advantage: it…

Searx is very cool. It would be nice if I could configure my browser to rotate through different searx instances rather than configuring one as the default search engine. Btw the list of public nodes is here: https://searx.space/ What is the difference between SearXNG [0] ("next generation," i.e. the one you just linked) vs. SearX [1]? NG claims to be a fork, but it's not clear why? The main SearX has recent developm…

> It would be nice if I could configure my browser to rotate through different searx instances rather than configuring one as the default search engine.

That can be achieved using the Privacy Redirect [1] extension, set it to redirect search engine calls and it will use a random engine. The list contains more than just instances of Searx and can by default not be edited by users so you might have to get the source [2] and build a version with only those search engines you want to use. It can redirect many other corporate entities like Youtube, Twitter, Instagram (which does not really seem to work but since I never go there anyway I don´t really know), Reddit, Maps (Google etc) and others. I have it redirect to private instances of Invidious (for Youtube), Nitter (for Twitter) and LibReddit. I do not use search engine redirect since I run a custom Searx instance which doubles as an intranet search engine and as such offers more than any public instance.

[1] https://addons.mozilla.org/en-US/firefox/addon/privacy-redir...

[2] https://github.com/SimonBrazell/privacy-redirect

Re: Prevent Google from mangling search result links when click/copying on Firefox

#90

Earlier quoted context omitted.

Even through HTTPS? They'll have the domain and IP address and transfer size, but not the URL or contents of the traffic. (Unless they managed to MITM a trusted certificate somehow.)

HTTPS encrypts the host? Thought you had to know where to go to open that secure transmission. It's enough for your ISP to know you went to "pornhub.com" for example.

They won't know when you use an alt DNS or DoH.
Post reply on HN