5

Amazon KindleAs I’m lying in my hospital bed, recovering from the surgery on my leg, I came across a story on Amazon’s recent action in asking that Mobileread take down information relating to the Python scripts for putting other vendors’ books on the Kindle. I noticed David Rothman’s piece on it a couple of days ago, though given that it was the day of the surgery I was not exactly in the best condition to give it much attention at the time.

But now that a few more articles have come out, a few more days have passed, and I am thinking more clearly now that I am emerging from a haze of painkillers, I would like to set down my own thoughts about this decision, what it entails, and how I feel it fits in with my predictions of Amazon’s future behavior.

The script was fairly harmless in and of itself. All that it did was turn the serial number of the Kindle into a Mobipocket “Device ID” that could be used in e-book stores like Fictionwise or BooksOnBoard to buy Mobi books for the Kindle as if it were any other Mobipocket-compatible device.

In fact, the removal of the KindleID script mainly harms people who are trying to do the “right thing” by retaining the DRM on the DRM-locked books that they buy. Stripping the DRM would actually be simpler, and would allow their use on not only the Kindle but on any other device (such as an iPhone) that has compatible reading software.

(Of course, the Kindle’s device ID could be used to strip the DRM from downloaded Kindle books in the same way—but Amazon did not go after the de-DRMing script which would actually be used for that purpose, which has also been prominently mentioned on MobileRead.)

So, Amazon is saying that it does not want people reading books they buy elsewhere on the Kindle. Amazon wants to be the only Kindle bookstore. Of course, Amazon can’t control unencrypted books, such as Baen Webscriptions—but if they’re DRM-locked, the DMCA comes into play.

The odd thing is that since Amazon actually owns Mobipocket, who owns and licenses the Mobipocket encryption to these other stores, Amazon is saying that it does not want its right hand to know what its left hand is doing—or at least, it does not want its right hand to be able to read the books that its left hand wrote.

So, let’s review. Amazon has “embraced and extended” the Mobipocket format so that the Kindle is not compatible with other Mobi-DRM-selling stores without the aid of certain Python scripts. It has DMCA’d those Python scripts, indicating in no uncertain terms this was no accident.

Amazon has apparently prevented Mobipocket from releasing an official, Mobi-DRM-compatible client for the iPhone—while it has itself released a Kindle-DRM-compatible client for the iPhone.

Amazon owns both its Kindle-DRM, and (through its subsidiary) everybody else’s Mobi-DRM. Amazon has already shown it does not want Mobi-DRM being read on its Kindle hardwae platform. It has begun to expand beyond that hardware platform into other hardware platforms (the iPhone is only the first) that already have their own e-book apps.

I think that, as a format for DRM-protected e-publishing, Mobipocket’s day is basically done. Just as with iPhone, I do not expect to see Mobipocket apps released for Android, or the Palm Pre, or any of the other new platforms that people are asking about on the Mobipocket forums. I don’t expect to see much further maintenance of Mobipocket apps for existing platforms. I do expect to see (Mobi-incompatible) Amazon Kindle clients come out for all of them.

I expect Amazon will weasel out of renewing the Mobi DRM contracts with Overdrive and other such licensees just as soon as it reasonably can (if it can) without inciting anti-trust scrutiny. And given how widespread the Mobipocket format is in stores that use encryption, and given the print publishing industry’s widespread insistence on encryption, if this happens it could be a major blow to non-Amazon e-book stores.

In short, based on past behavior, I expect to see Amazon doing its best to leverage its massive library to try to become the go-to e-book store on every platform—and to shove out the stores that are already in those market spaces. After all, more people reading Kindle books are more people likely to buy hardware Kindle readers in the future to work with the library they’ve already bought.

 
5