<?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: &#8220;Controversy&#8221;</title>
	<atom:link href="http://www.ryanblock.com/2006/03/controversy/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ryanblock.com/2006/03/controversy/</link>
	<description>Editor and technology critic in the midst of founding a new content startup.</description>
	<pubDate>Wed, 07 Jan 2009 02:36:44 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: On linking, editorial &#187; Ryan Block</title>
		<link>http://www.ryanblock.com/2006/03/controversy/comment-page-1/#comment-13298</link>
		<dc:creator>On linking, editorial &#187; Ryan Block</dc:creator>
		<pubDate>Sun, 28 Jan 2007 02:07:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.ryanblock.com/archive/2006/03/controversy/#comment-13298</guid>
		<description>[...] my pal, and I&#8217;m looking forward to putting today&#8217;s pointless invective behind us; we all have our missteps. Yes, obviously we link to blogs, although sometimes we have to make the same kinds of choices [...]</description>
		<content:encoded><![CDATA[<p>[...] my pal, and I&#8217;m looking forward to putting today&#8217;s pointless invective behind us; we all have our missteps. Yes, obviously we link to blogs, although sometimes we have to make the same kinds of choices [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MJM.Basher</title>
		<link>http://www.ryanblock.com/2006/03/controversy/comment-page-1/#comment-102</link>
		<dc:creator>MJM.Basher</dc:creator>
		<pubDate>Sat, 25 Mar 2006 14:04:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.ryanblock.com/archive/2006/03/controversy/#comment-102</guid>
		<description>Ryan,

Anyone who has been reading Engadget for any length of time should know what a great site you guys (and gals) have put together.  Its obvious that you take great pains to provide accurate information, and you do a damn good job.  

With success comes some degree of jealousy from peers.  Being put under the microscope is part of being as successful as Engadget has become, and may I say that you are handling it superbly.

M</description>
		<content:encoded><![CDATA[<p>Ryan,</p>
<p>Anyone who has been reading Engadget for any length of time should know what a great site you guys (and gals) have put together.  Its obvious that you take great pains to provide accurate information, and you do a damn good job.  </p>
<p>With success comes some degree of jealousy from peers.  Being put under the microscope is part of being as successful as Engadget has become, and may I say that you are handling it superbly.</p>
<p>M</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Block</title>
		<link>http://www.ryanblock.com/2006/03/controversy/comment-page-1/#comment-99</link>
		<dc:creator>Ryan Block</dc:creator>
		<pubDate>Fri, 24 Mar 2006 15:29:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.ryanblock.com/archive/2006/03/controversy/#comment-99</guid>
		<description>Hey Matt, yeah, but I'm not sure when yet -- we were actually about to podcast when all this stuff broke on Monday, so we had to skip it. Peter and I may be traveling during the next couple of weeks for tradeshows, too, so it's hard to say. But I know there are a lot of people waiting for the next episode, We haven't forgotten or anything, thanks for your interest!

Best, Ryan</description>
		<content:encoded><![CDATA[<p>Hey Matt, yeah, but I&#8217;m not sure when yet &#8212; we were actually about to podcast when all this stuff broke on Monday, so we had to skip it. Peter and I may be traveling during the next couple of weeks for tradeshows, too, so it&#8217;s hard to say. But I know there are a lot of people waiting for the next episode, We haven&#8217;t forgotten or anything, thanks for your interest!</p>
<p>Best, Ryan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://www.ryanblock.com/2006/03/controversy/comment-page-1/#comment-97</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Fri, 24 Mar 2006 14:44:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.ryanblock.com/archive/2006/03/controversy/#comment-97</guid>
		<description>Off topic, but are you guys podcasting again anytime soon?</description>
		<content:encoded><![CDATA[<p>Off topic, but are you guys podcasting again anytime soon?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bad Press Damage Control: The Engadget and DAPreview Story - Destination: Success</title>
		<link>http://www.ryanblock.com/2006/03/controversy/comment-page-1/#comment-95</link>
		<dc:creator>Bad Press Damage Control: The Engadget and DAPreview Story - Destination: Success</dc:creator>
		<pubDate>Thu, 23 Mar 2006 18:09:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.ryanblock.com/archive/2006/03/controversy/#comment-95</guid>
		<description>[...] As Mr. Block points out, he thought DAPreview put their watermark on an image that wasn&#8217;t theirs in the first place. The post in question today is one I later edited under pretenses that the watermark was autogenerated — as they very often are — by the wrong party, which I believed to be DAPreview. [...]</description>
		<content:encoded><![CDATA[<p>[...] As Mr. Block points out, he thought DAPreview put their watermark on an image that wasn&#8217;t theirs in the first place. The post in question today is one I later edited under pretenses that the watermark was autogenerated — as they very often are — by the wrong party, which I believed to be DAPreview. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chrono Tron - 100%</title>
		<link>http://www.ryanblock.com/2006/03/controversy/comment-page-1/#comment-94</link>
		<dc:creator>Chrono Tron - 100%</dc:creator>
		<pubDate>Thu, 23 Mar 2006 16:08:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.ryanblock.com/archive/2006/03/controversy/#comment-94</guid>
		<description>&lt;strong&gt;Nintendo Revolution to be Renamed Go?&lt;/strong&gt;

Nintendo Revolution, Nintendo&#8217;s next-gen console has recieved a lot of fanfare and Nintendo has promised that this may be the console to revolutionize the whole video-game industry. Nintendo has also said that this console may be released Novembe...</description>
		<content:encoded><![CDATA[<p><strong>Nintendo Revolution to be Renamed Go?</strong></p>
<p>Nintendo Revolution, Nintendo&#8217;s next-gen console has recieved a lot of fanfare and Nintendo has promised that this may be the console to revolutionize the whole video-game industry. Nintendo has also said that this console may be released Novembe&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesse</title>
		<link>http://www.ryanblock.com/2006/03/controversy/comment-page-1/#comment-91</link>
		<dc:creator>Jesse</dc:creator>
		<pubDate>Wed, 22 Mar 2006 20:40:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.ryanblock.com/archive/2006/03/controversy/#comment-91</guid>
		<description>Yeah, that definitely could have been resolved by a small little e-mail. 

Of course, what better way to get cheap traffic?</description>
		<content:encoded><![CDATA[<p>Yeah, that definitely could have been resolved by a small little e-mail. </p>
<p>Of course, what better way to get cheap traffic?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Block</title>
		<link>http://www.ryanblock.com/2006/03/controversy/comment-page-1/#comment-90</link>
		<dc:creator>Ryan Block</dc:creator>
		<pubDate>Wed, 22 Mar 2006 13:08:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.ryanblock.com/archive/2006/03/controversy/#comment-90</guid>
		<description>Thanks, I appreciate the sentiments. Obviously the stakes are very high when you're one of the top blogs in the world, and this just means that we have to be even more careful than we already are (which is very careful). I'm not going to whine about being the target, but I do wish the community would try harder to get along and settle petty disputes in private without bringing it to the court of public opinion -- especially since we at Engadget tend to keep a low profile and never, ever publicly complain when blogs bite our content or appear to have "blacklisted" us.

Best, Ryan</description>
		<content:encoded><![CDATA[<p>Thanks, I appreciate the sentiments. Obviously the stakes are very high when you&#8217;re one of the top blogs in the world, and this just means that we have to be even more careful than we already are (which is very careful). I&#8217;m not going to whine about being the target, but I do wish the community would try harder to get along and settle petty disputes in private without bringing it to the court of public opinion &#8212; especially since we at Engadget tend to keep a low profile and never, ever publicly complain when blogs bite our content or appear to have &#8220;blacklisted&#8221; us.</p>
<p>Best, Ryan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesse</title>
		<link>http://www.ryanblock.com/2006/03/controversy/comment-page-1/#comment-88</link>
		<dc:creator>Jesse</dc:creator>
		<pubDate>Wed, 22 Mar 2006 04:14:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.ryanblock.com/archive/2006/03/controversy/#comment-88</guid>
		<description>Some people are just born losers. 

To be honest, I don't actually read Engadget that often, but I do occasionally, and I find it rather entertaining. But that's not the point. 

People seem to get some perverted self-rightous satisfaction from taking down the big guys...

I guess there's no such thing as a mistake</description>
		<content:encoded><![CDATA[<p>Some people are just born losers. </p>
<p>To be honest, I don&#8217;t actually read Engadget that often, but I do occasionally, and I find it rather entertaining. But that&#8217;s not the point. </p>
<p>People seem to get some perverted self-rightous satisfaction from taking down the big guys&#8230;</p>
<p>I guess there&#8217;s no such thing as a mistake</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Knots</title>
		<link>http://www.ryanblock.com/2006/03/controversy/comment-page-1/#comment-87</link>
		<dc:creator>Knots</dc:creator>
		<pubDate>Tue, 21 Mar 2006 17:13:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.ryanblock.com/archive/2006/03/controversy/#comment-87</guid>
		<description>It seems all very explainable and inncocent to me. good luck all concerned</description>
		<content:encoded><![CDATA[<p>It seems all very explainable and inncocent to me. good luck all concerned</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gadgetizer.com</title>
		<link>http://www.ryanblock.com/2006/03/controversy/comment-page-1/#comment-86</link>
		<dc:creator>Gadgetizer.com</dc:creator>
		<pubDate>Tue, 21 Mar 2006 09:48:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.ryanblock.com/archive/2006/03/controversy/#comment-86</guid>
		<description>&lt;strong&gt;Engadget and Unethical Blogging - set 2&lt;/strong&gt;

	Since the previous post was getting  very big, it&#8217;s better to keep it short and to the point, with more updated news.
	Other interesting posts:
	- Ryan Block, the person that made the image/source mistake that sparked all this, has posted his th...</description>
		<content:encoded><![CDATA[<p><strong>Engadget and Unethical Blogging - set 2</strong></p>
<p>	Since the previous post was getting  very big, it&#8217;s better to keep it short and to the point, with more updated news.<br />
	Other interesting posts:<br />
	- Ryan Block, the person that made the image/source mistake that sparked all this, has posted his th&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
