-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
feature request: audiobookshelf and kavita integration #5
Comments
Hi, I'm not against integrations, but how would you see this ? My point of view is that Jelu is a passive app : your activity happens in other apps (like reading a book in kavita or listening to an audiobook in audiobookshelf), so the best place to trigger read events would be in kavita or audiobookshelf. For example you finish to read a book in kavita and that triggers a call to Jelu REST API to mark this book as read. So I see several ways to do it :
Well you see that is not easy on our side Maybe there is a plugin mechanism or a list of API to be used as sources in those apps ? |
Hi, |
Hi it seems both projects have already planned scrobbling : Kavita in the projects section, planned for v 0.6.1 : https://github.com/Kareadita/Kavita/projects Audiobookshelf : advplyr/audiobookshelf#281 Maybe it could be worth reaching them. |
I will ping both projects |
kinda curious if you decided to switch your personal setup to audiobookshelf and therefore may be making audiobookshelf and jelu interact? |
Hi, I'm testing audiobookshelf for podcasts only as I'm not listening to audiobooks. Sorry, I know you want this, but no interaction at the moment I'm afraid. Maybe you could benefit the APIs of Jelu and audiobookshelf and write some kind of sync script ? |
It would be awesome if this could talk to kavita (https://www.kavitareader.com/) and audiobookshelf (https://www.audiobookshelf.org/) to add their libraries (ideally with recognizing duplicates across them) and to keep track of what is read and not read in each to add to read/not read in this app.
The text was updated successfully, but these errors were encountered: