Quote:
Originally Posted by j.p.s
Kindles keep a database of all books "from" amazon with information for whether each book is "downloaded" or "in the cloud/library". Amazon servers have "content and devices" database(s) with similar information.
My guess is that synchronization of these databases is part of the book sync process. If you delete a book from a kindle via the "My Content and Devices" web page, the row for that book on the server database gets modified. If a kindle has the wrong time the order of operations gets muddled and the kindle mistakenly thinks a book has been deleted via "My C&D".
When all this got designed, written, and debugged, they probably never considered that EBOK would ever get set by anyone but amazon and also assumed that time would always be kept "close enough" by wireless or didn't even consider that bad time might cause a problem.
The above is not meant to be correct in detail or even in general outline, but to convey how things can go wrong with software or any process.
|
I could understand this if the time was wrong by, well, weeks or months. But others have experimented and found that deleting happens even when the time is wrong by a few minutes. Wouldn't that be "close enough"? I don't know, all this seems just weirder and weirder, and it's been going on for more than 2 years by now, as indicated by the posts in this thread. I'm not sure we'll ever see Amazon fixing it.
Is it even certain that not using the EBOK tag prevents the book from being deleted?