[FEATURE] Kobo Sync Integration

[arunoruto]

Is your feature request related to a problem? Please describe.
Currently, OPDS is the only way to distribute content to readers, and I am unaware that any commercial reader supports it. On the other hand, caliber-web implemented a way to send files via email to Kindle devices and even hosted the Kobo API to trick a device into syncing with the library like it was Kobo's servers.

EDIT: An interesting library to look at, would be kobink. It could be integrated directly into the code, as a module, or put in a separate docker container to handle the syncing of ebooks with a Kobo device.

Describe the solution you'd like
Make a similar feature set available for stump! While I do like Clibre-web, I do not like how Calibre manages the data in the background and how the user cannot rename things as he wants (database issues and so on). That is why I am using Stump now, but QoL features like this are currently missing.

Additional context
I am aware, that other features and bugs are higher on the priority list, but it would be cool to discuss possible solutions to this Problem! I was maybe thinking of taking the implementation of calibre-web, which consists of the kobo.py, kobo_auth.py, and kobo_sync_status, and implementing a library of its own, so it can be imported into other projects like stump. I will see how much I can do on my own, but getting help from someone experienced would be great!

[aaronleopold]

Hey 👋

This might be a potential duplicate of #239. If so, it might be good to move any further discussion there so everything is in one spot.

caliber-web implemented a way to send files via email to Kindle devices

There are (very new and experimental) email to device features already in Stump, I believe they are available in the nightly and experimental tags but will be in the next versioned release.

I was maybe thinking of taking the implementation of calibre-web...so it can be imported into other projects like stump.

I'm all for a solution which would work for multiple media servers / other projects! You might be able to write an isolated library like Aidoku which has bindings to be consumed by (an)other language(s), but I'm not sure how feasible it might be since I assume DB interactions would be involved and each server handles things differently enough.

I will see how much I can do on my own, but getting help from someone experienced would be great!

I'm happy to use the other ticket as a brainstorming session to help get something out there! There is also the Discord, if you prefer.

[aaronleopold]

I'm going to close this as a duplicate of #239. Please feel free to comment there if you have anything else you'd like to discuss wrt this feature 🙂

[arunoruto]

Hey @aaronleopold
As you mentioned in issue #239, the Kobo API integration should be tracked separately.
Maybe this issue can be reopened again to track that?

[aaronleopold]

Yep, definitely re-open. I think at the time I assumed the two were the same and so closed this as the duplicate.

I am renaming to focus on the Kobo side of things, send to kindle should actually already be available via email

[Dyad-ITSS]

plus one for this feature, either the email to Kobo feature or sync feature as it's implemented in Calibre Web - super easy to use for my users.

[aaronleopold]

either the email to Kobo feature

Is email to Kobo something special or unique? I assume the existing email-to-device functionality in Stump would satisfy that bit? I really need to get a Kobo 😅