Don't ever do that marginalization thing
Apr. 17th, 2009 08:32 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
Wait, should I do a follow-up post on that #AmazonFail thing? You all heard about the kinda-sorta resolution from everyone else already, right? Yeah.
So I dunno. I'm surely not in a boycottin' mood; the magnitude of the thing and the associated certainty of its discovery makes me pretty sure that there was no coherent and unified plan behind it.
But the fact that it was obviously some sort of cock-up doesn't mean that it wasn't a suspicious or potentially revealing cock-up. For one thing, we now know that Amazon has a stealthily implemented search-censoring system in place, and that it was already in the habit of playing nanny with no openness or disclosure. This seems like an important thing to know. And the fact that whoever had their finger on the trigger was inclined in the first place to hold gay material to a higher standard of "adult"-ness than straight material is both worrying and unsurprising. In other words, the situation was a fuckup, but the existence of the conditions that enabled the fuckup still implies a certain amount of moral failure. If you get me.
So I'm not in a boycottin' mood, but I'm also disinclined to go on about poor li'l Amazon getting piled-on. They can take their lumps, clean up their act, and we'll all move forward from there.
So I dunno. I'm surely not in a boycottin' mood; the magnitude of the thing and the associated certainty of its discovery makes me pretty sure that there was no coherent and unified plan behind it.
But the fact that it was obviously some sort of cock-up doesn't mean that it wasn't a suspicious or potentially revealing cock-up. For one thing, we now know that Amazon has a stealthily implemented search-censoring system in place, and that it was already in the habit of playing nanny with no openness or disclosure. This seems like an important thing to know. And the fact that whoever had their finger on the trigger was inclined in the first place to hold gay material to a higher standard of "adult"-ness than straight material is both worrying and unsurprising. In other words, the situation was a fuckup, but the existence of the conditions that enabled the fuckup still implies a certain amount of moral failure. If you get me.
So I'm not in a boycottin' mood, but I'm also disinclined to go on about poor li'l Amazon getting piled-on. They can take their lumps, clean up their act, and we'll all move forward from there.
no subject
Date: 2009-04-18 07:11 am (UTC)I mean, what's interesting about Heather Has Two Mommies is that it's hardcore famous for the number of queer rights battles in school library systems it's been at the center of. No one who knew anything about selling books would de-list that sucker even if they really wanted to. The context of it being both completely innocuous and a locus of insane-o controversy means that one, someone will always notice immediately if you mess with Heather, and two, INSTANT QUEER AND ALLY RAGE EVERYWHERE. Anyone who knew books well enough to rise to a position of making implementation decisions about search discrimination would know to never involve Heather in a de-listing/de-shelving campaign, because it is the Land War In Asia of censorship fights. Someone did something they totally weren't supposed to do.
Uh, none of that lets anyone off the hook. It's entirely possible that this was a Raskolnikov-style "my only crime was getting caught" situation. My current belief is that there was never any official policy — or even a rough consensus within Amazon — that everything gay should get de-ranked. But the existence of the de-ranking tool is evil, the opacity of the search censoring is evil, and the fact that the people who make these mistakes (or "mistakes") always seem to target some already marginalized segment of society is evil.
I have no IDEA what to say about those emails they sent. Those were just surreal and creepy.
no subject
Date: 2009-04-18 08:04 am (UTC)The emails are more dubious, because I know from experience that if you're a customer support peon, you are not always informed of what's going on. It's entirely possible that at the time the thing was made widely public last weekend, the person who sent the infamous "new policy" email thought it was a new policy, because such a policy does make some kind of sense, and they had no idea what in particular this "new policy" was actually affecting. So the recent one doesn't really strike me as deliberately misleading. Even the one back in February might not have been deliberately misleading on the CS rep's part. But it does indicate that this wasn't sudden catastrophe, which Amazon continues to cast it as.
I guess I care more about finding out what actually happened than about just reversing it and putting it to rest. Call it my inner Phoenix Wright. ;)