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.
Prevent Google from mangling search result links when click/copying on Firefox
51–60 of 203 posts
Re: Prevent Google from mangling search result links when click/copying on Firefox
#52Good search results, with privacy
Re: Prevent Google from mangling search result links when click/copying on Firefox
#53Earlier quoted context omitted.
> whose primary purpose is to enable surveillance Google search is good because it tracks what links people click and knows when they come back to go to a different url on the page. if 99% of people visit the top result for a query, return, then hit the second one, chances are that the top result never answers what the search query asks.
> Google search is good because Google search might have been good over a decade ago but today it's trash.
IME, its still consistently far and away better than the alternatives. Part of the difference in perception of quality may be that over time it has come to use more personal signals to zero in on relevant results, and the people that complain about how bad it is overlap considerably with those who actively seek to deny those signals to Google.
Re: Prevent Google from mangling search result links when click/copying on Firefox
#54Earlier quoted context omitted.
> 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.
You do, it's just in the devtools menu. The missing piece is triggering javascript based on the loaded page.
It's also not available on mobile.
Re: Prevent Google from mangling search result links when click/copying on Firefox
#55It 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.
DDG user here, I’m not even sure most people would need g! anymore. I recently came across a Google search results page, and was surprised how unrecognizable it has become. Instead of giving me a page full of search results, it was presenting me with a page full of Google-curated content. At this point, Google is basically unusable for me as a search engine.
Re: Prevent Google from mangling search result links when click/copying on Firefox
#56Google does this so they have click tracking data. But they don't need to mangle URLs in Chrome because it supports the `ping` attribute on tags [0]. The ping attribute basically adds click tracking as a native browser feature so you don't need to do URL redirects. It also makes these analytics much easier for the site and mysterious to the user. Looks like most vendors besides Firefox support it. (They were pretty o…
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?
Also probably worth noting that the W3C doesn't maintain an HTML standard anymore[1]; the WHATWG standard is the definitive one.
Re: Prevent Google from mangling search result links when click/copying on Firefox
#57Re: Prevent Google from mangling search result links when click/copying on Firefox
#58Earlier 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.
Re: Prevent Google from mangling search result links when click/copying on Firefox
#59Earlier quoted context omitted.
Doesn't require running javascript, so presumably the devices could be more efficient in sending them versus XHR/fetch.
The article specifically says the offending pages used JavaScript to add the ping attribute to the tags, so the attack wouldn't have worked against users with JS disabled anyway.
Re: Prevent Google from mangling search result links when click/copying on Firefox
#60It 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.
DDG user here, I’m not even sure most people would need g! anymore. I recently came across a Google search results page, and was surprised how unrecognizable it has become. Instead of giving me a page full of search results, it was presenting me with a page full of Google-curated content. At this point, Google is basically unusable for me as a search engine.