Quote:
Originally Posted by taming
I challenge you to visit the other forums and find active developer interactions. Once they understood the situation they acted and told us about it.
|
Active developer interactions? If I'm remembering correctly (and I haven't gone through all the threads this morning), we've gotten 10 posts from Kobo here:
- six from MDK, two announcing the release, one asking about more information about a relatively small bug (considering), one explaining the clock changes and two trying to help sven with his bricked Touch
- three from Samheer, one saying they were looking into the upgrade problem and asking people with bricked Touch's due to 2.0.0 to email him, one stating the pulling of the 2.0.0 release, and one not commenting on when requirements for resets with the new release
- and one from DarrellAtKobo, republishing Kobo's blog entry on the problems with 2.0.0.
Considering that this is a serious enough problem to require the pulling of the release, this is very little interaction from Kobo people.
And there has been very little accurate or usable communication of how to recover from the upgrade bricking your Touch. If I hadn't backed up my Touch before the upgrade, I would be very, very pissed right now. And remember, this is an upgrade that the Kobo software gave no warning about, nor allowed you to opt in or out of.
Quote:
Originally Posted by taming
I am quite sure their help line now is giving accurate information to people, too. Remember this is a huge issue that in truth impacted a small percentage of users.
|
'
now is giving accurate information'?