Quote:
Originally Posted by bopuc
The continue riffing on the above…
Here's the consolidation I would like to see:
1. a Calibre plugin that implements Calibre-Web's "kobo.com API masquerade" approach and adds those routes to Calibre's Content Server. (This way we don't need to set up and run a whole other service, etc etc)
This plugin would also create an endpoint to receive annotation data and properly add it to Caliber's annotations system.
2. "UNCaGED" can then focus on configuring the relevant options it already does (and not have to worry about all the syncing etc because Kobo now does it).
3. "UNCaGED" also integrates "KoBuddy" to access annotations etc on the Kobo device and send them to the above described Caliber plugin's API.
This would give us the foundation for a proper, contemporary "mobile service" user experience for Kobo ereaders (which don't use the Kobo store etc).
Bonus: a one-time migration script to push existing annotations from DavidFor's (much beloved but I am getting worried!) "Annotations" plugin into Caliber's Annotations.
|
This is absolutely brilliant implementation and exactly what I'd be looking for from a usability perspective. Thanks for laying it out so clearly!
In brief, Kobo API syncs books to the device 'natively', and KoboUNCaGED handles KoboTouchExtended (KTE) and Calibre metadata, covers, and annotations with these books (which is the present gap). The backend would also be some kind of auto-conversion with KTE, and preserving the metadata settings there would be brilliant.