home.social

#googletakeout — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #googletakeout, aggregated by home.social.

fetched live
  1. MakeUseOf: I downloaded everything Google knows about me and queried it like a database. “I knew Google had a lot on me. I didn’t expect it to show up as several gigabytes of raw files that basically amounted to a relational database of my own life. So that’s what I decided to do with it — I grabbed my full Google Takeout archive, dumped the JSON into a local SQLite database, and started […]

    https://rbfirehose.com/2026/08/03/makeuseof-i-downloaded-everything-google-knows-about-me-and-queried-it-like-a-database/
  2. MakeUseOf: I downloaded everything Google knows about me and queried it like a database. “I knew Google had a lot on me. I didn’t expect it to show up as several gigabytes of raw files that basically amounted to a relational database of my own life. So that’s what I decided to do with it — I grabbed my full Google Takeout archive, dumped the JSON into a local SQLite database, and started […]

    https://rbfirehose.com/2026/08/03/makeuseof-i-downloaded-everything-google-knows-about-me-and-queried-it-like-a-database/
  3. #nerdystuff in pausa pranzo

    #GoogleTakeout ti lascia scaricare (quasi) tutto quello che Google sa di te: email, foto, cronologia, in un unico pacchetto scomodo da aprire e illuminante da guardare.

  4. #nerdystuff in pausa pranzo

    #GoogleTakeout ti lascia scaricare (quasi) tutto quello che Google sa di te: email, foto, cronologia, in un unico pacchetto scomodo da aprire e illuminante da guardare.

  5. #TechIsShitDispatch
    #Google provides no mechanism for exporting blood pressure data from inside #GoogleFit where I entered it.
    The only way to export it is to export all Fit data in #GoogleTakeout.
    That means I'm exporting 229MB of data (compressed), an export which takes over an hour to produce, to get access to the 4.1KB (compressed) of blood pressure data I want.

  6. #TechIsShitDispatch
    #Google provides no mechanism for exporting blood pressure data from inside #GoogleFit where I entered it.
    The only way to export it is to export all Fit data in #GoogleTakeout.
    That means I'm exporting 229MB of data (compressed), an export which takes over an hour to produce, to get access to the 4.1KB (compressed) of blood pressure data I want.

  7. falls ihr ein Google-Konto habt und es löschen wollt: mit #GoogleTakeout könnt ihr euch alle Daten sehr schnell und leicht runterladen - auch z.B. eure Gmails und Chats.

    takeout.google.com/ #unplugTrump

  8. falls ihr ein Google-Konto habt und es löschen wollt: mit #GoogleTakeout könnt ihr euch alle Daten sehr schnell und leicht runterladen - auch z.B. eure Gmails und Chats.

    takeout.google.com/ #unplugTrump

  9. Google už zase prudí s tím, že mi na jeho službách zbývá už jen 1,45 GB místa. Drive i Photos mám v zanedbatelných velikostech, ale Gmail má 9,3 GB.

    Dal jsem druhou šanci Google One Storage Manager. Ano, našlo to pár bizarních e-mailů, které měly víc než 20 MB, ale kdybych si tím měl uvolnit gigabajty, musel bych si s tím hrát týden. Nejde to ani seřadit od největších! Zjevně je to tam jen na oko, aby člověk prostě zmáčkl všudypřítomné tlačítko „Get more storage“ a neřešil to.

    Asi nemám sílu přecházet s e-mailem jinam, ale konečně mě napadlo aspoň polovičaté řešení. Přes takeout.google.com/ si stáhnu zálohu celého Gmailu v otevřeném formátu a pak prostě udělám nějaký cutoff a smažu z Gmailu vše, co je víc jak 10 let staré. Kdybych to potřeboval, budu to mít na disku jako MBOX.

    Je v tomto řešení nějaká mezera, kterou přehlížím?

    #gmail #googletakeout #googleonestoragemanager #storagefull #cloud #enshittification

  10. Google už zase prudí s tím, že mi na jeho službách zbývá už jen 1,45 GB místa. Drive i Photos mám v zanedbatelných velikostech, ale Gmail má 9,3 GB.

    Dal jsem druhou šanci Google One Storage Manager. Ano, našlo to pár bizarních e-mailů, které měly víc než 20 MB, ale kdybych si tím měl uvolnit gigabajty, musel bych si s tím hrát týden. Nejde to ani seřadit od největších! Zjevně je to tam jen na oko, aby člověk prostě zmáčkl všudypřítomné tlačítko „Get more storage“ a neřešil to.

    Asi nemám sílu přecházet s e-mailem jinam, ale konečně mě napadlo aspoň polovičaté řešení. Přes takeout.google.com/ si stáhnu zálohu celého Gmailu v otevřeném formátu a pak prostě udělám nějaký cutoff a smažu z Gmailu vše, co je víc jak 10 let staré. Kdybych to potřeboval, budu to mít na disku jako MBOX.

    Je v tomto řešení nějaká mezera, kterou přehlížím?

    #gmail #googletakeout #googleonestoragemanager #storagefull #cloud #enshittification

  11. Ugh, trying to disentangle my stuff from Google is such a pain. Feels like it has infiltrated all corners of my life. Next up: remove all my images (so many!) from #googlephotos to my external drive.You can't just "select all" and move it -- oh, nooo! You have to use their product, #googletakeout to do it. I'm wondering what's the catch . . .

  12. Ugh, trying to disentangle my stuff from Google is such a pain. Feels like it has infiltrated all corners of my life. Next up: remove all my images (so many!) from #googlephotos to my external drive.You can't just "select all" and move it -- oh, nooo! You have to use their product, #googletakeout to do it. I'm wondering what's the catch . . .

  13. Migrating from Google Photos to Immich Via Google Takeout

    Reading Time: 5 minutes

    In an ideal world Google Photos, iCloud Photos, MyCloud (Swisscom) and other photo backup solutions would back up your photos into a directory structure that you can access and download from with ease and convenience. Unfortunately non of them want to offer that. That is why finding a workflow to get data out is worthwhile.

    Remember, a cloud solution, where you can't get media files back out, is not a backup solution. It's just a synching solution. That's why Immich and kDrive are interesting alternatives.

    The Problem

    If you're like me you have been taking videos and photos for decades and in that time you have taken gigabytes worth of photos and terabytes worth of video. If we save everything to a hard drive then we're fine but because we're in the age of laptops and mobile phones we're backing up to the cloud, and applications are offloading our data from MacOS, iOS and Android. The result is that we no longer have local copies of files and that's where Google Takeout comes in.

    Google Takeout

    Google Takeout is a tool provided by Google One to export data from Google services to have a local backup. A few years ago when I first considered leaving Google One for kDrive, because that solution was cheaper I found that exporting all my data would be time consuming.

    The reason for this is that I had over a hundred zip files to download from Google Drive and that would take hours, if not days to do. Instead, at the time, I was able to backup Google Photos directly to Infomaniak kDrive. With kDrive I could download the files automatically via the kDrive desktop app. I won't elaborate any further because that solution is no longer available.

    Takeout Options

    Google Takeout gives you the option of downloading 1GB, 2GB, 10GB, 50GB zip files and more. If you have 360 GB of files, as I do, the most convenient solution is to download the 50GB files as you only have eight files to download. With the 2gb version I would have had 186 files to download. It takes half a day or more for the files to be ready.

    Unzipping and Metadata

    Safari will want to automatically "open" the zip files but I chose not to have this option because I want to keep the zips. I downloaded all eight files, and before doing anything else I backed up the eight files to a second disk as a backup. I then unzipped all eight zips. This takes time so let it work overnight. This is a good time to work on something else.

    Folders and Json

    Google Takeout creates directories for each album but it also creates albums per year. This means that plenty of files are duplicated, at the very least.

    My natural instinct, as a media asset manager was to see this file organisation and tidy up. Don't make this mistake if you're going to use Immich CLI or Exif tool. The mistake is not critical but if you want to save time then it is not required.

    The JSON files that are created by Google Takeout expect the folder structure that it creates. If you tidy things up then Exif tool will look for files and not find them because it's looking in "Google Takeout 5" whereas you have everything in "Google Takeout". The result is that exif will fail to update exif data for thousands of photos.

    Getting AI Help

    Using the Exif tool might be daunting, and that's where Google Gemini or another AI solution can help. Sometimes you can read the fabulous manual but feel confused. With Gemini, Le Chat by Mistral, or other you can ask for help and it will.

    Of course, with AI, it might say "Use this prompt" and it might be wrong. That's why it's good to test on a small folder first, see if there are any errors. If you see there are errors you can fix them. When things work well, then you can try in a second and third directory.

    The Limitation

    With event specific folders that span a single folder this approach worked fine but it's when I was exporting "photos from 2010" that I noticed that it was looking for the folder structure that I had habitually destroyed as a media asset manager.

    That's why you keep the zip files. With the zip files intact you can extract the files and folders and start again, this time knowing that the command prompt is the right one and you can let Exif tool work in the background.

    Double Checking

    When Exiftool is done there are three ways to see if the operation was a success. The first is the summary after running the command. The second is to check individual files to see if the creation date is correct and the first test is to upload to immich and see if the files are uploaded with the correct date and time. When these three steps are complete you can scale up.

    Populating Immich

    The Fun part is when you start populating Immich. It is gratifying to see images sorted by date and time and for people to be recognised, and for us to see if we remember the names of friends from 15-20 years ago. It's also fun to see how mobile phones and photo cameras have improved over the years. It's also nice not to be trapped by iCloud or Google Photos anymore.

    Have a Test Instance or a Test Account

    I recommend having a test instance of Immich or at the very least a test account. If something goes wrong it's better to see it go wrong on a test instance rather than in production. I'd rather make sure all photos load into the right year, before seeing thousands of photos added to the day the Google Takeout archive was created.

    Things to Watch Out For

    • Duplicates: If you edited the rotation, adjusted histograms or anything else you might have three or four copies of the same image showing up.

    • Creation Date: With some photos I found that they are sorted by the creation date for the zip, rather than their original creation date. In these cases it's worth checking to see if they are duplicates or if you need to correct the date and time information.

    • Keep the Zips: If you make a mistake you can start over

    • Keep the file and folder structure: The JSON files are optimised for Google Takeout Folder structures.

    • Test Small and then scale up

    And Finally

    When I hit the 200 GB limit many years ago I upgraded to the 2TB plan and I was happy with it, but I didn't use all of that space so I was paying for more than I needed. As many people have said before me, if iCloud, Google One and other solutions had more tiers then we could upgrade one small step at a time, rather than catapulting from 200 GB to Terabytes.

    Another point is that with larger file export sizes breaking out of Google Photos is almost easy, in contrast to before. When you had too download hundreds of zip files, unzip them, and then re-consolidate everything you were speaking of a huge investment in time. Now, within a day or two, you can be out of Google Photos and into Immich.

    One of my key reservations about using cloud synching tools as a backup solution is that it was very hard to get data out, whereas now it is considerably easier.

    Upon completion of this process, if I tidy up my e-mails I could revert to Google's free tier.

    #exiftools #googlePhotos #googleTakeout #immich
  14. Migrating from Google Photos to Immich Via Google Takeout

    Reading Time: 5 minutes

    In an ideal world Google Photos, iCloud Photos, MyCloud (Swisscom) and other photo backup solutions would back up your photos into a directory structure that you can access and download from with ease and convenience. Unfortunately non of them want to offer that. That is why finding a workflow to get data out is worthwhile.

    Remember, a cloud solution, where you can't get media files back out, is not a backup solution. It's just a synching solution. That's why Immich and kDrive are interesting alternatives.

    The Problem

    If you're like me you have been taking videos and photos for decades and in that time you have taken gigabytes worth of photos and terabytes worth of video. If we save everything to a hard drive then we're fine but because we're in the age of laptops and mobile phones we're backing up to the cloud, and applications are offloading our data from MacOS, iOS and Android. The result is that we no longer have local copies of files and that's where Google Takeout comes in.

    Google Takeout

    Google Takeout is a tool provided by Google One to export data from Google services to have a local backup. A few years ago when I first considered leaving Google One for kDrive, because that solution was cheaper I found that exporting all my data would be time consuming.

    The reason for this is that I had over a hundred zip files to download from Google Drive and that would take hours, if not days to do. Instead, at the time, I was able to backup Google Photos directly to Infomaniak kDrive. With kDrive I could download the files automatically via the kDrive desktop app. I won't elaborate any further because that solution is no longer available.

    Takeout Options

    Google Takeout gives you the option of downloading 1GB, 2GB, 10GB, 50GB zip files and more. If you have 360 GB of files, as I do, the most convenient solution is to download the 50GB files as you only have eight files to download. With the 2gb version I would have had 186 files to download. It takes half a day or more for the files to be ready.

    Unzipping and Metadata

    Safari will want to automatically "open" the zip files but I chose not to have this option because I want to keep the zips. I downloaded all eight files, and before doing anything else I backed up the eight files to a second disk as a backup. I then unzipped all eight zips. This takes time so let it work overnight. This is a good time to work on something else.

    Folders and Json

    Google Takeout creates directories for each album but it also creates albums per year. This means that plenty of files are duplicated, at the very least.

    My natural instinct, as a media asset manager was to see this file organisation and tidy up. Don't make this mistake if you're going to use Immich CLI or Exif tool. The mistake is not critical but if you want to save time then it is not required.

    The JSON files that are created by Google Takeout expect the folder structure that it creates. If you tidy things up then Exif tool will look for files and not find them because it's looking in "Google Takeout 5" whereas you have everything in "Google Takeout". The result is that exif will fail to update exif data for thousands of photos.

    Getting AI Help

    Using the Exif tool might be daunting, and that's where Google Gemini or another AI solution can help. Sometimes you can read the fabulous manual but feel confused. With Gemini, Le Chat by Mistral, or other you can ask for help and it will.

    Of course, with AI, it might say "Use this prompt" and it might be wrong. That's why it's good to test on a small folder first, see if there are any errors. If you see there are errors you can fix them. When things work well, then you can try in a second and third directory.

    The Limitation

    With event specific folders that span a single folder this approach worked fine but it's when I was exporting "photos from 2010" that I noticed that it was looking for the folder structure that I had habitually destroyed as a media asset manager.

    That's why you keep the zip files. With the zip files intact you can extract the files and folders and start again, this time knowing that the command prompt is the right one and you can let Exif tool work in the background.

    Double Checking

    When Exiftool is done there are three ways to see if the operation was a success. The first is the summary after running the command. The second is to check individual files to see if the creation date is correct and the first test is to upload to immich and see if the files are uploaded with the correct date and time. When these three steps are complete you can scale up.

    Populating Immich

    The Fun part is when you start populating Immich. It is gratifying to see images sorted by date and time and for people to be recognised, and for us to see if we remember the names of friends from 15-20 years ago. It's also fun to see how mobile phones and photo cameras have improved over the years. It's also nice not to be trapped by iCloud or Google Photos anymore.

    Have a Test Instance or a Test Account

    I recommend having a test instance of Immich or at the very least a test account. If something goes wrong it's better to see it go wrong on a test instance rather than in production. I'd rather make sure all photos load into the right year, before seeing thousands of photos added to the day the Google Takeout archive was created.

    Things to Watch Out For

    • Duplicates: If you edited the rotation, adjusted histograms or anything else you might have three or four copies of the same image showing up.

    • Creation Date: With some photos I found that they are sorted by the creation date for the zip, rather than their original creation date. In these cases it's worth checking to see if they are duplicates or if you need to correct the date and time information.

    • Keep the Zips: If you make a mistake you can start over

    • Keep the file and folder structure: The JSON files are optimised for Google Takeout Folder structures.

    • Test Small and then scale up

    And Finally

    When I hit the 200 GB limit many years ago I upgraded to the 2TB plan and I was happy with it, but I didn't use all of that space so I was paying for more than I needed. As many people have said before me, if iCloud, Google One and other solutions had more tiers then we could upgrade one small step at a time, rather than catapulting from 200 GB to Terabytes.

    Another point is that with larger file export sizes breaking out of Google Photos is almost easy, in contrast to before. When you had too download hundreds of zip files, unzip them, and then re-consolidate everything you were speaking of a huge investment in time. Now, within a day or two, you can be out of Google Photos and into Immich.

    One of my key reservations about using cloud synching tools as a backup solution is that it was very hard to get data out, whereas now it is considerably easier.

    Upon completion of this process, if I tidy up my e-mails I could revert to Google's free tier.

    #exiftools #googlePhotos #googleTakeout #immich
  15. Butttttt…..

    Google Takeout seems to not handle it. There are countless examples where filename001.jpg has many instances in Google Photos, but Google Takeout only downloaded one (1) of them.

    How is this reality?!!?!!

    #GoogleTakeOut #GooglePhotos #DeGoogle

  16. Butttttt…..

    Google Takeout seems to not handle it. There are countless examples where filename001.jpg has many instances in Google Photos, but Google Takeout only downloaded one (1) of them.

    How is this reality?!!?!!

    #GoogleTakeOut #GooglePhotos #DeGoogle

  17. All of the files got uploaded and Google Photos could handle the file name collision no problem, the timestamps on the files were different even though the names were the same.

    #GoogleTakeOut #GooglePhotos #DeGoogle

  18. All of the files got uploaded and Google Photos could handle the file name collision no problem, the timestamps on the files were different even though the names were the same.

    #GoogleTakeOut #GooglePhotos #DeGoogle

  19. Ugggghhh, the problem is actually much worse. Apparently this is related to file names.

    I have tons of photos with the same file name because the files were created with a film negative scanner. There were no file name collisions originally because the scanner software would create a new folder for each scanning batch.

    #GoogleTakeOut #GooglePhotos #DeGoogle

  20. Ugggghhh, the problem is actually much worse. Apparently this is related to file names.

    I have tons of photos with the same file name because the files were created with a film negative scanner. There were no file name collisions originally because the scanner software would create a new folder for each scanning batch.

    #GoogleTakeOut #GooglePhotos #DeGoogle

  21. And for clarity, in the Google Photos web app, the okay resolutions can be seen. So they exist but are not included in the Takeout export. #GoogleTakeOut #GooglePhotos #DeGoogle

  22. And for clarity, in the Google Photos web app, the okay resolutions can be seen. So they exist but are not included in the Takeout export. #GoogleTakeOut #GooglePhotos #DeGoogle

  23. I have no idea the scale of the problem for my export but it could be thousands of images that I’m missing in my Takeout. #GoogleTakeOut #GooglePhotos #DeGoogle

  24. I have no idea the scale of the problem for my export but it could be thousands of images that I’m missing in my Takeout. #GoogleTakeOut #GooglePhotos #DeGoogle

  25. I just found out that #GoogleTakeOut has a serious bug when it comes to getting exports of #GooglePhotos libraries.

    If at any time in the past you enabled Space Saver your originals are gone forever.

    Fair enough, but….

    in _some_ cases Takeout won’t even download the good-but-not-great (5-16 megapixel from what I can tell) downscaled versions.

    Instead, it downloads 320x200 images, which are useless for anything other than hiding the reality of the situation.

    #DeGoogle

  26. I just found out that #GoogleTakeOut has a serious bug when it comes to getting exports of #GooglePhotos libraries.

    If at any time in the past you enabled Space Saver your originals are gone forever.

    Fair enough, but….

    in _some_ cases Takeout won’t even download the good-but-not-great (5-16 megapixel from what I can tell) downscaled versions.

    Instead, it downloads 320x200 images, which are useless for anything other than hiding the reality of the situation.

    #DeGoogle

  27. gibt es einen zu #googletakeout vergleichbaren Service für #onedrive? Oder bleibt es eher dabei, einmal eine Verlinkung aufzubauen, um dann "alles" runterzuladen, und zu hoffen dass man alles erwischt hat?

  28. den ersten Schwung an Daten mit #googletakeout lade ich gerade herunter. Bilder und Google Drive.

    Spannend wird es mit Googlemail. Ich benutze das auch gerne als Archiv - Jahre zurückliegende Bestellinfos verraten mir z.B. wann und wo ich ein Gerät gekauft habe, wie lange es bei uns in Benutzung war, solche Sachen.

    Wie kann ich den Maildump wieder irgendwo importieren und nutzbar machen?

    #DUT #DID

  29. den ersten Schwung an Daten mit #googletakeout lade ich gerade herunter. Bilder und Google Drive.

    Spannend wird es mit Googlemail. Ich benutze das auch gerne als Archiv - Jahre zurückliegende Bestellinfos verraten mir z.B. wann und wo ich ein Gerät gekauft habe, wie lange es bei uns in Benutzung war, solche Sachen.

    Wie kann ich den Maildump wieder irgendwo importieren und nutzbar machen?

    #DUT #DID

  30. The plan is to put all the Google Photos takeout in a local Ente instance running on the 45homelab HL4. The stack is running. I used Houston UI and Portainer-CE for most of the installation work.

    The trick was to edit the @ente quick start script to map the volumes and make other changes. I slipped in an exit after generation of .yaml files was complete.

    The health check of Postgres took some fiddling as Rocky 8 Podman was using the early syntax.

    #HomeLab #EntePhotos #GoogleTakeout #Cockpit

  31. The plan is to put all the Google Photos takeout in a local Ente instance running on the 45homelab HL4. The stack is running. I used Houston UI and Portainer-CE for most of the installation work.

    The trick was to edit the @ente quick start script to map the volumes and make other changes. I slipped in an exit after generation of .yaml files was complete.

    The health check of Postgres took some fiddling as Rocky 8 Podman was using the early syntax.

    #HomeLab #EntePhotos #GoogleTakeout #Cockpit

  32. I'm still fighting with my Google Takeout data. The last two days I tried to enrich the images with missing metadata inside the file with the metadata provided as supplemental JSON files by Google. I case you might find this helpful, check out: github.com/maxheadroom/GoogleT

    #GoogleTakeout #GooglePhotos

  33. I'm still fighting with my Google Takeout data. The last two days I tried to enrich the images with missing metadata inside the file with the metadata provided as supplemental JSON files by Google. I case you might find this helpful, check out: github.com/maxheadroom/GoogleT

    #GoogleTakeout #GooglePhotos

  34. Oh, seit wann gibt's das denn? Google Takeout (der Dienst, mit dem du deine Daten exportieren kannst) kann dir jetzt nicht nur nen Downloadlink per Mail schicken, sondern deinen Export auch direkt in Google Drive, Dropbox, OneDrive oder Box ablegen. Und sogar automatisiert alle zwei Monate nen neuen Export anstoßen. (Und .tgz statt .zip verwenden, und verschiedene Split-Größen für die erstellten Files: 1, 2, 4, 10 oder 50 GB.)

    #Google #GoogleTakeout #UnplugTrump

  35. Oh, seit wann gibt's das denn? Google Takeout (der Dienst, mit dem du deine Daten exportieren kannst) kann dir jetzt nicht nur nen Downloadlink per Mail schicken, sondern deinen Export auch direkt in Google Drive, Dropbox, OneDrive oder Box ablegen. Und sogar automatisiert alle zwei Monate nen neuen Export anstoßen. (Und .tgz statt .zip verwenden, und verschiedene Split-Größen für die erstellten Files: 1, 2, 4, 10 oder 50 GB.)

    #Google #GoogleTakeout #UnplugTrump

  36. So #GoogleTakeout läuft.

    Jemand eine gute Lösung um die MBOX Datei in eine Mailbox bei #hetzner zu Importieren?

  37. So #GoogleTakeout läuft.

    Jemand eine gute Lösung um die MBOX Datei in eine Mailbox bei #hetzner zu Importieren?

  38. If anyone is using the Google Takeout service to download and archive your Google data then the best way to download the actual .ZIP files seems to be to use the Google Drive Windows app 🤔

    Elect to have your Takeout .ZIP's delivered to your Google online storage (assuming you have enough free space).

    Install the Google Drive app and then use this to download the .ZIP files from the Windows Explorer view of the Drive (typically Drive G:).

    One you have them locally delete the Takeout .ZIP files from Google Drive and then uninstall the Google Drive app if you have no use for it 😊

    #Google #GoogleTakeOut #GoogleDrive

  39. If anyone is using the Google Takeout service to download and archive your Google data then the best way to download the actual .ZIP files seems to be to use the Google Drive Windows app 🤔

    Elect to have your Takeout .ZIP's delivered to your Google online storage (assuming you have enough free space).

    Install the Google Drive app and then use this to download the .ZIP files from the Windows Explorer view of the Drive (typically Drive G:).

    One you have them locally delete the Takeout .ZIP files from Google Drive and then uninstall the Google Drive app if you have no use for it 😊

    #Google #GoogleTakeOut #GoogleDrive

  40. Me he hecho un script rapido en python para pasar los mensajes de #Gmail bajados en formato #mbox con #googletakeout con fecha a partir del 1 de enero de 2023 a un nuevo fichero mbox para importar en @Tutanota el mbox completo de 15GB ya está #7z con contraseña en un @veracrypt si todo va bien compartiré el python en un gist (es mu tonto y muy a lo rápido eso si).

    #dataprivacy #ethicaldata

  41. Trying to export from #GooglePhotos is a nightmare. :eighthlayer_facepalm:

    Could go through #GoogleTakeout and download the 170GB worth of photos and video from there, but they don’t have embedded EXIF data, but a separate JSON file for each photo/video instead.

    Alternative is going through and manually selecting each to download which then includes the EXIF data.

    #Google #DeGoogle