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
Sync watched status with Invidious #611
Comments
Invidious does not have APIs to manage watched videos. If this ever changes then this can be reconsidered. |
@arekf I also don't see this in their documentation: However, I do see a history API was added and merged about 11 months ago: So perhaps they just haven't updated their docs? |
@kris-anderson Thanks, was not aware of this API, I will reopen, however I don't think it is easy to implement because it still will require to maintain local database and sync it with Invidious APIs as otherwise it will not perform well. I think iCloud will come first, hopefully supported with merge of this PR: sindresorhus/Defaults#136 |
@kris-anderson This has not made its way into Yattee. Besides this, syncing the watched status with Invidious/Piped would be a nice feature. So I would let this issue open. |
Guidelines
Type
New feature
Describe the feature
For those of us with multiple devices, it would be great if Yattee would sync the watched status with Invidious.
I have an iPhone, iPad, MacBook, and multiple Apple TVs. Invidious does keep track of watched status, but Yattee keeps that status local instead of storing syncing that with Invidious which gets saved in a PostgreSQL database.
I would love to not only know what I've watched, but I could start a video on my phone, and then finish on the Apple TV.
There is a similar request to this, which is issue #291. That issue is asking for iCloud syncing of the watched status.
That would also solve what I'm looking for, but I agree with this comment that doing this via Invidious would be better:
#291 (comment)
That way it's in sync on all Yattee devices, but also via the web client (or any other front end client).
The text was updated successfully, but these errors were encountered: