View Single Post
Old 02-03-2024, 09:18 AM   #173
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,764
Karma: 206758686
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by Quoth View Post
I'm sure this issue is incompetence rather than malicious intent by Amazon. The local clock getting too far out and then sync going a bit crazy is a good theory by @jhowell.
Yes. The internet is rife with tech support recommending the frequent synchronization of a device's time with a time server to work around bugs in programs/games that communicate via network. It's not at all a stretch to think that a time drift of a several seconds could cause seemingly unrelated issues whenever connectivity is restored to a complex system.

All it would take is one developer (or a few) thinking that someone leaving WiFi off long enough for local time to drift to the point of becoming problematic is an extremely unlikely event. One not worth the time of protecting against with more code. And in the grand scheme of Kindle usership, they're probably right.

Last edited by DiapDealer; 02-03-2024 at 09:28 AM.
DiapDealer is online now   Reply With Quote