4 ms·
What's the catch? Google doesn't need cookies anymore because they can track users with Android/Chrome/GMail/some other trick?
by palata 3y ago
What's the catch? Google doesn't need cookies anymore because they can track users with Android/Chrome/GMail/some other trick?
- fsflover 3y agohttps://news.ycombinator.com/item?id=26625369 https://news.ycombinator.com/item?id=26625369
- laszlojamf 3y agoGoogle tracks most users by them simply being logged in everywhere. I was working in this space a while back when FLoC was the next thing and the joke was that FLoC was just for the rest of us. Google always holds all the cards
- TekMol 3y agologged in everywhere Where? I doubt Google can track you because you are logged into HN.
- digitcatphd 3y ago~ 80% of browsers are Chrome, by my observation, they still track you even in 'incognito'
- izzydata 3y agoSo if I use Firefox and almost never encounter a website that uses a Google login then they aren't tracking me most of the time? It seems like they must have more tricks up their sleeve than that.
- AlexandrB 3y ago> It seems like they must have more tricks up their sleeve than that. Maybe, maybe not. Firefox market share is trivial at this point. I doubt Google invests a lot of time in figuring out how to track Firefox users specifically. Safari, especially on mobile, is a far more juicy target.
- capitainenemo 3y agoHow about people using gstatic fonts and js? People embedding google calendars or youtube videos? People using google captcha? People monetising their site with google ads? Combine that with standard fingerprinting techniques.
- renegat0x0 3y agoAre tracking pixels still a thing? If so it allows to fingerprint you, and track you down across sites.
- red-iron-pine 3y agodefinitely still a thing
- Thorrez 3y ago>Chrome, by my observation, they still track you even in 'incognito' Can you explain this? I don't thinks this is the case. Disclosure: I work at Google but not on Chrome.
- renegat0x0 3y agohttps://www.euronews.com/next/2024/01/01/google-settles-lawsuit-over-tracking-people-in-incognito-mode https://www.euronews.com/next/2024/01/01/google-settles-laws...
- ahahahahah 3y agoThis was the dumbest lawsuit ever. Like, users would go in incognito mode, sign into google while in incognito mode, and then be surprised that google as a company would track that activity. It's such a twist of logic to say that the incognito mode messaging would apply to google as a company rather than to the behavior of the browser itself.
- Thorrez 3y ago>sites using Google Analytics or Ad Manager collected information from browsers in Incognito mode, including web page content, device data, and IP address. https://arstechnica.com/tech-policy/2023/12/google-agrees-to-settle-in-chrome-incognito-mode-class-action-lawsuit/ https://arstechnica.com/tech-policy/2023/12/google-agrees-to... That doesn't sound like any sort of tracking backdoor in Chrome. That sounds like that same type of tracking would happen in Firefox private browsing mode. Well, maybe not because I think Firefox private mode has some sort of code that tries to strip out trackers. But if you disable that feature in Firefox, it sounds like Google would track Firefox private mode users the same as Chrome incognito users. I guess then you could consider the lawsuit to be complaining that Chrome doesn't have a feature to strip out trackers in incognito mode. Is that a realistic feature expectation?
- noirscape 3y agoChrome. Google is adding a dedicated "Topics API" to Chrome that they fully control the access to that does all tracking for them. (After repeatedly attempting to do it in an "agnostic" way that preserved privacy that just flat out didn't work, they just dropped the mask and openly started acting as gatekeepers for the Topics API.) That combined with the rollout of Manifest V3 permits them to axe adblockers whilst keeping full tracking enabled. The userbase percentage lost from Firefox users (around 3%, everything else runs a Firefox derivative or is iOS with Safari, which Google assumes is dead in the water due to the DMA) isn't enough to not have them transition fully to the Topics API at this point because of the ad profits they think they can get out of unwinding adblockers in Chrome. Google is closing the advertising jaws around Chrome and this is what that looks like.
- ahahahahah 3y agoThe "Topics API" isn't really for Google. Basically, in the market of ad platforms, platforms other than Google are much more reliant on third-party tracking than Google itself is. Given that, regulators would not allow Google to remove third party cookie support from Chrome because it would unfairly benefit their own ad platform. The "Topics API" (and previous attempts) have been Google trying to find the most privacy-preserving thing that they could use to replace third party cookies and that would convince the regulators to allow them to remove third party cookies.
- noirscape 3y ago...regulators aren't forbidding Google from blocking third party cookies as far as I can tell. I don't know what you're on about with that. The Topics API requires Google to approve your script before it works and if they didn't care about Ads and third party cookies, they'd have turned it off long ago.
- Scion9066 3y agoGoogle definitely can't just block third-party cookies on their own: https://blog.google/products/chrome/privacy-sandbox-tracking-protection/ https://blog.google/products/chrome/privacy-sandbox-tracking... On January 4, we'll begin testing Tracking Protection, a new feature that limits cross-site tracking by restricting website access to third-party cookies by default. We'll roll this out to 1% of Chrome users globally, a key milestone in our Privacy Sandbox initiative to phase out third-party cookies for everyone in the second half of 2024, subject to addressing any remaining competition concerns from the UK’s Competition and Markets Authority. https://assets.publishing.service.gov.uk/media/653a58e2e6c968000daa9b94/__Q3_2023_update_report____.pdf https://assets.publishing.service.gov.uk/media/653a58e2e6c96... We would like to reassure the ecosystem that deprecation of third-party cookies can only take place once the competition concerns, identified by the CMA during its investigation, are addressed by Google. We have asked Google to be clear about this in its communications. Under the Commitments, there will be a Standstill Period of 60 days that applies before third-party cookies can be removed. This period can be extended to 120 days. During the Standstill Period, we will determine whether third-party cookie deprecation can go ahead based on the evidence we are gathering. This includes evidence from tests of the tools conducted by Google and other market participants. Our aim is to gather evidence of the likely impacts of the changes by the middle of 2024. The Standstill Period will take place following this, and once testing has been completed.
- jefftk 3y agoGoogle committed to removing support for cross-site tracking (which here is being confusingly called "cookies") because other browsers were implementing it as a privacy measure. They've taken a long time to do it because they made a somewhat impractical promise to remove cross-site tracking while maintaining its economic benefits via new privacy-preserving APIs (PrivacySandbox). For example, see https://developers.google.com/privacy-sandbox/relevance/protected-audience https://developers.google.com/privacy-sandbox/relevance/prot... (Disclosure: until 2022 I worked in this area at Google)