View Single Post
Old 02-07-2016, 12:48 PM   #9
darryl
Wizard
darryl ought to be getting tired of karma fortunes by now.darryl ought to be getting tired of karma fortunes by now.darryl ought to be getting tired of karma fortunes by now.darryl ought to be getting tired of karma fortunes by now.darryl ought to be getting tired of karma fortunes by now.darryl ought to be getting tired of karma fortunes by now.darryl ought to be getting tired of karma fortunes by now.darryl ought to be getting tired of karma fortunes by now.darryl ought to be getting tired of karma fortunes by now.darryl ought to be getting tired of karma fortunes by now.darryl ought to be getting tired of karma fortunes by now.
 
darryl's Avatar
 
Posts: 3,108
Karma: 60231510
Join Date: Nov 2011
Location: Australia
Device: Kobo Aura H2O, Kindle Oasis, Huwei Ascend Mate 7
The boing boing thread is an interesting read. The problem arises with repairs involving the fingerprint sensor, which apparently include most or all repairs to the button. There is a vigorous defence of Apple apparently amongst those who are involved in security who say the response is proportional given the risk of the theft of fingerprints. Which can be argued. Where I think it fails is firstly that the "bricking" was not an immediate response to the suspected tampering with the fingerprint reader, but happened in many cases months later and was implemented by the update. Secondly, there was it seems no public warning that his could occur. In fact, it was sometime before Apple would admit to it. Also of interest is the reminder that Apple is a very large corporate entity, and its many hands often don't know what the others are doing. There is a suggestion that what happened was a result of these internal interactions and in fact came as s surprise to Apple. This to me is quite credible. Apple of course should as a group have known what would happen, but did not.

Apple now suggest that these devices simply cannot be unbricked. Again, being a security feature, to me this is also credible. For a consumer device marketed in the way it is as being easy to use and suitable for non-techies, it is also absolutely stupid. They should not have even considered such a feature without steps to educate their users about the risk. And how realistic is it for Apple to use this as a means, justified or otherwise, of controlling who can service their devices?

Apple needs to step up to the plate and repair or if necessary replace these bricked devices at their own cost. If I had been effected by this and Apple refused, I would by now have commenced a dispute in a wonderful institution here called the Consumer Trader and Tenancy Tribunal. Other Australian States have similar bodies, and I would venture to say similar bodies exist in most Western Countries. I suspect that this and similar Tribunals would have little time for Apple's actions, and would readily award damages. This would likely force Apple to act or die from a thousand cuts. Apple does some terrible things and some good ones. This time they are in the wrong and badly so. They need to deal with it and sooner rather than later.
darryl is offline   Reply With Quote