Is this project still alive? How to authenticate, and where is this documented?

[pmorch]

I can see that the last commit to this project was 4 years ago, which makes me suspicious.

There is also #37 from May 2023 which I ran into when I tried. I saw the exact same "Couldn't sign you in" screen. That bug is still open, contains some suggestions that where unclear and they apparently didn't work for everyone.

So is the expectation that this project still works in 2024, and exactly how should one invoke it?

If so, please document how to get it running in light of #37.

If not, please update the README to indicate this is abandoned, e.g. by simply adding this at the top of the README.

**WARNING**: This project is abandoned and is known to no longer work. See #37.

That is fair. It saves us mortals from spending useless time trying to get it to work.

I did this on Debian:

$ apt install golang
$ go run main.go

It would be nice if this was documented (once it works), and if that is not it, then document exactly what should work for first-time users.

[JakeWharton]

I can see that the last commit to this project was 4 years ago, which makes me suspicious.

Software can be finished! I've had this running on two accounts for four years with very little incident.

[pmorch]

Ok. So it works for some people. That is good to know. But you probably also authenticated a long time ago. I wonder if you would run into #37 also if you had to start this from scratch yourself.

Regardless, thanks for your reply.

[mpl]

@JakeWharton Hey. I seem to recall someone was maintaining a docker image for that project, which seemed to be the one that most people were using. Was/is that you?

[mpl]

@pmorch it's true that I haven't had much time to dedicate to this repo in a while, and I'm not sure how much time I'll have in the future.
But as @JakeWharton said, I wouldn't call the project abandoned either.
Anyway, I'm all for bringing more clarity on the matter later on though.
I'll be afk for two weeks now, but I'll try to think about it some more afterwards.

[JakeWharton]

@JakeWharton Hey. I seem to recall someone was maintaining a docker image for that project, which seemed to be the one that most people were using. Was/is that you?

Yep, that's me!

https://github.com/JakeWharton/docker-gphotos-sync/

Admittedly I'm running a four-year-old version of it, but it at least keeps on chugging along.

[presto8]

This is a very valuable project to increase one's data sovereignty. I agree with the sentiment that it does not "work out of the box," and it would be good to update it. This is due to changes on Google's side I believe to increase the security.

What worked for me was to create a dedicated profile first (normal mode, without automation) and log in. Then the automation works. But trying to login with the automation enabled seems to not work.

I don't know if there is a way to automate that or just provide instructions that the profile used has to already be logged in, and then provide the profile path as a command line arg.

I have been looking to get more experience with Go, I could provide a PR if it would be helpful.