Quote:
Originally Posted by dgatwood
Fascinatingly, I contacted Kobo and asked what the status of fixing this bug was, and they said that the bug that caused this problem was fixed last year.
Perhaps it was a problem with their ingest process that is fixed now, and Tor just needs to resubmit the same content through the process again to get it fixed. Might be worth dropping Tor an email. Either that or Kobo customer support really needs to read their emails more carefully.
With that said, their first response had nothing to do with the question I asked, so it would not be a surprise if their second response didn't, either.
Incidentally, the Nook folks fared equally badly when I asked this question, giving an answer that was equally unrelated to the question I asked, so it looks like nobody actually reads our emails before sending a canned response. I'm pretty sure I could put together an Eliza bot that would do better than these companies' customer service reps do. They definitely fail the Turing test, on average, which is probably a big part of the reason why so many trivially fixed bugs never actually get fixed.
I'll give Amazon some credit. They at least appear to pass on the feedback to the actual developers if you sound like you know what you're talking about. (Whether they actually do or not is another question, because the bugs still never seem to get fixed, but at least they say that they did.)
|
This is in keeping with my experience. Kobo CS seems to be taking the carousel approach of; "We're working on it" -- "I think that was fixed recently" -- "what bug?" with regard to this issue. Depends on who you ask (and what time of day you ask it)
