5 ms·

Submitting a form with toggle controls set to the off position is not “building Twitter”. The only reason this would take 3 months rather than a few days is if

Submitting a form with toggle controls set to the off position is not “building Twitter”. 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.

Groxx 5y ago
There is also room for C) they had millions of crappy partial copies of the same pop-up, much of which had to be fixed by hand
- shadowgovt 5y ago
  It's D) The hard part is the backend data storage, not the frontend. 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.
shadowgovt 5y ago
> Submitting a form with toggle controls set to the off position is not “building Twitter”. That's also not what "reject all" does.
- account42 5y ago
  It should be effectively the same, otherwise A) they were lying before in the old cookie popup
  - shadowgovt 5y ago
    Not at all. The previous pop-up gave you the opportunity to switch off every item individually. What do you think would happen if new items were added? 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.
    - hrbf 5y ago
      That may well be. However, I’d argue that effects like these are just the cost of doing business at their scale – and therefore entirely their problem. No one outside of the affected corporation should need to care at all.
      - shadowgovt 5y ago
        Oh, definitely. This overview was an explanation for why "Just adding one new option" is a one-quarter project and not nearly as simple as people from smaller operations assume it will be. ... 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.

Groxx 5y ago

There is also room for C) they had millions of crappy partial copies of the same pop-up, much of which had to be fixed by hand

shadowgovt 5y ago
It's D) The hard part is the backend data storage, not the frontend. 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.

shadowgovt 5y ago

> Submitting a form with toggle controls set to the off position is not “building Twitter”. That's also not what "reject all" does.

account42 5y ago
It should be effectively the same, otherwise A) they were lying before in the old cookie popup
- shadowgovt 5y ago
  Not at all. The previous pop-up gave you the opportunity to switch off every item individually. What do you think would happen if new items were added? 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.
  - hrbf 5y ago
    That may well be. However, I’d argue that effects like these are just the cost of doing business at their scale – and therefore entirely their problem. No one outside of the affected corporation should need to care at all.
    - shadowgovt 5y ago
      Oh, definitely. This overview was an explanation for why "Just adding one new option" is a one-quarter project and not nearly as simple as people from smaller operations assume it will be. ... 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.