View Single Post
Old 08-30-2015, 05:56 AM   #167
murg
No Comment
murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.
 
Posts: 3,240
Karma: 23878043
Join Date: Jan 2012
Location: Australia
Device: Kobo: Not just an eReader, it's an adventure!
Quote:
Originally Posted by DNSB View Post
From what I can make out of your statement above, if I use a software product, any missing features in that software product are my fault. Any bugs are my responsibility. Am I, perchance, missing the mandatory <sarcasm> & </sarcasm> tags?

On a more serious note, what alternative renderer would you suggest that Kobo use that would have compatibility with Adobe's ADEPT DRM used by virtually every supplier of DRMed epub ebooks, not require a major rewrite to work on their variant of Linux and not have any bugs or missing features?
If you use a software product, and that product has some bug embedded in an external library, it is the producer of the product you bought's fault.

Kobo already has their own renderer (kepub). While it makes sense to continue to use Adobe's server side, decrypting Adobe DRM is relatively trivial, as witnessed by Apprentice Alf, et al.
murg is offline   Reply With Quote