<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: More on #amazonfail</title>
	<atom:link href="http://www.angelakorrati.com/2009/04/14/more-on-amazonfail/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.angelakorrati.com/2009/04/14/more-on-amazonfail/</link>
	<description>Angela Korra&#039;ti&#039;s books and writing</description>
	<lastBuildDate>Thu, 09 Feb 2012 05:03:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: annathepiper</title>
		<link>http://www.angelakorrati.com/2009/04/14/more-on-amazonfail/comment-page-1/#comment-37</link>
		<dc:creator>annathepiper</dc:creator>
		<pubDate>Thu, 16 Apr 2009 03:00:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.angelakorrati.com/?p=153#comment-37</guid>
		<description>Technoshaman @ 1: &quot;Amazon got played&quot; implies that someone did this deliberately, a supposition for which we have no real evidence; in fact, the one public claim of having done this deliberately has already been debunked.

It also goes against their own statement of &quot;embarrassing, ham-fisted cataloguing error&quot;, for what it&#039;s worth. We have no solid evidence or even a solid statement out of Amazon on what that actually means. But as I said in another comment to Paul on this thread, since I&#039;ve worked for places with large customer-facing databases, I can definitely conceive of how easy it is for one person typing in a query to fuck it up catastrophically. In the absence of any actual data as to the motive of the person who caused the cataloguing error in question, I&#039;m willing enough to chalk it up to &quot;horribly, horribly unfortunate screwup&quot; and move on. And hope that Amazon will take steps to prevent any such massive cataloguing errors in the future.</description>
		<content:encoded><![CDATA[<p>Technoshaman @ 1: &#8220;Amazon got played&#8221; implies that someone did this deliberately, a supposition for which we have no real evidence; in fact, the one public claim of having done this deliberately has already been debunked.</p>
<p>It also goes against their own statement of &#8220;embarrassing, ham-fisted cataloguing error&#8221;, for what it&#8217;s worth. We have no solid evidence or even a solid statement out of Amazon on what that actually means. But as I said in another comment to Paul on this thread, since I&#8217;ve worked for places with large customer-facing databases, I can definitely conceive of how easy it is for one person typing in a query to fuck it up catastrophically. In the absence of any actual data as to the motive of the person who caused the cataloguing error in question, I&#8217;m willing enough to chalk it up to &#8220;horribly, horribly unfortunate screwup&#8221; and move on. And hope that Amazon will take steps to prevent any such massive cataloguing errors in the future.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: annathepiper</title>
		<link>http://www.angelakorrati.com/2009/04/14/more-on-amazonfail/comment-page-1/#comment-36</link>
		<dc:creator>annathepiper</dc:creator>
		<pubDate>Thu, 16 Apr 2009 02:55:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.angelakorrati.com/?p=153#comment-36</guid>
		<description>Paul @ 2: I&#039;d heard about this, yeah, and fair &#039;nuff. I&#039;d be more comfortable with the system if it were exclusively user-driven, though. Some sort of check does need to be in place to make sure that huge swaths of products don&#039;t suddenly vanish out from the sight of people who might actually want to, y&#039;know, &lt;i&gt;buy them&lt;/i&gt;.

But as I said--having worked for places with large web-facing databases, yeah, I can conceive of how this could have been a particularly catastrophic error. Thanks for chiming in!</description>
		<content:encoded><![CDATA[<p>Paul @ 2: I&#8217;d heard about this, yeah, and fair &#8217;nuff. I&#8217;d be more comfortable with the system if it were exclusively user-driven, though. Some sort of check does need to be in place to make sure that huge swaths of products don&#8217;t suddenly vanish out from the sight of people who might actually want to, y&#8217;know, <i>buy them</i>.</p>
<p>But as I said&#8211;having worked for places with large web-facing databases, yeah, I can conceive of how this could have been a particularly catastrophic error. Thanks for chiming in!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://www.angelakorrati.com/2009/04/14/more-on-amazonfail/comment-page-1/#comment-35</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Wed, 15 Apr 2009 15:58:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.angelakorrati.com/?p=153#comment-35</guid>
		<description>I think this is one reason the ability to &quot;hide&quot; stuff exists...
http://blogofhilarity.com/2009/03/30/amazons-girl-scout-cookie-sales-leave-something-to-be-desired
I won&#039;t object to better checks to ensure it doesn&#039;t get misused, but I do think the ability has its place.  There were a lot of issues like that that came up as Amazon moved beyond only carrying books.</description>
		<content:encoded><![CDATA[<p>I think this is one reason the ability to &#8220;hide&#8221; stuff exists&#8230;<br />
<a href="http://blogofhilarity.com/2009/03/30/amazons-girl-scout-cookie-sales-leave-something-to-be-desired" rel="nofollow">http://blogofhilarity.com/2009/03/30/amazons-girl-scout-cookie-sales-leave-something-to-be-desired</a><br />
I won&#8217;t object to better checks to ensure it doesn&#8217;t get misused, but I do think the ability has its place.  There were a lot of issues like that that came up as Amazon moved beyond only carrying books.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Technoshaman</title>
		<link>http://www.angelakorrati.com/2009/04/14/more-on-amazonfail/comment-page-1/#comment-34</link>
		<dc:creator>Technoshaman</dc:creator>
		<pubDate>Wed, 15 Apr 2009 14:04:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.angelakorrati.com/?p=153#comment-34</guid>
		<description>I gotta agree.  Looks like Amazon got played like a lute, in a fashion difficult to prove especially if you want to keep proprietary code out of the public record...  I am concerned that the speaking parts of Amazon didn&#039;t treat this the same way Engineering did, e.g. Sev1, worth waking people up on Easter Sunday.... and that somebody obviously thought that unmoderated deranking was a Good Idea (or at least, didn&#039;t think it through)....

The word that comes to mind is &quot;sloppy&quot;.  I don&#039;t care for sloppy.</description>
		<content:encoded><![CDATA[<p>I gotta agree.  Looks like Amazon got played like a lute, in a fashion difficult to prove especially if you want to keep proprietary code out of the public record&#8230;  I am concerned that the speaking parts of Amazon didn&#8217;t treat this the same way Engineering did, e.g. Sev1, worth waking people up on Easter Sunday&#8230;. and that somebody obviously thought that unmoderated deranking was a Good Idea (or at least, didn&#8217;t think it through)&#8230;.</p>
<p>The word that comes to mind is &#8220;sloppy&#8221;.  I don&#8217;t care for sloppy.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

