That's probably the least charitable way of looking at this. It's a tool for data portability that gives users access to their own content, in a way they weren't previous able to do. If the government wanted some data on a user I think they're going to get it from the company whether this service exists or not.
To be clear, that's not my logic.
You can use pretty much anything for good or bad. Rocks, Nitrogen, Automobiles, Thoughts.. it's an endless list.
If a developer was not oblivious to the fact that their code might be used for this other purpose, what do you think a typical developer a) would do and b) should do?
Now, as soon as Legal signs off, the production of the ZIP file is probably completely automated. And the programmers who made that possible probably believed their code was going to be used solely for their users' data portability.
(Disclaimer: Though I used to work there, all of the above is pure speculation.)
Its true that the Data Liberation Front did start as a group of 20%ers, but like the much less successful GMail, we got turned in a real team and now we have reorgs and TPS and everything.
[0] Check out the new My Activity service as an example of some of the new data we have added: https://takeout.google.com/settings/takeout/custom/my_activi...
[1] https://thejournal.com/articles/2016/12/09/google-unveils-gr...
Running a quasi-official blog without blessing didn't last either [0]. Glad to hear the team got turned into a permanent one internally, but the lack of a public info on its existence doesn't fill me with confidence that this is something Google wants or prioritises at a management level.
The gp was talking about companies' engineers writing "user-friendly data-portability features. Across all product lines". Is that the case with Takeout at Google, or is it just a job given to one relatively small team of self-starters working on a project that was never spearheaded by management?
i see the ability to download and delete your account as a good improvement
I think.
It used to be really hard to gather all that information and package it up in a nice little bundle. It used to be hard for a company to get their software engineers to quietly implement such functionality across all products without getting internal angst and bad press leaks.
But now, companies can just tell their software engineers that they're writing user-friendly data-portability features. Across all product lines, they'll happily code away, completely oblivious to the fact that their code is also going to be used for this other purpose.