2 days ago I started a Google Takeout, and it's still in progress...
I excluded Photos and Drive, but the first tarball is 33GB... and for some reason it's named 002. Where is 001?
2 days ago I started a Google Takeout, and it's still in progress...
I excluded Photos and Drive, but the first tarball is 33GB... and for some reason it's named 002. Where is 001?
The other tarballs are just a few MBs long, but they're taking forever...
Tarball 007 was created at 2:48am, and 12 hours later there's still no 008.
(I do have plenty of Drive space left.)
Another oddity is that all tarballs from 003 through 007 contain Nest thermostat data.
I only started using Google Home 2 months ago, and I have only one thermostat... how can it produce so much data?!?
I'm not trying to build a conspiracy theory on #Google doing something shady with my account data....
I'm just very curious: what kind of bug or edge case would cause Google Takeout to behave in this manner? ๐คจ
Having worked at Google previously and having lots of friends who still work there doesn't particularly help.
No, Google employees cannot access PII of random users, although an on-call SRE for Takeout might be able to see error logs related to requests that are causing crashes or other issues...
Did you know that Google Takeout was previously known as "Google Data Liberation Front"?
I miss the days when a group of Googlers could spontaneously come up with a product like this... and launch it publicly with such an awesome logo ๐
@cmhobbs Yes, batch jobs like this get very low priority on Google production servers... they might get starved for I/O to data and even get suddenly killed if the job scheduler needs more memory for a spike of search requests or anything...
These long running jobs should checkpoint their progress frequently so they can resume, but it might not be feasible for some backends. Nest is an acquisition, so perhaps they're still storing data to some RDBMS? YouTube was initially on MySQL lol ๐
@patrick Actually, I'm unable to download the files currently... perhaps they're "locked" during the export?
But I can still preview them in drive...
@patrick Ah, it was caused by blocking third-party cookies in Chrome.
Drive is the first product I see that doesn't work with this setting...
All right, I was able to download some of my Nest dataset and (unsurprisingly) experiments and debug logs take up much more space than actual thermostat readings and settings.
Tarball 009 arrived, and contains an HTML file with a detailed report of export errors.
As I suspected, there must be some bug with the Nest / Home App exporter...
Just to be clear: I'm not pissed or anything...
I still believe Takeout is an awesome feature and all Internet service providers should be obligated (ethically AND legally) to provide an equivalent service to export user data.
By the way, when was the last time you backed up your #Mastodon account? ๐
Ah, actually Google Home and Nest are separate products with separate datasets, but both have buggy exporters lol
@benoit Back when I was living in Cambridge, we used various Hangouts chats for my shared house, my anime club and various groups of friends.
I wonder if the chat history will be migrated to Google Chat and remain searchable. I'd hate losing those memories when Hangouts finally shuts down...
@codewiz Hangouts 20GB ๐ฑ
Bobinas P4G is a social network. It runs on GNU social, version 2.0.1-beta0, available under the GNU Affero General Public License.
All Bobinas P4G content and data are available under the Creative Commons Attribution 3.0 license.