3 ms·

Aren't browsers shifting to a per-domain cookie jar? While you can never prevent one specific site from tracking you, this still doesn't (directly) allow your

Aren't browsers shifting to a per-domain cookie jar? While you can never prevent one specific site from tracking you, this still doesn't (directly) allow your activity on Site A to be linked to activity on Site B, does it? Of course, fingerprinting combined with IP addresses will ultimately allow something that comes very close to it, so the current state (a few hundred trackers per website, all ending up harmlessly incrementing the adblocker's counter) is better for privacy for power-users, but I'm not sure if this is the big "game over".

lewantmontreal 5y ago
This is what I’m interested in. Article itself did not mention cross site tracking. Every website having their own tracking subdomain makes third party cookies not work cross site even without browser changes.
- GekkePrutser 5y ago
  They can still cross-track based on IP or any other fingerprint worthy information. I expect this is exactly what they're doing. Doing this all on a central service makes this process much easier unfortunately...
- pixeldetracking 5y ago
  yes, they would need to get another identifier, and that's what is done with players like Facebook. Sorry another of my articles in french: https://pixeldetracking.com/fr/les-signaux-resilients-de-facebook-ou-comment-la-surveillance-sadapte https://pixeldetracking.com/fr/les-signaux-resilients-de-fac..., but Facebook is making it easy to integrate their "Conversion API (CAPI)" with GTM Server-Side tagging
  - tgsovlerkhgsel 5y ago
    But that should only help e.g. a web store to track you from the ad you clicked, which seems reasonable. It should not allow e.g. Facebook to link your activity on a news site to your Facecbook cookie, because while you're on cnn.com, your browser is using the cnn.com-specific cookie jar for everything, including the like button?
- callmeal 5y ago
  The cross site tracking is done by a third party. From reading the docs, the way it works is, publisher sets a unique id, browsers send that unique id to the publishers domain, publisher forwards that (via the tag manager app engine) to the third party.
josefx 5y ago
Google is pushing to have the browser itself track your interests and share them with whoever asks. The first attempt FloC backfired rather quickly as it was an all around privacy nightmare. The second attempt Topics promises to fix a lot of the problems FloC had but that is not a high bar and Google left itself a lot of room for future changes.

lewantmontreal 5y ago

This is what I’m interested in. Article itself did not mention cross site tracking. Every website having their own tracking subdomain makes third party cookies not work cross site even without browser changes.

GekkePrutser 5y ago
They can still cross-track based on IP or any other fingerprint worthy information. I expect this is exactly what they're doing. Doing this all on a central service makes this process much easier unfortunately...
pixeldetracking 5y ago
yes, they would need to get another identifier, and that's what is done with players like Facebook. Sorry another of my articles in french: https://pixeldetracking.com/fr/les-signaux-resilients-de-facebook-ou-comment-la-surveillance-sadapte https://pixeldetracking.com/fr/les-signaux-resilients-de-fac..., but Facebook is making it easy to integrate their "Conversion API (CAPI)" with GTM Server-Side tagging
- tgsovlerkhgsel 5y ago
  But that should only help e.g. a web store to track you from the ad you clicked, which seems reasonable. It should not allow e.g. Facebook to link your activity on a news site to your Facecbook cookie, because while you're on cnn.com, your browser is using the cnn.com-specific cookie jar for everything, including the like button?
callmeal 5y ago
The cross site tracking is done by a third party. From reading the docs, the way it works is, publisher sets a unique id, browsers send that unique id to the publishers domain, publisher forwards that (via the tag manager app engine) to the third party.

josefx 5y ago

Google is pushing to have the browser itself track your interests and share them with whoever asks. The first attempt FloC backfired rather quickly as it was an all around privacy nightmare. The second attempt Topics promises to fix a lot of the problems FloC had but that is not a high bar and Google left itself a lot of room for future changes.