Quote:
Originally Posted by Elfwreck
B&N has a *sharp* separation between books bought through it, and sideloaded content. They definitely don't track or sync the sideloaded content.
|
See
MovieBird's comment on the first page of this thread. He claims that B&N is giving him recommmended readings based off his side-loaded content. And I have to agree with him that if B&N is doing, then the much sharper Amazon who pioneered some of these recommendation engines is probably doing it too.
I think we might be getting our wires crossed in a few different areas:
1) I'm really talking about books that you have purchased in another store that came with DRM. Stripping the DRM and converting it to another format will preserve the metadata. You would have to actively make an effort to corrupt the metadata in order to remove the unique identifiers.
2) I don't believe that Amazon is uploading the entire side-loaded book to the cloud. This is what I think happens as it makes the most sense from a design standpoint. The device has a database on it that I will called device_db. What format (sqlite, xml, etc) device_db is in is irrelevant. All books purchased from the store online, emailed to the device, or side-loaded have their meta-data read and stored in device_db. device_db is always synced to the cloud_db whenever you had a change (like a new file side-loaded) and connect via Wifi.
device_db is probably the same database the library\reader on the device uses to display your selections.
3) Amazon isn't the biggest problem here in terms of targeting the customer for DRM violations. It's the fact that someone could sue them to acquire the data. A publisher would be in a position to cross reference de-DRMed copies vs their official list of who received them.
* Edit - add part in italics