logoalt Hacker News

gjsman-1000today at 4:39 PM4 repliesview on HN

What's also not mentioned is that the discontinued devices don't support KFX.

KFX is the modern kindle format, AZW meanwhile is heavily PDF-based. KFX was designed ground-up by Amazon, supports every modern feature they could think of, and presumably couldn't be backported to 2013 and earlier Kindles; AZW meanwhile was basically a wrapper around a subset of PDF. KFX is a complete redo, notable enough it's what "Enhanced Typesetting" on every Kindle product page means, not a small DRM upgrade.

By doing this, all authors will soon receive guarantees that they will have the full KFX feature set when designing eBooks, and won't break AZW by accident. Trying to point this out though to the "it's about DRM" or "it's about obsolescence" crowd will get you downvoted to oblivion before the truth is even considered (speaking from experience, -4 when I dared suggest legitimate reasons exist) and is a prime example of echo chambers and deeply ingrained bias on this forum.


Replies

WorldMakertoday at 5:01 PM

The original AZW format was MOBI-based, not PDF-based. MOBI originally from a company called MobiPocket, which Amazon eventually acquired, was built to be an ePub competitor and like ePub was an HTML and JS-based solution, but in a somewhat different, proprietary DRM-friendlier container format. (ePub is "just" a ZIP file, with the DRM applied sometimes inside the container rather than outside it.)

MOBI stopped keeping up with ePub standards and standard features, in part because Amazon acquired MobiPocket. The KFX is just ePub with a new proprietary DRM container around the ZIP file that is ePub's container.

The 2013 boundary is also the "supports ePUB files directly without a conversion process" boundary in Amazon's kindle OS. It's not just useful to know for book file authors, but as a consumer it becomes useful for a quick "Can I buy a standards compliant DRM-free EPUBs such as from sites like DriveThruFiction and just send them to my Kindle with no other steps?"

show 1 reply
fshtoday at 5:15 PM

AZW is clearly not PDF based. Try opening an actual PDF on a Kindle and compare the experience.

show 1 reply
Barrin92today at 4:50 PM

I don't follow the logic here. Users of old devices aren't asking for new features, they're merely asking for their devices not to be bricked. If an author wants to design against a new set of features they can do that, and that book will not be available on older hardware. Just like, if you want to build an Android app against a newer version you can do that without forcing every human being to replace their phone.

show 1 reply
turtlesdown11today at 6:39 PM

and another thing: im not mad. please dont put in the newspaper that i got mad.