<?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: Viacom  v. YouTube: When Is It Storage? When Is It a Public Performance?</title>
	<atom:link href="http://madisonian.net/2010/06/23/viacom-v-youtube-when-is-it-storage-when-is-it-a-public-performance/feed/" rel="self" type="application/rss+xml" />
	<link>http://madisonian.net/2010/06/23/viacom-v-youtube-when-is-it-storage-when-is-it-a-public-performance/</link>
	<description>a blog about law, tech, culture, and related things</description>
	<lastBuildDate>Thu, 10 May 2012 20:32:56 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Chris Newman</title>
		<link>http://madisonian.net/2010/06/23/viacom-v-youtube-when-is-it-storage-when-is-it-a-public-performance/comment-page-1/#comment-308466</link>
		<dc:creator>Chris Newman</dc:creator>
		<pubDate>Thu, 24 Jun 2010 15:18:58 +0000</pubDate>
		<guid isPermaLink="false">http://madisonian.net/?p=4424#comment-308466</guid>
		<description>Exactly the right question.  The district court here took two huge steps of debatable validity.  The first was to hold that since someone who engages in  “transmission, routing, or providing of connections for digital online communications” is an ISP, and ISPs get immunity from liability “by reason of storage”, then “storage” must inherently include “transmission, routing, or providing of connections for digital online communications.”   This obviously doesn’t follow logically:  

All people who do A are Bs.
All Bs are immune when they do C.
Therefore doing A constitutes doing C.  (????)

That said, there is a common sense core of truth to what the court is saying here—obviously a safe harbor for “storage” has to include, at minimum, the retransmission of the stored materials to the storer.  It does not necessarily follow that a safe harbor for storage has to include transmission of stored materials to people other than the storer, or transmission in the form of displays or performances, particularly when the business model is one that reaps all its profits, not from providing “storage” services to uploaders, but from providing performances to people other than the uploader.

I think the Second Circuit has to answer two other interesting questions as well:

1)	 Is there any such thing as a judicially cognizable “red flag” of infringement?   I love it how the opinion quotes at length the legislative history, which seems to state that the only thing that would qualify as a “red flag” is a pirate website that trumpets its pirate status.   And then right after that we get the cite to CCBill, in which we learned that there really is no such thing as obviously trumpeting your pirate status, any more than there is any such thing as obviously infringing.  

2)	Is there any such thing as a violation of 512(c)(1)(A) or (B) that is not also a violation of (C)?  If you need a “red flag” to be on the hook under either (A) or (B), and there is no such thing as a red flag, then really all we’re left with is (C).   Maybe that’s the way it should be—I’m agnostic on that.  But I tend to think that interpretations of statutory language that result in huge null sets are suspect.</description>
		<content:encoded><![CDATA[<p>Exactly the right question.  The district court here took two huge steps of debatable validity.  The first was to hold that since someone who engages in  “transmission, routing, or providing of connections for digital online communications” is an ISP, and ISPs get immunity from liability “by reason of storage”, then “storage” must inherently include “transmission, routing, or providing of connections for digital online communications.”   This obviously doesn’t follow logically:  </p>
<p>All people who do A are Bs.<br />
All Bs are immune when they do C.<br />
Therefore doing A constitutes doing C.  (????)</p>
<p>That said, there is a common sense core of truth to what the court is saying here—obviously a safe harbor for “storage” has to include, at minimum, the retransmission of the stored materials to the storer.  It does not necessarily follow that a safe harbor for storage has to include transmission of stored materials to people other than the storer, or transmission in the form of displays or performances, particularly when the business model is one that reaps all its profits, not from providing “storage” services to uploaders, but from providing performances to people other than the uploader.</p>
<p>I think the Second Circuit has to answer two other interesting questions as well:</p>
<p>1)	 Is there any such thing as a judicially cognizable “red flag” of infringement?   I love it how the opinion quotes at length the legislative history, which seems to state that the only thing that would qualify as a “red flag” is a pirate website that trumpets its pirate status.   And then right after that we get the cite to CCBill, in which we learned that there really is no such thing as obviously trumpeting your pirate status, any more than there is any such thing as obviously infringing.  </p>
<p>2)	Is there any such thing as a violation of 512(c)(1)(A) or (B) that is not also a violation of (C)?  If you need a “red flag” to be on the hook under either (A) or (B), and there is no such thing as a red flag, then really all we’re left with is (C).   Maybe that’s the way it should be—I’m agnostic on that.  But I tend to think that interpretations of statutory language that result in huge null sets are suspect.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

