|
I agree that with the current system people could download and upgrade with the wrong software. But, that doesn't mean it couldn't be improved.
Why do they stagger OTA firmware upgrades? Likely to avoid killing everyone's reader if there is a problem in rolling it out. Why not roll it out to their BETA TESTERS which should be a representative pool of hardware first and give it 24-48 hours just to make sure all the betas are good with it? It seems to me they are too dumb or too arrogant to use the beta testers as they should. I'm not saying that is the case, but for lack of evidence to the contrary and taking into account the way other things are handled one might suppose.
As for the other end of it, there is no reason a section of code(a patch) couldn't be written and distributed for those in areas requiring certain versions, or with particular model readers, that forces the current version to look for a particular identifier or certain text in a file, etc., before it updates from .kobo directory. That stuff has been done over and over along with checksums for umpty ump years. We did something similar with an eprom burning software to make it largely bulletproof back in the 1980's for heaven's sake. It was overkill as we had the technical backgrounds to deal without it, but it wasn't a terrible idea, just overkill considering the user pool.
|