View Single Post
Old 12-09-2015, 10:51 AM   #92
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
Quote:
Originally Posted by the.Mtn.Man View Post
Except the "bug" apparently only happens on devices that have been modified by third-party "hacks". Again, you can't expect Kobo to take that into account when designing their firmware.
The only reason to write such checks, is if there is an expectation that they might, potentially, fail.
What do you think the purpose of it was, if not for people whose registration is broken without a third-party hack?

And it is completely obvious that they will see the exact same bug.

...

Unless, of course, you are suggesting that there is no way for someone's registration to be broken, unless they were using the third-party hack.

But that would mean this was designed purely to screw people using the hack.
In which case there is due cause to be pissed at Kobo.

...

Go ahead. Pick your poison.
eschwartz is offline   Reply With Quote