Yes, I realize that.
I used it myself the day it was released - and also posted a huge(/long) stylesheet (on a different forum) that went through the conversion, after playing with it for four hours to see what worked and what didn't.
If you reread my post - it is carefully worded around the fact, that we now can produce (still not fully understand) - .kfx files as well.
It was a nice - FU (sorry, harsh
) - towards Amazons ambitions to keep a wrap on the "feature exclusive" thing.
But we still dont understand the format fully (its not completely reverse engineered - and since the maintainer currently is still working solely on a trial an error basis, it will be hard to get to that point).
Besides that - there still is the issue of the "new DRM" - that has to be discussed separately but until now hasnt - because the entire format was closed. And the issue that the format isn't fit for archival purposes (one way conversion only).
Then we can tackle the issue that until the converter doesn't come with calibre - distribution and actual usage will be minimal (Unless pirates pick it up - which would be interesting from an attunement perspective (get people used to the first "read, then throw away" format from Amazon - without having them spend money for the lock in -
(Ok, thats sarcasm..
)) - and because the plugin is based on closed source converters by Amazon - this currently simply isnt possible.
Also it took us (well, him..
- but structurally spoken) - more than a year to reach this point. Wile Amazon this time around launched the format the same day it was announced. When does kfxi launch, btw?
Amazon btw. never even publicly has spoken to what this new "paradigm" ("Only we (as in the company) should be able to create the most recent eBook format, and know how it works") means for them.
("How have they successfully sold this to publishers?" - being my Nr. 1 question..
)