Date: 2009-04-13 04:41 pm (UTC)
No, the cust-sat rep wasn't lying.

It's just that what they were saying wasn't what they thought they were saying.

Policy: that which is deemed "adult" is de-sales-ranked.

Other thing: that which is GLBTBBQ is "adult".

The problem is that GLBTBBQ stuff is "adult", not that "adult" things are de-listed. Cus-sat rep said that the policy was de-listing "adult" things. Not that the policy was that GLBT things were "adult".

So: in February, a gentleman was told that his memoir of working as a gay stripper was deemed "adult". He points out, rightly, that Diabalo Cody's menior of working as a straight stripper wasn't -- but that MAY be an isolated incident, unrelated to the larger issue.

This is my guess:

The "policy" is de-listing adult things.

The event in February was an isolated incident which SHOULD have been a tip-off to this vulnerability.

The "glitch" is a mass categorization of GLBT things as "adult".

As far as I'm concerned, the significant question is "what is the glitch"? The options are: 1) an actual Amazon decision/policy (which I doubt), 2) someone within the company making an unsanctioned decision (possible) 3) an outside hacker group, either for political reasons or for the lulz (I have no way to even judge if this is possible or probable) 4) a result of adding in some sort of third-party database or something which had this unintended result (that'd be my guess, but I'm not certain.)
This account has disabled anonymous posting.
If you don't have an account you can create one now.
HTML doesn't work in the subject.
More info about formatting

May 2025

S M T W T F S
    123
45678910
11 121314151617
18192021222324
25262728293031

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Jul. 6th, 2025 02:24 am
Powered by Dreamwidth Studios