Live data from Hacker News

Google extends third party cookie deadline until late 2023

digiday.com

51–60 of 69 posts

Re: Google extends third party cookie deadline until late 2023

#51
post #36
post #14

> We believe the web community needs to come together to develop a set of open standards to fundamentally enhance privacy on the web, giving people more transparency and greater control over how their data is used. > In order to do this, we need to move at a responsible pace. This will allow sufficient time for public discussion on the right solutions, continued engagement with regulators, and for publishers and the…

news in the past two weeks has been of eu antitrust actions over issues including this 3rd party cookies change, and uk demanding their regulators get veto power over changing 3rd party cookies. google is trying to escape a colossal regulatory hellfire that has sprung up in the last two weeks over this attempt to do the right thing, that other browsers already do. shit has just gone defcon4 & they are adding time to…

Google is not doing the right thing.

They're solidifying control over the web.

Re: Google extends third party cookie deadline until late 2023

#52
post #43

Earlier quoted context omitted.

I think they should deprecate Chrome or spin it off into another company. The issue here is monopoly. Also, regulators aren't upset about them blocking third party cookies, every other browser already does that. They're upset about Google's attempts to inject new Google-controlled tracking methods that grant them a further advantage at the cost of all their competitors. The answer is simple: Block third party cookies…

> Also, regulators aren't upset about them blocking third party cookies, every other browser already does that As far as I can tell, that is untrue. CMA has explicitly stated concerns with any removal of third party cookies by default from Chrome, since they believe ad tech companies are dependent on them but Google isn't. Any new mechanisms introduced for privacy preserving ad targeting are irrelevant, except insofa…

> CMA has explicitly stated concerns with any removal of third party cookies by default from Chrome, since they believe ad tech companies are dependent on them but Google isn't

This is because Google owns Chrome, and hence, doesn't need the cookies to collect web activity. The solution, as I said, is to force them to spin off Chrome.

> Oh, come on.

It's actively harmful to consumers. Chrome is like asbestos, we're better off just... not using it. There are safer alternatives out there.

Re: Google extends third party cookie deadline until late 2023

#53
post #34

Earlier quoted context omitted.

Chrome still lets you block third party cookies. Not with an extension or some low level tweak; it's just in the settings.

Is there a use case for third party cookies outside of ad tracking? I’ve had it disabled for years and don’t recall it breaking any website I actually care to use.

Once case is iframing a site where people will get logged-in behavior without requiring them to log in to each site individually. For example, an embedded video player that wants to disable ads for subscribers or a micropayments service that needs to recognize which account to charge.

(Disclosure: I work on ads at Google, speaking only for myself)

Re: Google extends third party cookie deadline until late 2023

#54
post #14

> We believe the web community needs to come together to develop a set of open standards to fundamentally enhance privacy on the web, giving people more transparency and greater control over how their data is used. > In order to do this, we need to move at a responsible pace. This will allow sufficient time for public discussion on the right solutions, continued engagement with regulators, and for publishers and the…

This is Google admitting FLoC is dead, so they're going to just leave things as they are instead.

Re: Google extends third party cookie deadline until late 2023

#56
post #46
post #10

Earlier quoted context omitted.

Are you saying you can't download files from Google Drive in the default Safari configuration?

I don't use Safari or any AppleWare but I disable 3rd party cookies in Chrome and I can't download files from Google Drive unless I temporarily enable it.

I just tried it:

* On Safari it works correctly with default settings.

* On Chrome with third party cookies disabled it doesn't work and takes you to https://support.google.com/drive/answer/2423534

I poked around in dev tools, and it looks like what's happening is in serving to Safari it gives a download link that includes authentication information, but when serving to Chrome it doesn't. Perhaps because it's expecting to get third party cookies?

My guess is that they rolled out special handling for Safari when it started blocking third-party cookies by default, which will eventually make its way to all browsers?

(Disclosure: I work on ads at Google, speaking only for myself)

Re: Google extends third party cookie deadline until late 2023

#57
post #14

> We believe the web community needs to come together to develop a set of open standards to fundamentally enhance privacy on the web, giving people more transparency and greater control over how their data is used. > In order to do this, we need to move at a responsible pace. This will allow sufficient time for public discussion on the right solutions, continued engagement with regulators, and for publishers and the…

I'd like to comment about this part from the Google blog:

> By ensuring that the ecosystem can support their businesses […] we can all ensure that free access to content continues.

Internally, Google believes that with Ads they are doing good to the world: the mission of Google Ads literally starts with "power the open and free internet…" (you can find it online). The idea is that for every site online that carries ads on it ("publishers"), it's the website that has chosen to put ads there, to make money. So the assumption is that if websites couldn't make money from ads (or if they made significantly less money, because of worse ads) they'd either stop hosting the website or put it behind a paywall, and users wouldn't get "free access to content".

