Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix Netflix sync time #44

Closed
rafaelgomesxyz opened this issue Oct 27, 2020 · 3 comments · Fixed by #85
Closed

Fix Netflix sync time #44

rafaelgomesxyz opened this issue Oct 27, 2020 · 3 comments · Fixed by #85
Labels
bug Something isn't working

Comments

@rafaelgomesxyz
Copy link
Member

The Netflix watched date is always when the user began watching, not when they finished. We should change that by adding the length of the episode/movie to the watch date, so it's more accurate.

@rafaelgomesxyz rafaelgomesxyz added the bug Something isn't working label Oct 27, 2020
@MrMamen
Copy link
Member

MrMamen commented Nov 3, 2020

Possible as an user option?

@rafaelgomesxyz
Copy link
Member Author

Well, I can't see why anyone would want it to behave like it does currently, since the watch time is always wrong. But sure, we can add it as an option, enabled by default.

@MrMamen
Copy link
Member

MrMamen commented Nov 4, 2020

I think this is a case with pretty much all streaming services. It records the last time the play-button was clicked, or similar. The problem is of course if you watch a part of the title at one point, and resumes at another time. Not sure if it's worth making a lot of UI for, but at least it is a concern.
Also there are a few similar off situations.
If you use trakt "add on release date"-feature, it would record the start time. Scrobling and checkins would record the end time. I guess it is a matter of definition, and not sure if it is important. I don't have any strong opinions of this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants