I have a rather large library from Takeout and it's been a burden.
It seems I'm going to need to write something to interpret their metadata to make it remotely useful again; they provide a flat archive with images and JSON files.
If I have to do this, I'd rather pick my tools on familiarity - compared to Takeout, I have slightly more with rclone
Truth be told I'm a data hoarder, I'll probably do both and reconcile
It seems I'm not the only one experiencing those encoding issues with Google Takeout https://webapps.stackexchange.com/questions/71153/takeout-br...
But yeah, Google takeout can be done once a month if you have time to spare for that task.
It seems to me like deleting the files over your storage limit is the easy path for both you and google and I don't see how this is an example of holding you hostage. At most bad communication and a lack of warning.
If there was a problem with insufficient warning, that's a problem, but not a hostage problem.
To be sure I backup my phone's photos using rsync (via termux) to my own backup locations.
I want very much for the rclone/Gmail integration to work well but it’s very complicated and fussy.
You are better off doing a takeout and downloading in your browser.