View Single Post
Old 03-30-2019, 11:55 AM   #549
odamizu
just an egg
odamizu ought to be getting tired of karma fortunes by now.odamizu ought to be getting tired of karma fortunes by now.odamizu ought to be getting tired of karma fortunes by now.odamizu ought to be getting tired of karma fortunes by now.odamizu ought to be getting tired of karma fortunes by now.odamizu ought to be getting tired of karma fortunes by now.odamizu ought to be getting tired of karma fortunes by now.odamizu ought to be getting tired of karma fortunes by now.odamizu ought to be getting tired of karma fortunes by now.odamizu ought to be getting tired of karma fortunes by now.odamizu ought to be getting tired of karma fortunes by now.
 
odamizu's Avatar
 
Posts: 1,833
Karma: 8006102
Join Date: Mar 2015
Device: Kindle, iOS
Quote:
Originally Posted by lkmiller View Post
I notice that the last time the key file changed was when KF8 started taking over from MOBI.
It does seem clear that Amazon wants to replace KF8 with KFX, just as KF8 was the replacement for MOBI. However, Amazon hasn't abandoned MOBI (yet?), so I'm hoping the same will happen with KF8.

I'm curious: I understand that disabling renderer-test in K4PC 1.25.2 does nothing, and so far no one has figured out how to block KFX for K4PC. But what happens when you try to download/read an older book that's only available in MOBI or KF8? Can K4PC 1.25.2 handle it? Do you get a MOBI or KF8 file? And if so, will Alf work on it?

ETA: I enabled renderer-test on K4Mac 1.25.2 and ran the following tests:

1) Downloaded recent book and got KFX.

2) Downloaded really old book, got Topaz and Alf successfully liberated it.

3) Downloaded semi-old book, got MOBI and Alf successfully liberated it.

So it does seem the new .kinf2018 key file uses the same key as .kinf2011 for older formats and only KFX is affected — at least on Macs.

Last edited by odamizu; 03-30-2019 at 12:07 PM. Reason: more info
odamizu is offline