teamjimmyy

3 ms·

1. 1.▲
   by teamjimmyy 7y ago

   We now have trackers acting like first-party properties, but where do you draw the line between first-party and third-party? What I mean is, if I build my own in-house analytics app that does a lot of what Adobe's product does, should
2. 2.▲
   by teamjimmyy 13y ago

   Yeah, I saw the bit about turning off all 3rd party cookies, which made me happy as I already do that myself. As for the ubiquity and potential for data sharing among Google services, I suppose I hadn't though that entirely through. I
3. 3.▲
   by teamjimmyy 13y ago

   I'll say here what I said in the other reply, but briefly. There's a difference between a 3rd party doing the analytics and a 3rd party cookie. GA can (and should) use a 1st party cookie for this, which would make it impossible fo
4. 4.▲
   by teamjimmyy 13y ago

   This isn't strictly true, which is why I made the differentiation above between 1st and 3rd party cookies. With the 1st party cookie you'd get a new GA cookie on each site (e.g. mozilla-GA, ycombinator-GA, etc), making those corre
5. 5.▲
   by teamjimmyy 13y ago

   I don't get it. Why is this different from inspecting your web logs? Sure you lose the first-party cookie aspect, but I bet you can get awful close just looking at the request IPs. There's "tracking" inherent in how ever