|
The thing I don't care for in the built-in reader is that it stores the books in kind of a hidden place.
Most people are aware that their browser has a cache and stored cookies. But these days browsers also store a whole lot more "site data". Looking at my Chromium browser, I see these things stored: cookies, cache, Application cache, Cache Storage, Database storage, Local storage, File System, Channel ID, and Flash data. Many people have no idea about all this stuff that gets stored on a websites behalf (including calibre-server's internal reader's books). They don't know where it's located, how to get rid of it to free up disk space, what it's used for, etc.
Not that I use the internal reader, but if I did, I would prefer that it stored the books per the web browsers default download settings - usually either in the Download folder or "ask the user where to store it each time". Then the internal reader could save the path to the book for offline reading later. The user could accidentally (or intentionally) delete the book from wherever they downloaded it to, and thus break the internal readers linkage, but I think that would be preferable to the internal reader storing the book in this "hidden" site data area of the web browser.
The obvious answer is "don't click the button to read the book offline later". But if you don't know what that button does, and I didn't the first time I clicked it as a test, then you could end up with these hidden downloaded books following you around for the rest of your life because you don't know where they are or how to get rid of them. Maybe the internal reader has some kind of built-in cleanup to delete this stored data. That would be a nice feature.
|