Azure Jane Lunatic (Azz) 🌺 (
azurelunatic) wrote2009-04-13 12:38 pm
Quick amazonfail linkdump:
http://dearauthor.com/wordpress/2009/04/12/amazon-possibly-using-category-metadata-to-filter-rankings/
http://markprobst.livejournal.com/15507.html
http://community.livejournal.com/meta_writer/12478.html
http://community.livejournal.com/metafandom/238844.html (lots of links plus some non-amazonfail bonuses)
http://belmikey.livejournal.com/425631.html?thread=4245151#t4245151
http://markprobst.livejournal.com/15507.html
http://community.livejournal.com/meta_writer/12478.html
http://community.livejournal.com/metafandom/238844.html (lots of links plus some non-amazonfail bonuses)
http://belmikey.livejournal.com/425631.html?thread=4245151#t4245151

no subject
In case you haven't heard yet
All this commotion over a few lines of code. Just an exploited script is all.
no subject
no subject
The fact that so many books were removed in such a short space of time and were so specifically targeted really seems to point to a script exploit with automatic action that may have been done with little to no review. The problem is within the system.
no subject
I'm sure that somewhere in there is an automatic system gone completely fucking nuts. I'm disinclined to believe without further proof that it was due to repeated reporting by a malicious script, or that it was that particular troll responsible.
no subject
http://belmikey.livejournal.com/425631.html?thread=4245151#t4245151
As I said recently elsewhere, there's probably more background and nuance to this, but I've been in that situation and it's hugely frustrating.
Also, it's easy to call on a crowd and incite mass-uprising, but few people ever take quite as much effort to call them off or disseminate information when it's of an exculpatory nature.
no subject
no subject
http://tehdely.livejournal.com/88823.html?thread=334839#t334839
In order to stop assumptions, if I had time, I'd use the wayback machine to see how search results/rankings and sales rankings (and/or some sales ranking pages, maybe, like on, say Ellen's biography) changed in the past week. And I'd view page source, maybe using Firebug too, to see what kinds of invisible tags or directions were part of the code (just as a fishing expedition, not necessarily looking for A Particular Bug). Separating out this particular issue from pre-existing issues would help for greater understanding of the situation.
It may be that some of those books just weren't high on the search results anyway, unrelated to this one issue. It may be that the flagging and this particular technical glitch are unrelated as far as this particular incident goes.
Finding out exactly what is new, what was existing, and watching as some of the changes are reverted will probably shed light. It would be nicer if Amazon could sit down and explain it in a question and answer, but I'm now more likely to be patient waiting for that.
no subject
It kind of bothers me that people think that they can nag their friends working at Amazon for some answer. :| I'm certain the people either don't have access to that information, or don't want to loose their job trying to reply with office hearsay.
no subject
After hearing from people on the inside at Amazon, I am convinced it was in fact, a "glitch."
Well, more like user error--some idiot editing code for one of the many international versions of Amazon mixed up the difference between "adult" and "erotic" and "sexuality". All the sites are tied together, so editing one affected all for blacklisting, and ta-da, you get the situation.
The CS rep who responded that this was Amazon policy was just confused about what they were talking about, and gave standard boilerplate about porn.
The dumbest part is saying it was a "glitch". A "glitch"? Just say that it was one of your workers making an editing error. Really dumb PR move, that one.
Never ascribe to malice and all that...