<?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: The Internet Rallies Against A Terrible Section 230 Ruling&#8211;Hassell v. Bird	</title>
	<atom:link href="https://blog.ericgoldman.org/archives/2016/08/hassell-v-bird.htm/feed" rel="self" type="application/rss+xml" />
	<link>https://blog.ericgoldman.org/archives/2016/08/hassell-v-bird.htm</link>
	<description></description>
	<lastBuildDate>Thu, 15 Jun 2017 16:23:00 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Ben Tate		</title>
		<link>https://blog.ericgoldman.org/archives/2016/08/hassell-v-bird.htm#comment-1871</link>

		<dc:creator><![CDATA[Ben Tate]]></dc:creator>
		<pubDate>Thu, 15 Jun 2017 16:23:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericgoldman.org/?p=16330#comment-1871</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://blog.ericgoldman.org/archives/2016/08/hassell-v-bird.htm#comment-1649&quot;&gt;Eric Goldman&lt;/a&gt;.

Oops. Yes. My bad (acknowledged 9 months after the fact.)]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://blog.ericgoldman.org/archives/2016/08/hassell-v-bird.htm#comment-1649">Eric Goldman</a>.</p>
<p>Oops. Yes. My bad (acknowledged 9 months after the fact.)</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Eric Goldman		</title>
		<link>https://blog.ericgoldman.org/archives/2016/08/hassell-v-bird.htm#comment-1649</link>

		<dc:creator><![CDATA[Eric Goldman]]></dc:creator>
		<pubDate>Fri, 02 Sep 2016 17:25:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericgoldman.org/?p=16330#comment-1649</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://blog.ericgoldman.org/archives/2016/08/hassell-v-bird.htm#comment-1648&quot;&gt;Ben Tate&lt;/a&gt;.

I believe you&#039;re referring to the Doe #14 v. Internet Brands case, not this one...?]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://blog.ericgoldman.org/archives/2016/08/hassell-v-bird.htm#comment-1648">Ben Tate</a>.</p>
<p>I believe you&#8217;re referring to the Doe #14 v. Internet Brands case, not this one&#8230;?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Ben Tate		</title>
		<link>https://blog.ericgoldman.org/archives/2016/08/hassell-v-bird.htm#comment-1648</link>

		<dc:creator><![CDATA[Ben Tate]]></dc:creator>
		<pubDate>Fri, 02 Sep 2016 16:08:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericgoldman.org/?p=16330#comment-1648</guid>

					<description><![CDATA[En banc review has been denied. Further requests will not be entertained. The appeal court has circled their wagons.]]></description>
			<content:encoded><![CDATA[<p>En banc review has been denied. Further requests will not be entertained. The appeal court has circled their wagons.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Major internet companies support Yelp in case that threatens online reviews		</title>
		<link>https://blog.ericgoldman.org/archives/2016/08/hassell-v-bird.htm#comment-1633</link>

		<dc:creator><![CDATA[Major internet companies support Yelp in case that threatens online reviews]]></dc:creator>
		<pubDate>Wed, 24 Aug 2016 15:13:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericgoldman.org/?p=16330#comment-1633</guid>

					<description><![CDATA[[&#8230;] are some relatively obscure legal-procedural issues in this case that are explained in depth by Eric Goldman. But here&#8217;s the simplified [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] are some relatively obscure legal-procedural issues in this case that are explained in depth by Eric Goldman. But here&#8217;s the simplified [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: David S. Gingras		</title>
		<link>https://blog.ericgoldman.org/archives/2016/08/hassell-v-bird.htm#comment-1632</link>

		<dc:creator><![CDATA[David S. Gingras]]></dc:creator>
		<pubDate>Tue, 23 Aug 2016 19:08:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericgoldman.org/?p=16330#comment-1632</guid>

					<description><![CDATA[Eric,

The initial draft of my letter actually went in a different direction with the &quot;provocative&quot; argument thing -- I pointed out that ROR&#039;s policy is basically the exact same thing as the policies used by virtually every court in this country; i.e., people can say almost anything in a pleading.  People can (and do) present claims in court they know are 100% false.  

Despite this, courts typically don&#039;t destroy their records or hide them from public view just because a claim has been proven false.  Rather, the only relief given to an aggrieved litigant is a final order/judgment which explains the outcome of the case.

ROR works in exactly the same way -- people can make any allegation in a report, and if that allegation is later proven to be false, ROR will post a copy of whatever document/order/judgment shows the outcome of the dispute. I see no material difference between that policy and the one employed by most courts. 

Also, most courts permanently maintain their records and often publish them online (indeed, the federal government even makes money by selling online access to records containing false information @ .10 cents a page!) Of course, the public is always free to publish statements contained in court records (as you often do), regardless of whether the statements are true or false.

So while it might be provocative, it seems inappropriate for courts to instruct website owners to: &quot;Do as I say, not as I do.&quot;

That isn&#039;t a legal argument, but it&#039;s still something to consider.]]></description>
			<content:encoded><![CDATA[<p>Eric,</p>
<p>The initial draft of my letter actually went in a different direction with the &#8220;provocative&#8221; argument thing &#8212; I pointed out that ROR&#8217;s policy is basically the exact same thing as the policies used by virtually every court in this country; i.e., people can say almost anything in a pleading.  People can (and do) present claims in court they know are 100% false.  </p>
<p>Despite this, courts typically don&#8217;t destroy their records or hide them from public view just because a claim has been proven false.  Rather, the only relief given to an aggrieved litigant is a final order/judgment which explains the outcome of the case.</p>
<p>ROR works in exactly the same way &#8212; people can make any allegation in a report, and if that allegation is later proven to be false, ROR will post a copy of whatever document/order/judgment shows the outcome of the dispute. I see no material difference between that policy and the one employed by most courts. </p>
<p>Also, most courts permanently maintain their records and often publish them online (indeed, the federal government even makes money by selling online access to records containing false information @ .10 cents a page!) Of course, the public is always free to publish statements contained in court records (as you often do), regardless of whether the statements are true or false.</p>
<p>So while it might be provocative, it seems inappropriate for courts to instruct website owners to: &#8220;Do as I say, not as I do.&#8221;</p>
<p>That isn&#8217;t a legal argument, but it&#8217;s still something to consider.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Ben Tate		</title>
		<link>https://blog.ericgoldman.org/archives/2016/08/hassell-v-bird.htm#comment-1630</link>

		<dc:creator><![CDATA[Ben Tate]]></dc:creator>
		<pubDate>Mon, 22 Aug 2016 20:21:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericgoldman.org/?p=16330#comment-1630</guid>

					<description><![CDATA[Nice compilation. Thank you for the effort.]]></description>
			<content:encoded><![CDATA[<p>Nice compilation. Thank you for the effort.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
