Comment by vishnumohandas
5 years ago
FWIW, ente processes all of the location metadata generated by Takeout during an import via web.ente.io.
5 years ago
FWIW, ente processes all of the location metadata generated by Takeout during an import via web.ente.io.
That's probably the best once can do other than reverse engineering the protocol used by Google Photos Android app - as that app seems to be able to download files with full exif, unlike official API.
Unfortunately, as mentioned, multiple users report that Takeout does not work once you get past certain size (I have 350GB and it fails every time). It's been failing for years, probably always. Of course Google doesn't care.
I guess if someone was in EU they could try to ask Google for their data under GDPR data portability, face inevitable non-answer and then go to court if they are determined enough.
I sincerely hope that someone sues.
Google has blocked access to their APIs for migration[1] which IMO contradicts with their stance on data portability[2]. It is hard to assume good intent here.
[1]: https://developers.google.com/photos/library/guides/acceptab...
[2]: https://datatransferproject.dev
As the famous saying goes, never ascribe to malice that which can be explained by incompetence. This is Google we are talking about, they are infamous for their lack of strategic focus and disorganization.