I dont understand how works

[segator]

You have a rest api service connected to redis (keep account and watched information)

then user A connect to server A and watch a movie

next day user A connect to server B and he can see the movie seen yesterday marked as watched, he now watch an other movie on Server B.

I expect (after sync) the movie watched on server B is marked on server A.

That's correct? that's mean the sync is bidirectional?

[fiLLLip]

You guessed it right, yes :)

I'm not actually sure that the rest api is online anymore. I don't monitor it and have not checked if it is online in a long time.

[segator]

the system sync also friends watch status? or only owner server info?

[fiLLLip]

the system sync also friends watch status? or only owner server info?

It syncs the watch status for all users who has logged via the frontend and approved it, just as a extra security feature. It's just so that you can not fake being a random server and accessing users watch habits 😄 But of course, if you are running this locally you don't need that extra feature. For the hosted version I felt it was needed to not allow random people to access your watch history.

[segator]

SO is necesary all my users log first to your frontend then it will sync bidirectioanl between servers.

It also sync movies stopped in a half of reproduction?

[segator]

could you define a simple example how to bring all the system up?

[fiLLLip]

It only syncs watched/not-watched status.

In the readme it provides a rough setup how to get it up and running. It is a long time since I ran this feature myself, so things might have changed in Plex since last time. I can not guarantee it works. Some developer experience might be needed to get it up and running.