View Single Post
Old 10-08-2014, 04:04 AM   #73
Froide
Wizard
Froide ought to be getting tired of karma fortunes by now.Froide ought to be getting tired of karma fortunes by now.Froide ought to be getting tired of karma fortunes by now.Froide ought to be getting tired of karma fortunes by now.Froide ought to be getting tired of karma fortunes by now.Froide ought to be getting tired of karma fortunes by now.Froide ought to be getting tired of karma fortunes by now.Froide ought to be getting tired of karma fortunes by now.Froide ought to be getting tired of karma fortunes by now.Froide ought to be getting tired of karma fortunes by now.Froide ought to be getting tired of karma fortunes by now.
 
Froide's Avatar
 
Posts: 1,898
Karma: 9851695
Join Date: Mar 2012
Location: Noo Yawk
Device: Samsung Galaxy and Windows devices. RIP: Palm & Nook devices.
Quote:
Originally Posted by Lynx-lynx View Post
@froide thanks for posting that info.

I don't get it - why does adobe need to view the pages one selects to determine the DRM status. Unless of course every page has DRM embedded in it.

And it seems to me that Adobe is stealing my books and book information if it is accessing Calibre on my PC. Does it also read the now converted Amazon ebooks and send that info back to it's base as well?
Iain Thomson's article of 8 October 2014 - The Register: "Adobe spies on reading habits over unencrypted web because your 'privacy is important' (Is Adobe facing its Sony rootkit moment?)" - breaks it down, based on what Adobe published:

Quote:
Adobe explained that the data it collects is for digital rights management (DRM) mechanisms that may be demanded by publishers to combat piracy, and gave a detailed list of what and why it needs such specific information:
  • User ID: The user ID is collected to authenticate the user.
  • Device ID: The device ID is collected for digital right management (DRM) purposes since publishers typically restrict the number of devices an eBook or digital publication can be read on.
  • Certified app ID: The Certified App ID is collected as part of the DRM workflow to ensure that only certified apps can render a book, reducing DRM hacks and compromised DRM implementations.
  • Device IP: The device IP is collected to determine the broad geo-location, since publishers have different pricing models in place depending on the location of the reader purchasing a given eBook or digital publication.
  • Duration for which the book was read: This information is collected to facilitate limited or metered pricing models where publishers or distributors charge readers based on the duration a book is read. For example, a reader may borrow a book for a period of 30 days. While some publishers/distributers charge for 30-days from the date of the download, others follow a metered pricing model and charge for the actual time the book is read.
  • Percentage of the book read: This information is collected to allow publishers to implement subscription models where they can charge based on the percentage of the book read. For example, some publishers charge only a percentage of the full price if only a certain percentage of the book is read.

Additionally, the following data is provided by the publisher as part of the actual license and DRM for the ebook:
  • Date of purchase or download
  • Distributor ID and Adobe content server operator URL
  • Metadata of the book provided by publisher (including title, author, publisher list price, ISBN number)

Last edited by Froide; 10-08-2014 at 04:09 AM.
Froide is offline   Reply With Quote