Post by @fonix232

In reply to 8 earlier posts

@fonix232@fedia.io on fedia.io Open parent

It's a pity Calibre to date refuses to be refactored into a self-hosted service. The core logic should be portable, with the app just being an interface to it, but no, the entire project is so much spaghetti it would feed the entire boot for over a year... such a shame.

Open parent Original URL

@Fmstrat@lemmy.world on lemmy.world Open parent

I switched. Kavita is the new hotness.

I found it for comics, but realized it handled books as well as Caliber does, in a modern interface with OPDS support.

Open parent Original URL

@fonix232@fedia.io on fedia.io Open parent

I tried Kavita and immediately recoiled at the fact that basic features like progress sync or metadata matching are behind a paywall - literally features that don't cost the developers anything, while having open, active bug reports going back a year on these "premium" features. All while licensing the code under GPLv3...

Open parent Original URL

@Fmstrat@lemmy.world on lemmy.world Open parent

Progress sync works fine for me in KOReader with OPDS. Progress Sync Scrobble (to third-parties) is the Kavita+ feature. My understanding was the Kavita+ items are things to do with third-party services and meta data providers that are an API/cost-based service to the dev. That being said I don't use any of those features.

Open parent Original URL

@fonix232@fedia.io on fedia.io Open parent

OPDS doesn't do progress sync, at all... you're running something else there if that works for you.

Open parent Original URL

@Fmstrat@lemmy.world on lemmy.world Open parent

https://anansi-project.github.io/docs/opds-pse/specs/v1.2 They use the PS extension. I believe Komga and Kavita maintain the spec now. Reader support for Kavita specifically is in the Wiki.

Open parent Original URL

@fonix232@fedia.io on fedia.io Open parent

PSE is page streaming, not progress sync...

Open parent Original URL

@Fmstrat@lemmy.world on lemmy.world Open parent

PSE is a protocol, how information is used on each side of that protocol is at the developers discretion.

pse:lastRead="10"
pse:lastReadDate="2010-01-10T10:01:11Z"

Open parent Original URL

fonix232 in !community

@fonix232@fedia.io · 7d

which is fucking useless for actual progress sync of books because it doesn't handle concurrency (multiple readers reading the same content, potentially offline), and more importantly, modern ebook formats have no concept of "page" in transit. Oh, you read page 10? Awesome! Now do tell, is it page 10 on a 5" 800x480 eink display with 48px font size and giant margins/lineheights/word paddings, or is it page 10 on a 13" display of 2480x1860 resolution with 11px font size and barely any margins? Since you'll get wildly different results in both cases, and OPDS doesn't really allow for adapting this simple integer to a precise position. No, for that you require a proper locator scheme, something OPDS doesn't provide and cannot enforce. Page based progress is fine for fixed format publications - comics, PDF/DOCX files, etc., but that approach breaks irreparably the moment you switch to dynamically formatted content. In case of EPUV/MOBI/the various Kindle formats, you want to determine the reader's position based on the first and last paragraph/sentence visible on the reader and correlate that to a position within the actual files of the book, which is actually dynamic, as it can be resolved regardless if it's XML formatted EPUB or if you dumbed the book down to a simple TXT file. So no, OPDS's PSE is at best a stopgap solution for syncing progress.

Comments (2)