<?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: Are Takedowns in 48 Hours &#8220;Expeditious&#8221; Enough?&#8211;Square Ring v. UStream	</title>
	<atom:link href="https://blog.ericgoldman.org/archives/2015/01/are-takedowns-in-48-hours-expeditious-enough-square-ring-v-ustream.htm/feed" rel="self" type="application/rss+xml" />
	<link>https://blog.ericgoldman.org/archives/2015/01/are-takedowns-in-48-hours-expeditious-enough-square-ring-v-ustream.htm</link>
	<description></description>
	<lastBuildDate>Fri, 13 Feb 2015 02:40:00 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Methaya Sirichit		</title>
		<link>https://blog.ericgoldman.org/archives/2015/01/are-takedowns-in-48-hours-expeditious-enough-square-ring-v-ustream.htm#comment-1182</link>

		<dc:creator><![CDATA[Methaya Sirichit]]></dc:creator>
		<pubDate>Fri, 13 Feb 2015 02:40:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericgoldman.org/?p=13654#comment-1182</guid>

					<description><![CDATA[Actually copyright law in most countries (as per Berne Convention) do not protect live broadcast and only protect &quot;rebroadcasting.&quot; As a result, it is not an infringement if the infringer live-stream the signal coming from different telecom providers.]]></description>
			<content:encoded><![CDATA[<p>Actually copyright law in most countries (as per Berne Convention) do not protect live broadcast and only protect &#8220;rebroadcasting.&#8221; As a result, it is not an infringement if the infringer live-stream the signal coming from different telecom providers.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: j.r.mchale : Recommended:		</title>
		<link>https://blog.ericgoldman.org/archives/2015/01/are-takedowns-in-48-hours-expeditious-enough-square-ring-v-ustream.htm#comment-1157</link>

		<dc:creator><![CDATA[j.r.mchale : Recommended:]]></dc:creator>
		<pubDate>Wed, 04 Feb 2015 16:50:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericgoldman.org/?p=13654#comment-1157</guid>

					<description><![CDATA[[&#8230;] Are Takedowns in 48 Hours &#8216;Expeditious&#8217; Enough? The Case of Square Ring v. UStream  – Professor Eric Goldman at the Technology &#038; Marketing Law Blog. [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] Are Takedowns in 48 Hours &#8216;Expeditious&#8217; Enough? The Case of Square Ring v. UStream  – Professor Eric Goldman at the Technology &amp; Marketing Law Blog. [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Zachary Strebeck		</title>
		<link>https://blog.ericgoldman.org/archives/2015/01/are-takedowns-in-48-hours-expeditious-enough-square-ring-v-ustream.htm#comment-1149</link>

		<dc:creator><![CDATA[Zachary Strebeck]]></dc:creator>
		<pubDate>Mon, 02 Feb 2015 04:03:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericgoldman.org/?p=13654#comment-1149</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://blog.ericgoldman.org/archives/2015/01/are-takedowns-in-48-hours-expeditious-enough-square-ring-v-ustream.htm#comment-1148&quot;&gt;Anonymous&lt;/a&gt;.

Agree on all counts.


Though I believe the law should require shorter times on both ends, particularly when most of this can be automated. When a YouTube video, for instance, gets hit with a takedown, the amount of revenue that the creator could be missing out on could be very big (by YouTube creator standards, anyway) if they have to wait the 10 days.


Although the point of the 10 days seems to be to give them the time to file their lawsuit. It&#039;s a difficult situation all around, i suppose.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://blog.ericgoldman.org/archives/2015/01/are-takedowns-in-48-hours-expeditious-enough-square-ring-v-ustream.htm#comment-1148">Anonymous</a>.</p>
<p>Agree on all counts.</p>
<p>Though I believe the law should require shorter times on both ends, particularly when most of this can be automated. When a YouTube video, for instance, gets hit with a takedown, the amount of revenue that the creator could be missing out on could be very big (by YouTube creator standards, anyway) if they have to wait the 10 days.</p>
<p>Although the point of the 10 days seems to be to give them the time to file their lawsuit. It&#8217;s a difficult situation all around, i suppose.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Anonymous		</title>
		<link>https://blog.ericgoldman.org/archives/2015/01/are-takedowns-in-48-hours-expeditious-enough-square-ring-v-ustream.htm#comment-1148</link>

		<dc:creator><![CDATA[Anonymous]]></dc:creator>
		<pubDate>Mon, 02 Feb 2015 03:42:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericgoldman.org/?p=13654#comment-1148</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://blog.ericgoldman.org/archives/2015/01/are-takedowns-in-48-hours-expeditious-enough-square-ring-v-ustream.htm#comment-1147&quot;&gt;Zachary Strebeck&lt;/a&gt;.

If the ISP wants to retain safe harbor, it cannot evaluate the merit of a takedown. At best, it can cite material deficiencies in the notice, like a missing &quot;good faith&quot; statement, and ask for an updated notice to be resubmitted.

Of course, the ISP can choose to evaluate on the merits and resist takedown notices that it determines to be improper, but it will lose safe harbor protection in doing so.

Your statement of &quot;giving the ISP at least 10 business days to reenable access after a counter-notice&quot; is slightly incorrect. The ISP doesn&#039;t have 10 days to re-enable after a counter-notice, it *must* wait at least 10, but no more than 14 business days after a counter-notice before it is allowed to re-enable.

I do agree with you about your sentiment regarding the timing of the takedown/reposting, though. If the ISP is expected to remove expeditiously, shouldn&#039;t the claimant also be expected to file a lawsuit expeditiously if there is a counter-claim? If so, then that would mean that 10-14 business days is &quot;expeditious.&quot;]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://blog.ericgoldman.org/archives/2015/01/are-takedowns-in-48-hours-expeditious-enough-square-ring-v-ustream.htm#comment-1147">Zachary Strebeck</a>.</p>
<p>If the ISP wants to retain safe harbor, it cannot evaluate the merit of a takedown. At best, it can cite material deficiencies in the notice, like a missing &#8220;good faith&#8221; statement, and ask for an updated notice to be resubmitted.</p>
<p>Of course, the ISP can choose to evaluate on the merits and resist takedown notices that it determines to be improper, but it will lose safe harbor protection in doing so.</p>
<p>Your statement of &#8220;giving the ISP at least 10 business days to reenable access after a counter-notice&#8221; is slightly incorrect. The ISP doesn&#8217;t have 10 days to re-enable after a counter-notice, it *must* wait at least 10, but no more than 14 business days after a counter-notice before it is allowed to re-enable.</p>
<p>I do agree with you about your sentiment regarding the timing of the takedown/reposting, though. If the ISP is expected to remove expeditiously, shouldn&#8217;t the claimant also be expected to file a lawsuit expeditiously if there is a counter-claim? If so, then that would mean that 10-14 business days is &#8220;expeditious.&#8221;</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Zachary Strebeck		</title>
		<link>https://blog.ericgoldman.org/archives/2015/01/are-takedowns-in-48-hours-expeditious-enough-square-ring-v-ustream.htm#comment-1147</link>

		<dc:creator><![CDATA[Zachary Strebeck]]></dc:creator>
		<pubDate>Mon, 02 Feb 2015 02:10:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericgoldman.org/?p=13654#comment-1147</guid>

					<description><![CDATA[My understanding is that the ISP is not in the position to evaluate the merits of a takedown request. That is for the person filing the counter-notice. 

I would argue that, regardless of the law, making the takedown happen within 48 hours, but giving the ISP at least 10 business days to reenable access after a counter-notice seems a bit unfair to someone who has a legitimate claim of fair use or mistake on the part of the party sending the original notice.

The whole thing is kind of messy, unfortunately.]]></description>
			<content:encoded><![CDATA[<p>My understanding is that the ISP is not in the position to evaluate the merits of a takedown request. That is for the person filing the counter-notice. </p>
<p>I would argue that, regardless of the law, making the takedown happen within 48 hours, but giving the ISP at least 10 business days to reenable access after a counter-notice seems a bit unfair to someone who has a legitimate claim of fair use or mistake on the part of the party sending the original notice.</p>
<p>The whole thing is kind of messy, unfortunately.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Anonymous		</title>
		<link>https://blog.ericgoldman.org/archives/2015/01/are-takedowns-in-48-hours-expeditious-enough-square-ring-v-ustream.htm#comment-1146</link>

		<dc:creator><![CDATA[Anonymous]]></dc:creator>
		<pubDate>Sun, 01 Feb 2015 02:38:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericgoldman.org/?p=13654#comment-1146</guid>

					<description><![CDATA[At the hosting provider where I work, DMCA takedowns are generally handled by forwarding the notice to the customer and giving them two business days to remove the content. After this period expires, if the content is still present, we take action. It&#039;s done this way to allow the site owners to remove the content claimed as infringing without someone on our staff possibly breaking something on the customer&#039;s site because we aren&#039;t familiar with the website coding.

Our lawyers seem to think that two business days is expeditious. Something else to consider in cases of livestreaming is whether a provider&#039;s DMCA-handling staff is even in the office and able to respond to a request at the time the stream occurs. My company&#039;s legal department is not 24/7, for example.]]></description>
			<content:encoded><![CDATA[<p>At the hosting provider where I work, DMCA takedowns are generally handled by forwarding the notice to the customer and giving them two business days to remove the content. After this period expires, if the content is still present, we take action. It&#8217;s done this way to allow the site owners to remove the content claimed as infringing without someone on our staff possibly breaking something on the customer&#8217;s site because we aren&#8217;t familiar with the website coding.</p>
<p>Our lawyers seem to think that two business days is expeditious. Something else to consider in cases of livestreaming is whether a provider&#8217;s DMCA-handling staff is even in the office and able to respond to a request at the time the stream occurs. My company&#8217;s legal department is not 24/7, for example.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Julie		</title>
		<link>https://blog.ericgoldman.org/archives/2015/01/are-takedowns-in-48-hours-expeditious-enough-square-ring-v-ustream.htm#comment-1139</link>

		<dc:creator><![CDATA[Julie]]></dc:creator>
		<pubDate>Tue, 27 Jan 2015 19:16:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericgoldman.org/?p=13654#comment-1139</guid>

					<description><![CDATA[Recent decision in France involving Daily Motion said a week was too long to leave content up. http://ipkitten.blogspot.com/2014/12/tf1-v-dailymotion-meet-third-generation.html]]></description>
			<content:encoded><![CDATA[<p>Recent decision in France involving Daily Motion said a week was too long to leave content up. <a href="http://ipkitten.blogspot.com/2014/12/tf1-v-dailymotion-meet-third-generation.html" rel="nofollow ugc">http://ipkitten.blogspot.com/2014/12/tf1-v-dailymotion-meet-third-generation.html</a></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: curtisneeley		</title>
		<link>https://blog.ericgoldman.org/archives/2015/01/are-takedowns-in-48-hours-expeditious-enough-square-ring-v-ustream.htm#comment-1138</link>

		<dc:creator><![CDATA[curtisneeley]]></dc:creator>
		<pubDate>Tue, 27 Jan 2015 18:55:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericgoldman.org/?p=13654#comment-1138</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://blog.ericgoldman.org/archives/2015/01/are-takedowns-in-48-hours-expeditious-enough-square-ring-v-ustream.htm#comment-1137&quot;&gt;David S. Gingras&lt;/a&gt;.

48 hours will not be enough time for a jury. After being shown how 
easily taking things offline is, the damages should be easily supported 
because violation take-downs should be nearly-immediately where possible
 and without counter-notices.  GOOG should soon be battling to survive at all because of ignoring several hundred of mine for years. Justice is just no possible in the &quot;America&quot; that overthrew the United States.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://blog.ericgoldman.org/archives/2015/01/are-takedowns-in-48-hours-expeditious-enough-square-ring-v-ustream.htm#comment-1137">David S. Gingras</a>.</p>
<p>48 hours will not be enough time for a jury. After being shown how<br />
easily taking things offline is, the damages should be easily supported<br />
because violation take-downs should be nearly-immediately where possible<br />
 and without counter-notices.  GOOG should soon be battling to survive at all because of ignoring several hundred of mine for years. Justice is just no possible in the &#8220;America&#8221; that overthrew the United States.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: David S. Gingras		</title>
		<link>https://blog.ericgoldman.org/archives/2015/01/are-takedowns-in-48-hours-expeditious-enough-square-ring-v-ustream.htm#comment-1137</link>

		<dc:creator><![CDATA[David S. Gingras]]></dc:creator>
		<pubDate>Tue, 27 Jan 2015 18:49:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericgoldman.org/?p=13654#comment-1137</guid>

					<description><![CDATA[Wow -- very scary ruling, but very relevant; thanks for posting.  It is baffling that the court would say whether or not Ustream acted &quot;expeditiously&quot; is a jury question.  It sounds like all of the underlying facts were undisputed such as the date/time the DMCA notices were sent and the date/time the content was removed.  What disputed issues of fact would the jury be asked to resolve?  None that I can see.  Because the facts were not disputed, it seems like the court should have resolved the remaining question as a matter of law -- the removal was either expeditious or it was not -- then let the losing party appeal.   If the timing of the takedown is always a question of fact, then the jury will be making up the law on an ad hoc basis.  That seems directly inconsistent with the intent of the DMCA.   Google must be quaking in its boots at this one -- they generally take weeks to consider DMCA notices I send them, and usually they&#039;re just ignored.]]></description>
			<content:encoded><![CDATA[<p>Wow &#8212; very scary ruling, but very relevant; thanks for posting.  It is baffling that the court would say whether or not Ustream acted &#8220;expeditiously&#8221; is a jury question.  It sounds like all of the underlying facts were undisputed such as the date/time the DMCA notices were sent and the date/time the content was removed.  What disputed issues of fact would the jury be asked to resolve?  None that I can see.  Because the facts were not disputed, it seems like the court should have resolved the remaining question as a matter of law &#8212; the removal was either expeditious or it was not &#8212; then let the losing party appeal.   If the timing of the takedown is always a question of fact, then the jury will be making up the law on an ad hoc basis.  That seems directly inconsistent with the intent of the DMCA.   Google must be quaking in its boots at this one &#8212; they generally take weeks to consider DMCA notices I send them, and usually they&#8217;re just ignored.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Rain, Rain		</title>
		<link>https://blog.ericgoldman.org/archives/2015/01/are-takedowns-in-48-hours-expeditious-enough-square-ring-v-ustream.htm#comment-1136</link>

		<dc:creator><![CDATA[Rain, Rain]]></dc:creator>
		<pubDate>Tue, 27 Jan 2015 18:14:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericgoldman.org/?p=13654#comment-1136</guid>

					<description><![CDATA[Two separate courts found that Veoh was eligible for safe harbor when it &quot;disable[d] access to the allegedly infringing videos, often the same day 
that Veoh receive[d] notice, or within a day or two of notice.&quot; UMG Recordings, Inc. v. Veoh Networks Inc., 665 F. Supp. 2d 1099, 1103 (C.D. Cal. 2009) (Matz, J.); Io Group, Inc. v. Veoh Networks, Inc., 586 F. Supp. 2d 1132 (N.D. Cal. 2008) (Lloyd, Mag. J.) (&quot;Veoh often responds to infringement notices the same day they are received, or at most, within a few days.&quot;)]]></description>
			<content:encoded><![CDATA[<p>Two separate courts found that Veoh was eligible for safe harbor when it &#8220;disable[d] access to the allegedly infringing videos, often the same day<br />
that Veoh receive[d] notice, or within a day or two of notice.&#8221; UMG Recordings, Inc. v. Veoh Networks Inc., 665 F. Supp. 2d 1099, 1103 (C.D. Cal. 2009) (Matz, J.); Io Group, Inc. v. Veoh Networks, Inc., 586 F. Supp. 2d 1132 (N.D. Cal. 2008) (Lloyd, Mag. J.) (&#8220;Veoh often responds to infringement notices the same day they are received, or at most, within a few days.&#8221;)</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
