Quote:
Originally Posted by jhowell
And since the registration problem now seems to be resolved we may never know if it was actually intentional or just a glitch.
|
The response I got from the Amazon "engineer" has convinced me it was more than just a glitch. They knew there was a problem, and their solution was "upgrade". Still doesn't mean the devices in question were intentionally abandoned, but there was definitely a brief period of time where Amazon chose to not give a damn about these fully-functional devices.
My being able to register, and have full functionality restored is proof that the capability of these devices is sufficient to utilize their infrastructure.
I agree, however, that it doesn't automatically mean these devices were being axed to further strengthen Amazon's lock-in via KFX. More than likely, it was test to see how important it was to continue maintaining infrastructure for these aging devices (or some idiot who's now out of a job made a bone-headed unilateral decision). I'd say it's time to worry, though, if support for KFX on K3's starts rolling out.
