←back to thread

572 points bookofjoe | 1 comments | | HN request time: 0s | source
Show context
pfooti ◴[] No.41864842[source]
I have a pretty old paperwhite. When it started deleting books i had side-loaded via calibre, I decided to get a kobo. I have a libra color, and I have to say: price notwithstanding, it's a great device. I don't have a lot of experience with more recent devices, but compared to my 2nd gen paperwhite, it is _amazing_.

Color is good enough to read comic books on it, the google drive integration means it's not too hard to get my CBR/CBZ files on directly. The annotation / notetaking featureas are nice (I haven't leaned into them yet, but they work well even on the small screen size), plus all the regular stuff with normal book reading. Also, since it's kobo/rakuten, the libby integration is better (search and select library books right from the device).

The actual reading app is maybe 90% as good as reading on the kindle (or a more specialized reader like perfectviewer on android). There's some annoyingly fiddly features- font size is kind of weirdly variable, when going through CBR files there's no "read next in the folder" gesture nor is there a "this is read/unread" state in the google drive ui, so you always have to remember which book you are finishing when opening the next in the series.

I tried out one of those boox readers with the android apps, which would be even better software-wise, but the boox hardware seems like garbage (for an N=1 at least). My display came with several rows of stuck pixels, and apparently it's a good thing that I ordered from amazon instead of the boox store, because the reviews indicate getting an RMA from boox directly is a pain.

replies(20): >>41865054 #>>41865144 #>>41865315 #>>41865560 #>>41865566 #>>41865600 #>>41865699 #>>41865782 #>>41866257 #>>41867222 #>>41867433 #>>41867629 #>>41867668 #>>41867732 #>>41868184 #>>41869695 #>>41870125 #>>41870297 #>>41870442 #>>41870449 #
koyote ◴[] No.41865054[source]
> When it started deleting books i had side-loaded via calibre

Could you expand on that? I load all my books via calibre but I also have the kindle set to aeroplane mode at all times. Does this happen when syncing?

replies(5): >>41865136 #>>41865143 #>>41866474 #>>41866681 #>>41867609 #
wooque ◴[] No.41865143[source]
It deletes all side-loaded books when you connect it to the internet, happened to me as well.
replies(9): >>41865197 #>>41865255 #>>41865379 #>>41865383 #>>41865482 #>>41866326 #>>41867042 #>>41867109 #>>41867339 #
jacurtis ◴[] No.41865383[source]
That is strange. I have had a Kindle for years (probably around a decade), upgrading mutliple times. I am using a Paperwhite Signature for the past year or so and I have not experienced this with any books. I have probably 70% Amazon purchased books, but that still leaves a decent amount of side-loaded books (mostly epub).

The only annoying thing I experience is that the cover art will unload on the side-loaded books where you just get the generic cover with the text of the book. But once you click the book it loads the artwork, which seems to last a few days before quickly going back to the generic cover. But the book itself never leaves the device. I can't say I have experienced this ever (except for once, mentioned below) and I have over 150 books on my 32Gb device.

Just some random thoughts I am wondering:

- Is it an ads-supported model (mine isn't)

- Are the books in a broken-DRM .mobi? Not judging, i've done it too, just curious if Amazon has some sort of "signature" in mobis that allow it to detect a book that had DRM removed?

- Are they standard .epub?

- What is the size of the device? (Maybe smaller 8Gb devices will clean up and prioritize non-Kindle content to make way for "official content)

- Which device is it? (Scribe, Oasis, Paperwhite, older paperwhite, etc)

The one time I had it deleting my book was a large book (it was 400Mb) and it was on an older 8Gb paperwhite. I still had PLENTY of storage space available (I was using around 4Gb) but it kept deleting that book. This was the only time I have seen it happen and it was with this one specific book. That was many years ago and I haven't seen it since. That book was a DRM-removed book I got through "shared" means. Which has led me to question if the Kindle removes it because it could detect that the DRM had been removed or because of its large size. But this was a one-off experience for me. The book was readable by the device. It would download for several weeks at a time before being removed. You could redownload it and it would work for weeks again before dissapearing. I never could figure it out.

replies(1): >>41866079 #
pfooti ◴[] No.41866079[source]
For me, they were drm free ebooks I bought legitimately and had to sideload via calibre because the kindle doesn't support epub. It's an old Paperwhite, and it only happens when I go out of airplane mode. However, I have to go out of airplane mode (or had to before I ditched the kindle for a kobo) to get library books and the occasional actual Amazon kindle book when I didn't feel like waiting for the library to get me to the front of the list.

*Edit to add: I believe the kindle won't delete epubs you sideload via the Amazon kindle email gateway, but I have no interest in doing that.

replies(1): >>41866932 #
ane ◴[] No.41866932[source]
I have been using Send to kindle[1] for years to upload epubs directly to Kindle. It even syncs the position in the books so that if I read it on my Kindle, it syncs the position to the Kindle app on my phone.

[1] https://www.amazon.com/sendtokindle

replies(1): >>41867324 #
k33l0r ◴[] No.41867324[source]
I've found that Send to Kindle does a much worse job at converting to MOBI than Calibre, which is a bit ironic but on par with Amazon's overall treatment of non-Kindle books.
replies(1): >>41872072 #
1. int_19h ◴[] No.41872072[source]
Back when MOBI was still the primary format for Kindles, it would actually allow you to upload .mobi files directly via Send to Kindle.

These days it wants ePub only, but things also seem to "just work", and I always assumed it's because they added support for it on device side. What are the issues that you ran into?