5 ms·
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 th
by hvdijk 5y ago
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-auditing 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 Firefox doesn't support the ping attribute, the problem is that Google fails to respect user requests not to track.
- metalliqaz 5y agoExactly. That's why I solved this problem by using DDG. Although I admit some searches I have to send to Google to get the result I'm looking for.
- zuhsetaqi 5y agoSame for me, but all google searches are done by DDG bangs like 'g!'
- metalliqaz 5y agoYeah, me too. Love the bang system. Don't forget to put the exclamation point in front! "!g"
- greenyoda 5y ago> Don't forget to put the exclamation point in front! "!g" At least some of the bang keywords work with the "!" on either side. I tried "g!" and "w!" and they work OK.
- zuhsetaqi 5y agoFor all the bangs I use it works either way but yes, the official way is with the exclamation in front
- zokula 5y agoUsing bangs defeats the purpose of using DDG in the first place. And DDG tracks your clicks just like Google does.
- zuhsetaqi 5y agoAbsolutely not at all. It's the reason number one why I use it because very often I know on which page I want to search for a query. And having DDG as the default search engine in the browser gives me the ability to use the URL bar to directly query Youtube with !yt or Wikipedia with !w and a lot more.
- mrguyorama 5y ago>use the URL bar to directly query Youtube with !yt or Wikipedia with !w and a lot more. My understanding is both Chrome and Firefox can do this natively, ie without DDG
- zuhsetaqi 5y agoYes you can add these, in Firefox it's called Search Shortcuts and a few are there by default. But there are a few reason why I prefer DDG: 1. I don't have to add those things in my Browser 2. When I searched DDG for something don't find good stuff I can just go to the search bar on the DDG page and add any !bang to query a search engine I like (!y for Yahoo, !g for Google, …) 3. No matter which Browser I use on which device, the only thing I have to change is the default Search engine and it's set up for anything I want to search. This is especially nice for me since I use Firefox on my Mac, Brave and Safari on my iPhone and Brave and Chromium on my Windows device
- Dah00n 5y agoSeems to me the old Emac (or vi) saying have changed. Today it is "How do you know someone uses DDG? He'll tell you!"
- mcdevilkiller 5y agoHow do you know someone uses Google? Well, virtually everyone does, so they probably do.
- Ajedi32 5y agoSeems 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.
- JohnFen 5y agoThat wasn't what caused DNT to fail. What caused it to fail was that websites could decide whether or not to honor it, and honoring it would have meant a reduced ability to spy on people, impacting their income.
- Ajedi32 5y agoThat was part of it. Obviously if sites had no choice in the matter then it wouldn't have mattered whether browsers enabled it by default or not. Since it was a voluntary thing though, browsers sending it by default pretty much destroyed what chance there was of mainstream sites deciding to implement support for it. It's one thing to give up on tracking a small portion of users who explicitly opt-out, and another thing entirely to give up on tracking everyone except for a tiny minority who choose to opt-in.
- 8note 5y agoIf browsers weren't sending it be default, it wouldnt have any support because nobody saw enough traffic with it to implement it. The design is the problem since websites who don't feel like it don't have to honor it. Whether it's because it'll bankrupt them by everyone setting it, or not bothering with supporting their unprofitable users.
- metalliqaz 5y agoIts reasonable to assume that users choose a more privacy focused browser intentionally, meaning that "default" setting is intended by the user and not a decision that's made for them without their knowledge.
- varenc 5y agoI 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 tooltip. Does any browser supporting pings actually do that?? Also the "Note" in that section provides a decent argument for supporting `ping`. Basically, users will have their clicks tracked anyway, but the `ping` attribute provides more transparency and a better user experience. Though the transparency part is debatable given browser implementations.
- kevin_thibedeau 5y agoThird 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.
- nephanth 5y agoThis is wrong : what google currently does on firefox is make you go through a link that logs you clicked on it, then redirects you to your destination. This doesn't need any javascript, it just needs to log your http request, so it should work on any browser (even, say, elinks)
- account42 5y ago> Also the "Note" in that section provides a decent argument for supporting `ping`. Basically, users will have their clicks tracked anyway, but the `ping` attribute provides more transparency and a better user experience. I see this argument used a lot for including user-hostile features in browsers. I don't think it's a good argument since having a browser implementation a) makes this privacy abuse easier and b) legitimizes the practice. Meanwhile as shown in this post, user-preference to disable the feature is ignored and simply worked around by websites.