Adobe Releases New Epub DRM - The Digital Reader
Rumors have been circulating since at least October 2013 that Adobe was planning to release javascript array a new version of their DRM for Epub ebooks, and it looks like the rumors have come true. Adobe has released a new version of Adobe Digital Editions yesterday, and guess what?
The features page says that along with improved CSS support javascript array and better support for vertical languages javascript array (Japanese, for example), Adobe DE 3.0 also includes a new DRM which is described as now being “hardened and made more secure”.
Yes, after over 2 years 4 years of quietly ignoring the fact that their DRM was hacked, Adobe finally took a step to repair the broken lock. And as part of their effort Adobe also updated javascript array Adobe Content Server 5 (there’s also a new RMSDK ), thus enabling ebookstores to provide ebooks that use the new DRM and allowing app and device developers to integrate the new DRM.
Yes, there’s a new type of DRM out there, and yes we will eventually see ebook readers and apps that support it. But for the near future the devices and apps that do not support the new DRM (and frankly, never will support the new DRM) will far out number the newer gadgetry javascript array that does. And that means that the vast body of existing ereaders and apps is going to drive the market. eBookstores will want to sell to the largest number of potential javascript array customers, so they will continue to offer the older DRM.
They already know that they’re losing customers to Amazon, Apple, and B&N, all of which have a proprietary DRM schema, so they’ll do their best to avoid losing what few customers they can get.
No, I think it much more likely that we will see almost javascript array no adoption of the new DRM. Instead I expect to see a repeat of the launch of the Nook store in 2009, when B&N announced their clever new DRM which no one else adopted.
Just javascript array about the only ones who will adopt the DRM will be the hackers who have probably already started working on cracking the DRM. I would put good money that the DRM will be hacked long before any reader encounters it.
Well, no. But I can definitely see ebookstores adding the new DRM *without* including a warning that the book is guaranteed not to work in your device or app and then refusing to refund you after you paid (or only issuing refunds in geological time).
Hopefully Adobe won’t try and do like they did when Content Server 3 was replaced by version 4. Unless you knew about the 9 month window (March ’09 – javascript array Dec ’09) to migrate books with CS3 encryption or have an old machine with an already activated copy of Acrobat javascript array or Acrobat Reader 6 or 7 you’re out of luck to access that content any more. http://web.archive.org/web/20100524173407/http://www.adobe.com/products/contentserver/migrate.html javascript array
Will they pull the same thing with CS4 to CS5? At first one would think not. There are many more books out there with CS4 encryption than there ever were with CS3 and the entire market is pretty different/larger than it was back then, but Adobe often takes an our way or nothing approach too, so who knows.
BN’s DRM is *not* proprietary. While they are the only major store that uses it, the schema has been made widely available upon NDA request (why many third party reading apps can read BN ebooks) and is completely compatible with ADEPT EPUB.
No, not really.
Proprietary has a very specific meaning. A proprietary DRM means that that company and only that company uses the schema *because the company refuses to allow anyone else use it*. BN is happy to make their DRM interoperable with other ADEPT systems.
Ah, proprietary. That word doesn’t mean what many people think it does. All it means is somebody owns it and controls it. MP3, proprietary. Ask the Fraunhofer institute. MPEG? The LA group. Fat32? Microsoft.
All DRM systems are proprietary. EReader DRM? B&N property. Licensed to Adobe who license it to others but B&N still owns it. They’d better; they paid decent cash to buy it. ADEPT? As this news makes clear, it is Adobe property. They charge for its use and decide what is and isn’t ADEPT. FAIRPLAY? Proprietary. MARLIN? Proprietary. CSS? Proprietary. Pretty much anything useful is somebody’s property. There is nothing derogatory in calling something proprietary. No need to be defensive about it.
Adobe’s timing is amusing, given this morning’s link to this: http://www.digitalbookworld.com/2014/ebook-buyers-are-loyal-to-specific-retailers-especially-kindle-ibooks-and-nook-new-data-show/
Generic ADEPT ebookstores javascript array command at most 10% of the US market but most of that is Kobo, who have their own proprietary DRM. Adobe’s true clients command well under 5% of ebook sales (and a good chunk of it is DRM free) so it is pretty much irrelevant whether they adopt the new DRM or not.
The interesting javascript array question is *wh
Rumors have been circulating since at least October 2013 that Adobe was planning to release javascript array a new version of their DRM for Epub ebooks, and it looks like the rumors have come true. Adobe has released a new version of Adobe Digital Editions yesterday, and guess what?
The features page says that along with improved CSS support javascript array and better support for vertical languages javascript array (Japanese, for example), Adobe DE 3.0 also includes a new DRM which is described as now being “hardened and made more secure”.
Yes, after over 2 years 4 years of quietly ignoring the fact that their DRM was hacked, Adobe finally took a step to repair the broken lock. And as part of their effort Adobe also updated javascript array Adobe Content Server 5 (there’s also a new RMSDK ), thus enabling ebookstores to provide ebooks that use the new DRM and allowing app and device developers to integrate the new DRM.
Yes, there’s a new type of DRM out there, and yes we will eventually see ebook readers and apps that support it. But for the near future the devices and apps that do not support the new DRM (and frankly, never will support the new DRM) will far out number the newer gadgetry javascript array that does. And that means that the vast body of existing ereaders and apps is going to drive the market. eBookstores will want to sell to the largest number of potential javascript array customers, so they will continue to offer the older DRM.
They already know that they’re losing customers to Amazon, Apple, and B&N, all of which have a proprietary DRM schema, so they’ll do their best to avoid losing what few customers they can get.
No, I think it much more likely that we will see almost javascript array no adoption of the new DRM. Instead I expect to see a repeat of the launch of the Nook store in 2009, when B&N announced their clever new DRM which no one else adopted.
Just javascript array about the only ones who will adopt the DRM will be the hackers who have probably already started working on cracking the DRM. I would put good money that the DRM will be hacked long before any reader encounters it.
Well, no. But I can definitely see ebookstores adding the new DRM *without* including a warning that the book is guaranteed not to work in your device or app and then refusing to refund you after you paid (or only issuing refunds in geological time).
Hopefully Adobe won’t try and do like they did when Content Server 3 was replaced by version 4. Unless you knew about the 9 month window (March ’09 – javascript array Dec ’09) to migrate books with CS3 encryption or have an old machine with an already activated copy of Acrobat javascript array or Acrobat Reader 6 or 7 you’re out of luck to access that content any more. http://web.archive.org/web/20100524173407/http://www.adobe.com/products/contentserver/migrate.html javascript array
Will they pull the same thing with CS4 to CS5? At first one would think not. There are many more books out there with CS4 encryption than there ever were with CS3 and the entire market is pretty different/larger than it was back then, but Adobe often takes an our way or nothing approach too, so who knows.
BN’s DRM is *not* proprietary. While they are the only major store that uses it, the schema has been made widely available upon NDA request (why many third party reading apps can read BN ebooks) and is completely compatible with ADEPT EPUB.
No, not really.
Proprietary has a very specific meaning. A proprietary DRM means that that company and only that company uses the schema *because the company refuses to allow anyone else use it*. BN is happy to make their DRM interoperable with other ADEPT systems.
Ah, proprietary. That word doesn’t mean what many people think it does. All it means is somebody owns it and controls it. MP3, proprietary. Ask the Fraunhofer institute. MPEG? The LA group. Fat32? Microsoft.
All DRM systems are proprietary. EReader DRM? B&N property. Licensed to Adobe who license it to others but B&N still owns it. They’d better; they paid decent cash to buy it. ADEPT? As this news makes clear, it is Adobe property. They charge for its use and decide what is and isn’t ADEPT. FAIRPLAY? Proprietary. MARLIN? Proprietary. CSS? Proprietary. Pretty much anything useful is somebody’s property. There is nothing derogatory in calling something proprietary. No need to be defensive about it.
Adobe’s timing is amusing, given this morning’s link to this: http://www.digitalbookworld.com/2014/ebook-buyers-are-loyal-to-specific-retailers-especially-kindle-ibooks-and-nook-new-data-show/
Generic ADEPT ebookstores javascript array command at most 10% of the US market but most of that is Kobo, who have their own proprietary DRM. Adobe’s true clients command well under 5% of ebook sales (and a good chunk of it is DRM free) so it is pretty much irrelevant whether they adopt the new DRM or not.
The interesting javascript array question is *wh
No comments:
Post a Comment