3 ms·

Ugh, all external links in this article go through the Google click tracker. :-/ Here are ungoogled URLs: https://elixir.bootlin.com/linux/v4.17/source/includ

by jwilk 8y ago

Ugh, all external links in this article go through the Google click tracker. :-/ Here are ungoogled URLs: https://elixir.bootlin.com/linux/v4.17/source/include/linux/jhash.h#L70 https://elixir.bootlin.com/linux/v4.17/source/include/linux/... https://elixir.bootlin.com/linux/v4.17/source/include/net/dst.h#L442 https://elixir.bootlin.com/linux/v4.17/source/include/net/ds... https://elixir.bootlin.com/linux/v4.17/source/include/linux/thread_info.h#L121 https://elixir.bootlin.com/linux/v4.17/source/include/linux/... https://c9x.me/x86/html/file_module_x86_id_318.html https://c9x.me/x86/html/file_module_x86_id_318.html https://elixir.bootlin.com/linux/v4.17/source/arch/x86/include/asm/bug.h#L33 https://elixir.bootlin.com/linux/v4.17/source/arch/x86/inclu... https://gcc.gnu.org/onlinedocs/gcc-4.0.1/gcc/Extended-Asm.html https://gcc.gnu.org/onlinedocs/gcc-4.0.1/gcc/Extended-Asm.ht... https://www.embecosm.com/appnotes/ean10/ean10-howto-llvmas-1.0.html#idp109760 https://www.embecosm.com/appnotes/ean10/ean10-howto-llvmas-1... https://patchwork.kernel.org/patch/10450037/ https://patchwork.kernel.org/patch/10450037/ https://lkml.org/lkml/2018/10/4/25 https://lkml.org/lkml/2018/10/4/25 https://elixir.bootlin.com/linux/v4.17/source/include/linux/slab.h#L699 https://elixir.bootlin.com/linux/v4.17/source/include/linux/... https://gcc.gnu.org/onlinedocs/gcc/Other-Builtins.html https://gcc.gnu.org/onlinedocs/gcc/Other-Builtins.html https://elixir.bootlin.com/linux/v4.17/source/arch/x86/kvm/vmx.c#L9669 https://elixir.bootlin.com/linux/v4.17/source/arch/x86/kvm/v... https://elixir.bootlin.com/linux/v4.17/source/arch/x86/kvm/vmx.c#L706 https://elixir.bootlin.com/linux/v4.17/source/arch/x86/kvm/v...

gruez 8y ago
I was wondering why that'd be the case (usually the only reason these urls even pop up was because someone was copying urls from a google results page), then I saw this at the bottom: >Made with the new Google Sites, an effortless way to create beautiful sites.
- kbd 8y ago
  TIL about Google Sites. TBH I'd prefer Google link tracking everywhere over popups every time I visit a la Medium.
  - anadav 8y ago
    Sorry for that. It was the path of least resistance when I set a website.
- jrockway 8y ago
  The idea is to prevent you from leaking the URL of your internal google sites page through the referer header. Maybe Google does some tracking, but the idea behind the redirect was for privacy, as I understand it. (Disclaimer: former Googler.)
  - jwilk 8y ago
    You can disable sending the Referer header with Referrer-Policy: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Re... (Maybe R-P didn't exist when the current solution was concocted.)
    - wolfgang42 8y ago
      Per MDN, Referrer-Policy isn't supported in IE/Edge either, so you'd have to do browser sniffing. This seems like it has the potential for something to go wrong and cause a referer leak. On the other hand, if it's a public site then obviously there's no concern about the URL leaking, so I'd think this should only be turned on for sites that are set as private.
      - jrockway 8y ago
        I'm guessing that the underlying problem here is that you can share things in Google Drive / Google Docs to "anyone with the link" and when that's enabled, you probably didn't actually intend to share it with the owners of the websites that you happened to link to. Safer to just never let the URL leak.
  - taneq 8y ago
    There's usually a good justification like this for features like these. The fact that every single such feature results in Google tracking more of your life is a mere coincidence.
    - jrockway 8y ago
      I mean, they could just inject Javascript that detected that you clicked the link if tracking was the only goal. The fact that they prefer an HTTP redirect means there's more than just tracking involved. It would be nice if they put a link to the privacy policy on the redirect page, so the intent was more clear.
jwilk 8y ago
Alternatively, you can run this in the web console to fix the links: for (let a of document.querySelectorAll('a[href*="/url?"')) { a.href = decodeURIComponent(a.href.match(/[?]q=([^&]+)/)[1]); }

by jwilk 8y ago

gruez 8y ago

I was wondering why that'd be the case (usually the only reason these urls even pop up was because someone was copying urls from a google results page), then I saw this at the bottom: >Made with the new Google Sites, an effortless way to create beautiful sites.

kbd 8y ago
TIL about Google Sites. TBH I'd prefer Google link tracking everywhere over popups every time I visit a la Medium.
- anadav 8y ago
  Sorry for that. It was the path of least resistance when I set a website.
jrockway 8y ago
The idea is to prevent you from leaking the URL of your internal google sites page through the referer header. Maybe Google does some tracking, but the idea behind the redirect was for privacy, as I understand it. (Disclaimer: former Googler.)
- jwilk 8y ago
  You can disable sending the Referer header with Referrer-Policy: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Re... (Maybe R-P didn't exist when the current solution was concocted.)
  - wolfgang42 8y ago
    Per MDN, Referrer-Policy isn't supported in IE/Edge either, so you'd have to do browser sniffing. This seems like it has the potential for something to go wrong and cause a referer leak. On the other hand, if it's a public site then obviously there's no concern about the URL leaking, so I'd think this should only be turned on for sites that are set as private.
    - jrockway 8y ago
      I'm guessing that the underlying problem here is that you can share things in Google Drive / Google Docs to "anyone with the link" and when that's enabled, you probably didn't actually intend to share it with the owners of the websites that you happened to link to. Safer to just never let the URL leak.
- taneq 8y ago
  There's usually a good justification like this for features like these. The fact that every single such feature results in Google tracking more of your life is a mere coincidence.
  - jrockway 8y ago
    I mean, they could just inject Javascript that detected that you clicked the link if tracking was the only goal. The fact that they prefer an HTTP redirect means there's more than just tracking involved. It would be nice if they put a link to the privacy policy on the redirect page, so the intent was more clear.

jwilk 8y ago

Alternatively, you can run this in the web console to fix the links: for (let a of document.querySelectorAll('a[href*="/url?"')) { a.href = decodeURIComponent(a.href.match(/[?]q=([^&]+)/)[1]); }