What I've been reading lately
Birthday dinner at Bollywood in Pleasantville

Clay Shirky has an excellent post on #amazonfail

ShikybyDoctorow The Failure of #amazonfail (I have quoted extensively, but read the whole thing):

In 1987, a teenage girl in suburban New York was discovered wrapped in a garbage bag, smeared with feces, with racial epithets scrawled on her torso. She had been attacked by half a dozen white men, then left in that state on the grounds of an apartment building. As the court case against her accused assailants proceeded, it became clear that she’d actually faked the attack, in order not to be punished for running away from home. Though the event initially triggered enormous moral outrage, evidence that the event didn’t actually happen didn’t reverse that outrage. Moral judgment is harder to reverse than other, less emotional forms; when an event precipitates the cleansing anger of righteousness, admitting you were mistaken feels dirty. As a result, there can be an enormous premium put on finding rationales to continue to feel aggrieved, should the initial one disappear. Call it ‘conservation of outrage.’

A lot of us behaved like that this week, in our fury at Amazon. After an enormous number of books relating to lesbian, gay, bi-sexual, and transgendered (LGBT) themes lost their Amazon sales rank, and therefore their visibility in certain Amazon list and search functions, we participated in a public campaign, largely coordinated via the Twitter keyword #amazonfail (a form of labeling called a hashtag) because of a perceived injustice at the hands of that company, an injustice that didn’t actually occur.

. . .

So it is here. Whatever stupidities Amazon is guilty of, none of them are hanging offenses. The problems they have with labeling and handling contested categories is a problem with all categorization systems since the world began. Metadata is worldview; sorting is a political act. Amazon would love to avoid those problems if they could – who needs the tsouris? — but they can’t. No one gets cataloging “right” in any perfect sense, and no algorithm returns the “correct” results. We know that, because we see it every day, in every large-scale system we use. No set of labels or algorithms solves anything once and for all; any working system for showing data to the user is a bag of optimizations and tradeoffs that are a lot worse than some Platonic ideal, but a lot better than nothing.

We know all that, but we’re no longer willing to cut Amazon any slack, because we don’t trust them, and we don’t trust them because we feel like they did something bad, even though we now know, intellectually, that they didn’t actually do the bad thing we’ve come to hate them for. They didn’t intend to silence gay-themed work, and they didn’t provide the means for groups of anti-gay bigots to do so either. Even if the employee currently blamed for the change in the database turned out to be a virulent homophobe, the problem is in not having checks and balances for making changes to the database, not widespread bias.

We’re used to the future turning out differently than we expected; it happens all the time. When the past turns out differently, though, it can get really upsetting, and because people don’t like that kind of upset, we’re at risk of believing false things rather than revising our sense of what actually happened.

We shouldn’t let that happen here; conservation of outrage is the wrong answer. We can apologize to Amazon while not losing sight of the fact that homophobic bias is wrong and we have to fight it everywhere it exists. What we can’t do, can’t afford to do if we want to think of ourselves as people who care about injustice, is to fight it in places it doesn’t exist.

Yes. Yes. And yes. Rushing to judgement does not justice serve.

See also Darren Barefoot.

Photo of Clay Shirky by Cory Doctorow.

Comments