<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: HD DVD Cracks and Digg Censorship</title>
	<atom:link href="http://jrascher.wordpress.com/2007/05/01/hd-dvd-cracks-and-digg-censorship/feed/" rel="self" type="application/rss+xml" />
	<link>http://jrascher.wordpress.com/2007/05/01/hd-dvd-cracks-and-digg-censorship/</link>
	<description></description>
	<lastBuildDate>Fri, 05 Dec 2008 06:12:20 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: tropican8</title>
		<link>http://jrascher.wordpress.com/2007/05/01/hd-dvd-cracks-and-digg-censorship/#comment-59</link>
		<dc:creator>tropican8</dc:creator>
		<pubDate>Wed, 02 May 2007 05:18:45 +0000</pubDate>
		<guid isPermaLink="false">http://jrascher.wordpress.com/2007/05/01/hd-dvd-cracks-and-digg-censorship/#comment-59</guid>
		<description>You are only hearing a portion of the story. The processing key was found in February. The reason it&#039;s being posted now outside of Doom9 and the Wired News story that originally reported it was one of the staff of BoingBoing blogged about it. That blog was removed due to a DMCA takedown request. Another blogger started a campaign to spread the number because of that blog&#039;s deletion, and he succeeded. Google and Digg then received takedown notices. Google ignored it because they are large enough to fight a major legal battle. (Preventing people from spreading a number is indeed unjust.) Digg, however, is a small company and does not have the resources, even if this is wrong. They had to obey the request, following advice from their lawyers. Their users are rebelling anyway. The site&#039;s valued at $60 Million. It&#039;s owned by a small group of people, mostly 2. What would you have done? Flushed everything down the toilet?

I also posted about why spreading the number was not a good idea:

http://citrusgeek.wordpress.com/2007/05/01/why-spreading-the-number-is-not-a-good-idea/

The industry will never learn. This will just cause what I detail in that post to happen. If you want to fight DRM, this isn&#039;t the way to do it. Help out defectivebydesign.</description>
		<content:encoded><![CDATA[<p>You are only hearing a portion of the story. The processing key was found in February. The reason it&#8217;s being posted now outside of Doom9 and the Wired News story that originally reported it was one of the staff of BoingBoing blogged about it. That blog was removed due to a DMCA takedown request. Another blogger started a campaign to spread the number because of that blog&#8217;s deletion, and he succeeded. Google and Digg then received takedown notices. Google ignored it because they are large enough to fight a major legal battle. (Preventing people from spreading a number is indeed unjust.) Digg, however, is a small company and does not have the resources, even if this is wrong. They had to obey the request, following advice from their lawyers. Their users are rebelling anyway. The site&#8217;s valued at $60 Million. It&#8217;s owned by a small group of people, mostly 2. What would you have done? Flushed everything down the toilet?</p>
<p>I also posted about why spreading the number was not a good idea:</p>
<p><a href="http://citrusgeek.wordpress.com/2007/05/01/why-spreading-the-number-is-not-a-good-idea/" rel="nofollow">http://citrusgeek.wordpress.com/2007/05/01/why-spreading-the-number-is-not-a-good-idea/</a></p>
<p>The industry will never learn. This will just cause what I detail in that post to happen. If you want to fight DRM, this isn&#8217;t the way to do it. Help out defectivebydesign.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
