The blog post mentions:
> This update meant we needed to re-engineer the way cookies work on Google sites, and to make deep, coordinated changes to critical Google infrastructure.
> This update meant we needed to re-engineer the way cookies work on Google sites, and to make deep, coordinated changes to critical Google infrastructure.
Honestly I'm at the point where I just give up. Whomever gets to infiltrate beyond Firefox tracking protection and ublock: congratulations.
Yes, you will need to white list many websites, yes, you will also become appealed at the sheer amount of cookie requests you receive and thank God that you have installed noscript every day
Google cookies do not work that way. Ironically, one of the challenges is that some of them are firewalled from each other so that it's harder to aggregate a holistic picture of a user in one location. You know, for privacy reasons.
And not even moving an onClick handler is trivial given the layers of abstraction that Google's UIs are built on top of.
The only reason this would take 3 months rather than a few days is if:
A) they were lying before in the old cookie popup
B) they are dragging their feet out of spite
Not sure which is worse honestly.
People's intuition of how user data storage and retrieval works at Google scale doesn't align with the reality. Cost of storage (immediate and secondary), effect on creation of new permissions, privacy protection, user security (can this new option somehow be used to leak userdata or trick users into doing something they didn't want to do?), and (if they're only rolling this out in Europe) region gating all have to be accounted for.
That's also not what "reject all" does.
A) they were lying before in the old cookie popup
The new button sets a new default that affects new options for data collection. And yes, adding one new field that affects user configuration across all Google properties (or even two major Google properties, such as the main site and YouTube) is a one-quarter project. Privacy review, legal review, data storage assessment to make sure an additional Boolean isn't going to blow a limit somewhere, thinking through all permutations of options users could already have set to make sure that this new feature doesn't break existing user configurations... Hell, they probably had to do analysis to make sure that you couldn't uniquely identify users based on the setting because of how many / how few people would click reject all. And did they roll it out everywhere or just in europe? Europe only requires additional work.
It's a big corporation, extrapolating how it works from small corporations leads to inaccurate conclusions.
... in fact, I think this is indicative of the risk Google experiences now of disruption. At their scale, they are no longer agile. When a company is willing to spend money on a daily fine for exceeding the target deadline after three months, they're signalling strongly that smaller, more focused operations can out-maneuver them.