"How To Turn Off Google’s “Privacy Sandbox” Ad Tracking—and Why You Should": <a href="https://www.eff.org/deeplinks/2023/09/how-turn-googles-privacy-sandbox-ad-tracking-and-why-you-should" rel="nofollow">https://www.eff.org/deeplinks/2023/09/how-turn-googles-priva...</a>
> Meanwhile, you can expect websites all over the internet to fight to get you to log in so they can track you themselves.<p>There's a part of me that welcomes this. Sites that require logins for no good reason are at least broadcasting their desire to spy on you, which means you can make an informed decision. That's orders of magnitude better than sites that just spy on you without warning you.
> That will spell the death of cookies across the web, ushering in one of the biggest changes in the history of the internet.<p>First-party cookies are not going away. I think the article should've explained that the website domain in the URL bar is the first party. The first-party website can load things from other parties, the third parties.<p>> For one thing, Chrome isn’t the first browser to block tracking cookies (formerly known as third-party cookies). Safari and Firefox, for example, have blocked these cookies for a long time.<p>Not all third-party cookies are tracking cookies. I think Firefox blocks only third-party tracking cookies by default, not all third-party cookies [1]. Not sure about Safari. But it's hard for the average website visitor to tell whether a third-party cookie is for tracking, so blocking all third-party cookies is a good idea.<p>> Others, especially big retailers including Amazon, Disney, and Walmart, are developing their own advertising businesses harnessing the mountains of data they already have about their customers. Meanwhile, you can expect websites all over the internet to fight to get you to log in so they can track you themselves.<p>I'm glad that the article brings up login walls.<p>Unfortunately, the article doesn't mention fingerprinting at all. Fingerprinting [2] lets third parties on website X figure out that the user who is currently visiting website X also visited website X a day ago. Fingerprinting also lets third parties on website X figure out that the user who is currently visiting website X also has visited a website Y that has the same third parties. The Topics API [3] (used to be the FLoC API) in the "Privacy Sandbox" gives third parties information about the user's preferences. Even though removing third-party cookies means removing one tracking vector, <i>Google Chrome's "Privacy Sandbox" gives third parties a new tracking vector</i>.<p>From less privacy to more privacy, the current order is roughly:<p>1. third-party cookies + "Privacy Sandbox" + fingerprinting<p>2. third-party cookies + fingerprinting<p>3. "Privacy Sandbox" + fingerprinting<p>4. non-tracking third-party cookies + fingerprinting<p>5. fingerprinting<p>Google Chrome is type 1 now and will be type 3 in the future. Firefox is type 4. You can manually disable all third-party cookies for Firefox (type 5) [1]. Firefox mitigates fingerprint-based tracking, but fingerprinting is impossible to eliminate completely. Regardless, today's Firefox already is a net-positive for privacy compared to future third-party-cookieless Google Chrome.<p>[1] <a href="https://support.mozilla.org/en-US/kb/third-party-cookies-firefox-tracking-protection" rel="nofollow">https://support.mozilla.org/en-US/kb/third-party-cookies-fir...</a><p>[2] <a href="https://coveryourtracks.eff.org/learn" rel="nofollow">https://coveryourtracks.eff.org/learn</a><p>[3] <a href="https://www.eff.org/deeplinks/2023/09/how-turn-googles-privacy-sandbox-ad-tracking-and-why-you-should" rel="nofollow">https://www.eff.org/deeplinks/2023/09/how-turn-googles-priva...</a>