davidbgk
/
larlet-fr-david-cache
Beobachten 1
Favorisieren 0
Fork 0
Code Releases 0 Aktivität
A place to cache linked articles (think custom and personal wayback machine)
Du kannst nicht mehr als 25 Themen auswählen Themen müssen mit entweder einem Buchstaben oder einer Ziffer beginnen. Sie können Bindestriche („-“) enthalten und bis zu 35 Zeichen lang sein.
60 Commits
1 Branch
Struktur: e305ebd928
Branches Tags
${ item.name }
Erstelle Branch ${ searchTerm }
von „e305ebd928“
${ noResults }
larlet-fr-david-cache/cache/2020/9a3fecdca72af16f1403b9e77b6.../index.html

index.html 8.2KB
Originalformat Blame Verlauf

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192939495969798 
  1. <!doctype html><!-- This is a valid HTML5 document. -->

  2. <!-- Screen readers, SEO, extensions and so on. -->

  3. <html lang="fr">

  4. <!-- Has to be within the first 1024 bytes, hence before the <title>

  5.   See: https://www.w3.org/TR/2012/CR-html5-20121217/document-metadata.html#charset -->

  6. <meta charset="utf-8">

  7. <!-- Why no `X-UA-Compatible` meta: https://stackoverflow.com/a/6771584 -->

  8. <!-- The viewport meta is quite crowded and we are responsible for that.

  9.   See: https://codepen.io/tigt/post/meta-viewport-for-2015 -->

  10. <meta name="viewport" content="width=device-width,initial-scale=1">

  11. <!-- Required to make a valid HTML5 document. -->

  12. <title>“Hey Google, stop tracking me” (archive) — David Larlet</title>

  13. <!-- Generated from https://realfavicongenerator.net/ such a mess. -->

  14. <link rel="apple-touch-icon" sizes="180x180" href="/static/david/icons2/apple-touch-icon.png">

  15. <link rel="icon" type="image/png" sizes="32x32" href="/static/david/icons2/favicon-32x32.png">

  16. <link rel="icon" type="image/png" sizes="16x16" href="/static/david/icons2/favicon-16x16.png">

  17. <link rel="manifest" href="/static/david/icons2/site.webmanifest">

  18. <link rel="mask-icon" href="/static/david/icons2/safari-pinned-tab.svg" color="#07486c">

  19. <link rel="shortcut icon" href="/static/david/icons2/favicon.ico">

  20. <meta name="msapplication-TileColor" content="#f0f0ea">

  21. <meta name="msapplication-config" content="/static/david/icons2/browserconfig.xml">

  22. <meta name="theme-color" content="#f0f0ea">

  23. <!-- Documented, feel free to shoot an email. -->

  24. <link rel="stylesheet" href="/static/david/css/style_2020-04-25.css">

  25. <!-- See https://www.zachleat.com/web/comprehensive-webfonts/ for the trade-off. -->

  26. <link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_regular.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>

  27. <link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_bold.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>

  28. <link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_italic.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>

  29. <link rel="preload" href="/static/david/css/fonts/triplicate_t3_regular.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>

  30. <link rel="preload" href="/static/david/css/fonts/triplicate_t3_bold.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>

  31. <link rel="preload" href="/static/david/css/fonts/triplicate_t3_italic.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>

  32. 

  33.   <meta name="robots" content="noindex, nofollow">

  34.   <meta content="origin-when-cross-origin" name="referrer">

  35.   <!-- Canonical URL for SEO purposes -->

  36.   <link rel="canonical" href="https://www.magiclasso.co/insights/hey-google/">

  37. 

  38. <body class="remarkdown h1-underline h2-underline h3-underline hr-center ul-star pre-tick">

  39. 

  40. <article>

  41. <h1>“Hey Google, stop tracking me”</h1>

  42. <h2><a href="https://www.magiclasso.co/insights/hey-google/">Source originale du contenu</a></h2>

  43. <p>It’s common knowledge that Google has used their political, marketing and technical prowess <a href="https://www.magiclasso.co/insights/google-undermines-adblock/">to stop and co-opt effective ad blocking</a> on the web. What hasn’t been clear until recently is how Google is using the Chrome web browser to track individuals, even when ad blocking and in-built tracking prevention is enabled.</p>

  44. 

  45. <h3 id="tracking-three-ways">Tracking three ways</h3>

  46. 

  47. <p>Google recently invented a third way to track who you are and what you view on the web.</p>

  48. 

  49. <p>The first wave of web tracking worked via cookies. Each visitor to a page would be given a unique ID which would be stored within a browser cookie. Using third-party JavaScript tracking, this cookie was then cross-referenced and retrieved on pages you visited, even across different websites.</p>

  50. 

  51. <p>Eventually a profile of your browsing history would be created. Google (and other ad companies) then used this profile to determine the best ads to serve you, in order to prompt a click and a purchase.</p>

  52. 

  53. <p>However as cookie-based tracking became more obvious and intolerable, users employed ad blockers to prevent and block these cookies.</p>

  54. 

  55. <p>Consequently ad networks deployed a second way to track users called browser fingerprinting. Browser fingerprinting consists of collecting data about the configuration of your browser and system when you visit a site. This process can reveal a surprising amount of information about your software and hardware environment, and ultimately can be used to construct a unique identifier of you, called a browser fingerprint.</p>

  56. 

  57. <p>The browser fingerprint is then used to, once again, target advertising. In order to reduce the effectiveness of fingerprinting, some browsers like Safari have been changing how they identify the browser and its features to websites. This has effectively neutered this tracking approach.</p>

  58. 

  59. <p>With the first and second tracking approaches no longer as effective, Google has decided to up the ante and deploy tracking directly via its Chrome browser.</p>

  60. 

  61. <h3 id="chromes-unique-install-id">Chrome’s unique install ID</h3>

  62. 

  63. <p>As an open-source project, it’s possible to view the source code for the Chrome web browser. Insightful contributors to the code have <a href="https://github.com/w3ctag/design-reviews/issues/467#issuecomment-581944600">recently discovered</a> an insidious third way that Google tracks you across the web.</p>

  64. 

  65. <p>Each and every install of Chrome, since version 54, have generated a unique ID. Depending upon which settings you configure, the unique ID may be longer or shorter.</p>

  66. 

  67. <p>Irrespective, when used in combination with other configuration features, Google now generates and retains a unique ID in each Chrome installation. The ID represents your particular Chrome install, and as soon as you log into any Google account, is likely also linked directly to your individual Google profile.</p>

  68. 

  69. <p>The evil next step is that this unique ID is then sent (in the “x-client-data” field of a Chrome web request) to Google every time the browser accesses a Google web property. This ID is not sent to any non-Google web requests; thereby restricting the tracking capability to Google itself.</p>

  70. 

  71. <p>As well as being immoral, this step may also be illegal (at least in privacy sensitive jurisdictions) as it’s retaining and sending personal identifiers without informed consent.</p>

  72. 

  73. <p>So every time you visit a Google web page or use a third party site which uses some Google resource, this ID is sent to Google and can be used to track which website or individual page you are viewing. As Google’s services such as scripts, captchas and fonts are used extensively on the most popular web sites, it’s likely that Google tracks most web pages you visit.</p>

  74. 

  75. <p>Unfortunately for users of Google Chrome, this third wave tracking identifier will not be removed by using VPNs or Chrome based ad blockers.</p>

  76. 

  77. <h3 id="who-can-you-trust">Who can you trust?</h3>

  78. 

  79. <p>It has been repeatedly demonstrated that Google cannot be trusted with user privacy.  Their business model depends upon tracking and surveilling web users.</p>

  80. 

  81. <p>For a user who wants online privacy, the only option is to use a web browser whose creators aren’t funded via advertising. Creators who aren’t incentivised to continually gather more information about you. Luckily there are a number of alternative options available including Firefox or Safari. If you’re still using Google Chrome, it’s time to switch to a browser that isn’t built to monetise your privacy.</p>

  82. </article>

  83. 

  84. 

  85. <hr>

  86. 

  87. <footer>

  88.   <p>

  89.     <a href="/david/" title="Aller à l’accueil">🏠</a> •

  90.     <a href="/david/log/" title="Accès au flux RSS">🤖</a> •

  91.     <a href="http://larlet.com" title="Go to my English profile" data-instant>🇨🇦</a> •

  92.     <a href="mailto:david%40larlet.fr" title="Envoyer un courriel">📮</a> •

  93.     <abbr title="Hébergeur : Alwaysdata, 62 rue Tiquetonne 75002 Paris, +33184162340">🧚</abbr>

  94.   </p>

  95. </footer>

  96. <script src="/static/david/js/instantpage-3.0.0.min.js" type="module" defer></script>

  97. </body>

  98. </html>