I've received a cuecat for scanning book ISBNs. Oh my, it's fast! Oh my, data from amazon.com is seriously bad! I'm scanning the kids books. See LibraryThing if you're curious.
Indeed! If it hadn't been for mangaroo's identifying the problem, it would have stayed broken. Tim clearly had looked at it and hadn't figured out the problem.
Thank you! That makes me feel less guilty about going head-to-head with Chris/stalepez in a "you are too ignoring me and my needs" whinefest.
I suspect Tim had the correction queued up -- I mean, he made it within 10 minutes of my guess as to what was causing the problem, and they would need some transparently accessible code to make a change that quickly. (They do seem to make all their changes directly to the production environment, which freaks me out.) I'm glad I researched the issue, though, because I had assumed LT's coding was 100% at fault (adding to my disdain), and really Amazon shares the responsibility for not standardizing their XML output. It's a disservice to all developers using Amazon's web services.
head-to-head with Chris/stalepez in a "you are too ignoring me and my needs" whinefest.
Wait, what? I missed something.
I suspect Tim had the correction queued up -- I mean, he made it within 10 minutes of my guess as to what was causing the problem
I'm relieved. Again, thanks so much. Other things are still messed up, but this had become a snowball sort of problem, getting worse and worse.
Still, I'd wandered in late to the denouement, courtesy technical difficulties on the homefront, and I was trying to NOT NOTICE how quickly that had seemed to occur. 'Cause, y'know, this would seem to imply that they'd been observing how people were growing progressively frustrated and sad by their silence on the subject for weeks and they were pointedly blowing us off.
I mean, because that seems rather unkind. So really trying not to leap to that conclusion.
But it left me feeling more grateful to everyone who'd kept that thread alive when it was obviously a waste of time than to LT's staff for the actual fix. *sigh*
(Added you, btw. I keep lecturing myself that I'm not allowed to add anyone new until I clean up my LJ mess, but [fill in random excuses for laziness here].)
See, the clever girl would just keep her mouth shut, but because of the friending, I am obliged to let you know I am a jerk (http://www.librarything.com/talktopic.php?topic=2823#27727).
Other things are still messed up
I have a couple of friends who won't join until the Japanese character set problems are solved, including author pages (pleeeease), sort order, Asian name order, and the mojibake'd mobile display. Sadness. (Are you watching, unibrain? Is my sorrow moving you?)
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
no subject
no subject
no subject
I suspect Tim had the correction queued up -- I mean, he made it within 10 minutes of my guess as to what was causing the problem, and they would need some transparently accessible code to make a change that quickly. (They do seem to make all their changes directly to the production environment, which freaks me out.) I'm glad I researched the issue, though, because I had assumed LT's coding was 100% at fault (adding to my disdain), and really Amazon shares the responsibility for not standardizing their XML output. It's a disservice to all developers using Amazon's web services.
no subject
Wait, what? I missed something.
I suspect Tim had the correction queued up -- I mean, he made it within 10 minutes of my guess as to what was causing the problem
I'm relieved. Again, thanks so much. Other things are still messed up, but this had become a snowball sort of problem, getting worse and worse.
Still, I'd wandered in late to the denouement, courtesy technical difficulties on the homefront, and I was trying to NOT NOTICE how quickly that had seemed to occur. 'Cause, y'know, this would seem to imply that they'd been observing how people were growing progressively frustrated and sad by their silence on the subject for weeks and they were pointedly blowing us off.
I mean, because that seems rather unkind. So really trying not to leap to that conclusion.
But it left me feeling more grateful to everyone who'd kept that thread alive when it was obviously a waste of time than to LT's staff for the actual fix. *sigh*
(Added you, btw. I keep lecturing myself that I'm not allowed to add anyone new until I clean up my LJ mess, but [fill in random excuses for laziness here].)
no subject
See, the clever girl would just keep her mouth shut, but because of the friending, I am obliged to let you know I am a jerk (http://www.librarything.com/talktopic.php?topic=2823#27727).
Other things are still messed up
I have a couple of friends who won't join until the Japanese character set problems are solved, including author pages (pleeeease), sort order, Asian name order, and the mojibake'd mobile display. Sadness. (Are you watching, unibrain? Is my sorrow moving you?)