What's Supposed to be Different about Livtet?
I started working on Livtet out of the annoyance of using Calibre. Sure, it's a venerable tool for managing one's local eBook collection but it also does so much more. The presence of such "more" has confused me to a point where I, like the tinkerer I am, would install so many plug-ins and have overwhelmed my small installation. Now, having done my operating system reinstall, I find myself questioning if I want that application in particular. It's hard! The things of value I find from Calibre are:
- KOReader sync server: I use KOReader as the "reading interface" on my eReader. It handles the work of managing all of my reading positions, bookmarks, highlights and includes dictionary and Wikipedia lookups. The only thing this can't do is check out books from places like Hoopla or Overdrive but that's a limitation of the client itself: Calibre can do that.
- Cataloguing: The fact that I can add a DRM-free book, immediately get more information from corpora around the Web, associate it to the social reading software I'm using and keep that in sync as I read is a boon.
Though the list is short, these features feel indispensable to me — despite not even having Calibre installed on my machine at the moment. The initial blog post I wrote about Livtet was effectively a GUI over the Calibre API; something that's no longer useful for me.
A Local Library
What I personally want is a tool that satisfies the feature list above. This is what prevents me from doing those little excerpt posts I used to do on my Fediverse account. I'm not going to sit and retype what I've easily highlight when it's captured with precision already! Implementing the API needed to become a KOReader sync server isn't terribly difficult — in fact, I could inject the code into Livtet itself as a sidecar application. But before I get to that point, the act of managing one's library needs to be made more simpler, at least for this tool.
Discussion in the ATmosphere