View Single Post
Old 02-27-2020, 08:44 AM   #72
NullNix
Guru
NullNix ought to be getting tired of karma fortunes by now.NullNix ought to be getting tired of karma fortunes by now.NullNix ought to be getting tired of karma fortunes by now.NullNix ought to be getting tired of karma fortunes by now.NullNix ought to be getting tired of karma fortunes by now.NullNix ought to be getting tired of karma fortunes by now.NullNix ought to be getting tired of karma fortunes by now.NullNix ought to be getting tired of karma fortunes by now.NullNix ought to be getting tired of karma fortunes by now.NullNix ought to be getting tired of karma fortunes by now.NullNix ought to be getting tired of karma fortunes by now.
 
Posts: 929
Karma: 15576314
Join Date: Jan 2013
Location: Ely, Cambridgeshire, UK
Device: Kindle Oasis 3, Kindle Oasis 1
Quote:
Originally Posted by Sol Arkite View Post
It’s not just weird it’s sneaky. They also sneak in a forced firmware update that messes with potential jailbreaks. This isn’t for our benefit. It’s all about how to lock us into the way they want us to do things.
It's normal for all firms running large clouds these days -- it means you can trickle changes out, then easily roll them back if they break. Trickling firmware updates out allows you to do the latter, but unless the new features can be switched on *and off* independently of the upgrade, there's no easy way to revert broken changes fast without rapidly releasing a new bugfix firmware to everyone who received the broken one, which presumably Amazon can't really do due to bandwidth constraints. Flipping a feature on or off only takes a few hundred bytes.

They're just treating Kindles the same way as big fleets of remotely-administered servers, which seems sensible to me: Amazon do, after all, have a lot of experience with that sort of thing.
NullNix is offline   Reply With Quote