Will gphotos-cdp continue to work after Googles API change announcement?

[tschweitzer]

Google announced changes to their Photos API limiting access for third parties as a privacy/security mechanism. Projects like gphotos-sync therefore won't be working anymore, see gilesknap/gphotos-sync-discussion#1.

Does this change also affect gphotos-cdp or how high do you see the risk of gphotos-cdp stopping to work in the future?

[mpl]

I don't have the authentication flow off the top of my head anymore, but looking at the discussion on gphotos-sync , I would assume that yes, gphotos-cdp is going to have the same problem.

[spraot]

gphotos-cdp doesn't use any APIs, so that change won't break it. If you are interesting in using it, consider this fork instead though, it has a number of improvements, including:

• Use newer chromedp version
• Make finding end of library more robust
• If downloaded file is a zip, unzip it
• Add -date option that takes the date from the gphotos UI and sets it as file modified time (many of my files have no date metadata)
• Skip existing files (allowing redoing sync without redownloading, necessary if adding older photos to gphotos)
• Fix race condition that caused my syncs to stop every 40 files or so
• Add -json option for outputting logs in json format

There's a nice setup with cron running in a docker container and auth helpers here: https://github.com/spraot/gphotos-sync