This is a really unfortunate move by Amazon. My next e-reader will be one that I own (instead of just rent).
Glad that I took the time to jailbreak and pause updates on my 2017 kindle paperwhite while I could.
Their main advantage is providing access to all e-reading apps available on the Google Play Store, including Amazon's own Kindle app, as well as sideloaded ones such as KOReader.
On the downside, the battery life on those isn't as good as that of dedicated Kindles, Kobos, or other lightweight e-readers, but they still hold a charge for four or five days if one turns off their antennas, which is plenty of time to recharge them.
As for the ebooks themselves, I switched to purchasing from Kobo and other ebook stores. Some sell DRM-less ePubs, which is nice, while those that come with DRM can be easily liberated. And for the occasional Kindle-exclusive that is struck with (temporarily) unbreakable DRM, the Kindle app, although annoying, works well enough.
I do miss physical buttons a little, but that’s minor gripe.
I struggled with reviews when buying as I do love having a local library and the ease/difficulty of setting this up is never in device reviews.
Also hearing good things about XTEINK X4.
I really appreciate that the company that makes the device has embraced the community firmware scene and even links directly to them from their website as a semi-blessed alternative to their official one.
All of these discontinued devices support the AWZ4-format (which can be de-drmed and what im guessing this whole thing is about), but the newer ones use KFX which locks you perfectly into the Amazon and Kindle-ecosystem
I used that research to build something similar. It only works for manga and comics right now, but I have been tinkering with implementing glyph support as well to be able to handle full books.
https://github.com/Alexia/kandle-downloader
The original research is here, but the web site is down right now. https://blog.pixelmelt.dev/kindle-web-drm/
Any idea why your script does not seem to flag as a valid greasemonkey script when I try to use it in the Falkon (KDE) browser? Even if I attempt to add it manually, the script then disappears from my gm scripts.
Issues and PRs are available to open.(I just have not gotten any yet.)
> Any idea why your script does not seem to flag as a valid greasemonkey script when I try to use it in the Falkon (KDE) browser?
Honestly, no idea. I have only tested it with Tampermonkey on Firefox. Manually installing it should still work.
Well, I happen to use it everyday. I honestly don't know what exactly is "terrible/horrible/awful" about it. I'm neutral about its UX - neither memorable nor despicable. It may be missed if the new app's UX turns out to be worse on whatever metrics you're using.
I'll never own a kindle again. Does anyone know which platforms work with Calibre De-DRM? Or do we need to build a screen cap tool for transforming books to an open format?
I think the more plausible and likely explanations are:
1. Kindles take a beating when people actually use them instead of putting them in a drawer. Not many older kindles are still in circulation that are old + used. How good is a 14 year old lithium battery at best doing?
2. Added to the above, how is a 14 year old CPU doing when trying to support modern features and eBooks that now have metadata that did not exist at the time, such as fancier typesetting and color?
3. As for the Windows app, it's terrible. Horrible. Awful. Nobody liked it. Nobody uses it. It will not be missed.