View Single Post
Old 01-30-2019, 12:36 AM   #9
stumped
Wizard
stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.
 
Posts: 3,305
Karma: 10259306
Join Date: May 2016
Device: kobo forma, Kobo Libra, Huawei media Tab, fire HD10, PW3 HDX8.9,
Quote:
Originally Posted by kovidgoyal View Post
You appear to be extremely naive when it comes to how networks operate. You want a non-magical explanation, here is the most obvious one:

There exists a caching proxy between the software on your device and the content server.
that would be a time travelling, space warping proxy on the device then, *capable of operating when device is off, and capable of retrieving files from some multi-verse.?
I prefer my explanaion, but if no one cares enough to test it., it can stay as a bug. I can work around it and will not ask you to waste your valuable time investigating....
* a book (version A) that no longer existed as a file in the library was delivered to a device that had been previously OFF, OFF since before the book was placed in the library, and had remained off while the book was edited from version A to version B
stumped is offline   Reply With Quote