Of course this applies only to those sites on the internet that have ads at all (doesn't apply to HN, Wikipedia, government/academic websites etc), but then again, ad-tech third-party cookies are also only present on such sites anyway.

-----

(I work at Google in Ads but not on anything related to any of this; this is all my own opinion posted from an alternate account. I find ads annoying and use an adblocker personally, so I was surprised to encounter this point of view.)

-----

Rather than "Google's consumer privacy strategy is all smoke and show", the sense I get internally is that Google is serious about "as much privacy as possible without seriously affecting our revenue". A couple of examples:

- [Edit: Added this point later.] In 2019 most (all I think? It's hard to tell) of "what Google knows about you" was consolidated into a single "My Activity" page (https://myactivity.google.com/), with user controls for turning things off or individual items. This was a lot of effort (Sundar at TGIF spoke proudly of it; see also the blog post https://blog.google/technology/safety-security/putting-you-i...), and personally as a user I feel better having control and visibility over what exactly what Google knows about me, but I don't remember much media coverage or discussion of this; maybe not everyone finds this exciting. :-)

- In 2020, they changed the default for new users to auto-delete this "Web and App Activity" after 18 months. Probably, this doesn't hurt Google's revenue much because data older than this is not very useful for Ads anyway, but it is still an increase in privacy compared to Google remembering everything about you forever (just not as good for privacy as defaulting to Off).

- FLOC is their answer to "how can we have the same level of user-targeting in ads, with more privacy?" The idea is that to decide whether to show me ads about shoes it doesn't need to know every site I've ever visited; it just needs to know roughly what kind of person I am. The old model is that every site carrying ads by Google would have a third-party Google cookie that would record your visit; the new FLOC model is that your browser privately builds up a profile about you and just reveals which bucket you fall into. Obviously your browser tracking you isn't as much privacy as no tracking at all, but if you start with the assumption that well-targeted ads ought to exist and try to maximize privacy under that constraint, then FLOC is a reasonably good answer to that question. (I know some smart privacy/crypto engineers—not from the Ads org—who've worked hard on developing/analyzing it…)

- [Edit: Added this point later.] You can see this Chrome blog post https://blog.google/products/chrome/privacy-sustainability-a... where they say "Overall, we felt that blocking third-party cookies outright without viable alternatives for the ecosystem was irresponsible, and even harmful, to the free and open web we all enjoy" — this is something Apple can afford to do because they make money from users using Apple products and iOS apps; they don't benefit from content existing on the web. (See below.)

A couple of other points:

- Google makes a significant chunk of its revenue from ads on its own sites (Google Search, YouTube, etc), where third-party cookies or FLOC are irrelevant. So all this is only about ads on other websites, where Google keeps a fraction of the advertiser money and the rest goes to the "publisher", i.e. the website (I've seen a number like 68% somewhere, not sure whether it applies to all websites). So if all users suddenly started blocking third-party cookies today, the (ad-carrying) websites will together lose more money than Google does, and (for many of them) a greater fraction of their revenue.

- Well targeted ads ("show my ads to people who are likely to buy my product") are worth a lot more (as in, advertisers pay more, as they can measure more conversions) than ads based on nothing more than, say, the content of the web page/site you're visiting (or even worse, completely generic ads: remember "punch the monkey"?). So if ads stopped being personalized, each website would have to carry even more ads to continue making the same amount of money. (Though frankly… there are some websites that seem to have hit physical limits by filling every inch of space with ads, those cannot possibly get worse I imagine.)

- Google stands to profit if there's more content on the web. If every ad-supported site chose to (shut down or) move its content to (say) apps instead, Apple would be ok. Google benefits from content staying on the web because those websites will carry Google (and other) ads, but also indirectly because the web itself becomes more useful and people will continue to use Google Search rather than expect content not to exist on the web (and ads on Search make even more money for Google than ads on other websites). In fact, one thing common to many of Google's products is that they increase the value of the web: Search makes the web more useful; Gmail was the start of web mail being a significant alternative to Outlook etc; similarly Maps; Chrome when it first appeared pioneered tab-isolation and seemed to cause fewer frustrations from browser crashes (remember the comic? https://www.google.com/googlebooks/chrome/); even the much-hated AMP was intended to fix the problem of websites being too slow on mobile (the popular consensus on HN seems to be that it made things worse).

So while it indeed seems true that Apple can afford to pursue the user-privacy angle in Safari harder than Chrome can (Apple doesn't have publishers and advertisers among its constituents), it's also arguable that Google's approach helps keep content on the web and is aligned with user interests that way. (Though personally as a user, I wonder: how many ad-supported websites are really useful to me anyway? I'd be fine and possibly happier if most of the ad-supported websites disappeared and only non-commercial content remained on the web… may not be true for many people though.)

----

Edit: Also, note that (as the article says) this delay is because the U.K.’s Competition and Markets Authority forced it. (Their page is here: https://www.gov.uk/government/news/cma-to-investigate-google... — my understanding is that they thought blocking third-party cookies would make it harder for other ad-tech companies.) Left to itself, Google would like to charge ahead with replacing third-party cookies with FLOC.

Re: Google extends third party cookie deadline until late 2023

#58
post #54
post #14

> We believe the web community needs to come together to develop a set of open standards to fundamentally enhance privacy on the web, giving people more transparency and greater control over how their data is used. > In order to do this, we need to move at a responsible pace. This will allow sufficient time for public discussion on the right solutions, continued engagement with regulators, and for publishers and the…

This is Google admitting FLoC is dead, so they're going to just leave things as they are instead.

Are you saying all of Privacy Sandbox APIs are dead or just FLoC?

Re: Google extends third party cookie deadline until late 2023

#59
post #34

Earlier quoted context omitted.

Chrome still lets you block third party cookies. Not with an extension or some low level tweak; it's just in the settings.

Is there a use case for third party cookies outside of ad tracking? I’ve had it disabled for years and don’t recall it breaking any website I actually care to use.

I had to enable third party cookies to log into Pearson’s online learning garbage. It appears the use case here is standing up poorly designed websites.

Re: Google extends third party cookie deadline until late 2023

#60
post #58
post #54

Earlier quoted context omitted.

This is Google admitting FLoC is dead, so they're going to just leave things as they are instead.

Are you saying all of Privacy Sandbox APIs are dead or just FLoC?

Personally, I don't think the concept is a problem the industry can solve on their own.

If Google wasn't having anti-trust worries, maybe they could force it to happen, but it's too blatant now.

My assumption is 3rd party cookies die to regulation, and nothing gets enough consensus to replace them.

Post reply on HN