Why do you think otherwise?
Note: I love Amazon and agreed with your defending of them in the original post. I'm honestly surprised that it isn't obvious that the article influenced Amazon here.
I find the alternatives much more surprising:
- Amazon did not have a policy on this issue prior to this situation.
- Amazon's policy is to remove any and all purchased content without explanation or warning, and they thought that no one would mind. Once they thought about it, they changed their policy.
- Or they thought they might as well screw as many people as they could until the issue became a big deal, at which point they would suddenly change their policy
- (or pretend that their policy was different all along).
- BTW, There are no bugs in Amazon's code, so one of the above must be true and any removal of content had to be due to their evil policies
- The customer service department at Amazon ignores mistakes that they know about and could fix until enough computer programmers and tech enthusiasts know about them, too.
- (because, of course, the readership of hn/wired/etc makes up a significant portion of Amazon's revenues. I mean, doesn't everyone talk about reddit at the bar after work?)
Instead, why couldn't there just be a simple mistake, which was fixed once someone became aware of it? We could all agree that the high visibility of the issue helped make the mistake clear (which Linn's emails did not) and high priority (which does not mean that it would otherwise have been completely ignored).
Although, them reversing the wipe purely to save their publish image is equally despicable in my opinion.
http://news.ycombinator.com/over?points=1000
1000 points happened around a month ago as well, but before that there doesn't seem to be any, though I'd expect Steve Job's death to be much higher - perhaps it was hidden after a time?
For a full list of stories with high-scores you can consult HNSearch [1]
[1]: http://www.hnsearch.com/search#request/submissions&sortb...
Most likely, a few engineers from Amazon saw the story and forwarded it to the right person. That sort of thing is fairly common even in large companies; I ask friends who work at Facebook for favors all the time, for example.
Best part was we got an email later that day saying "Student Research and Development" was obscene, and would need to be changed.
It shouldn't surprise me that some give credence to conspiracy theories but it does. Amazon panicked and reversed itself because a story about removing DRM was on the front page of HN? Seriously?
What you'll find with customer service departments is that what they do is largely prescribed by scripts. Call centers work like this (to the point of there being checking to see that people don't deviate from the script). They will have procedures that must be followed.
The Mark Fiore example [1] springs to mind. Some saw some global conspiracy. The more likely explanation is that the procedures defined for those approving apps just hadn't taken such a scenario into account when being written ie it was an oversight (a "mistake" as Steve Jobs called it).
We're all too willing to accept bugs in software. Procedures that humans need to follow--particularly if they need to follow them rigidly--have bugs too. The more discretion you give those following the procedures, the more you tend to just add inconsistency.
[1]: http://mediadecoder.blogs.nytimes.com/2010/04/20/pulitzer-wi...
EDIT: to clarify, I think the original story getting as much of an audience as it did certainly helped and may well have been instrumental. It's kind of sad that that's the case. I was referring to some commenters putting forward theories about the DRM removal story being the catalyst for action here, which is ludicrous.