<?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:gml="http://www.opengis.net/gml"
	>
<channel>
	<title>Comments on: Website Owners Not Liable for Comments</title>
	<atom:link href="http://raincityguide.com/2006/06/06/website-owners-not-liable-for-comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://raincityguide.com/2006/06/06/website-owners-not-liable-for-comments/</link>
	<description>Seattle&#039;s Leading Resource for Real Estate Information</description>
	<lastBuildDate>Sat, 20 Mar 2010 05:05:28 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: RealEstateCafe</title>
		<link>http://raincityguide.com/2006/06/06/website-owners-not-liable-for-comments/#comment-8391</link>
		<dc:creator>RealEstateCafe</dc:creator>
		<pubDate>Sat, 10 Jun 2006 01:06:11 +0000</pubDate>
		<guid isPermaLink="false">http://raincityguide.com/2006/06/06/website-owners-not-liable-for-comments/#comment-8391</guid>
		<description>Thanks for this extremely helpful discussion, Russ and Dustin.</description>
		<content:encoded><![CDATA[<p>Thanks for this extremely helpful discussion, Russ and Dustin.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Russ Cofano</title>
		<link>http://raincityguide.com/2006/06/06/website-owners-not-liable-for-comments/#comment-8268</link>
		<dc:creator>Russ Cofano</dc:creator>
		<pubDate>Wed, 07 Jun 2006 03:34:22 +0000</pubDate>
		<guid isPermaLink="false">http://raincityguide.com/2006/06/06/website-owners-not-liable-for-comments/#comment-8268</guid>
		<description>Back from lunch...had a Salmon Burger.  Yum!

Anyway, I agree with you Dustin that blog operators are generally not going to be liable for defamatory content posted by visitors to the blog. The basis of this immunization is the Communications Decency Act of 1996 which was enacted primarily to control the exposure of indecent material to minors.  

Some of the provisions in the CDA were enacted in response to the decision in Stratton Oakmont, Inc. v. Prodigy Services Co.  In this case, Prodigy was held liable for publishing defamatory statements on one of its online bulletin boards. The court determined that Prodigy should be responsible for the statements on its bulletin board because it monitored the information posted and occasionally removed offensive material. 

Congress was concerned that this standard of liability would deter web site operators from removing objectionable material posted by others that may be accessed by minors because the act of removing the material would subject the service provider to &quot;publisher&quot; liability.  Congress reasoned that making someone liable for trying to clean up the Internet was a bad road to go down.

At a high level, you should know that the CDA protects providers and users of &quot;interactive computer services&quot; from defamation liability arising out of information &quot;provided by another information content provider.&quot;   Do typical blogs qualify as an &quot;interactive computer service&quot;?  Yes.  The key limitation here, though, is that the protection applies only to information provided by another.

Let&#039;s say that I make a defamatory post about someone else on RCG.  Regardless of whether Dustin chooses to leave my post up or to remove it, he would have no liability for my defamatory statements even though he operates this blog.  He did not create the content and will not be deemed to have &quot;published&quot; it.

Now, let&#039;s say that Dustin partially edits some of my comments to make them more appropriate in his mind but leaving intact the substance of what I was trying to say.  Courts have held that this type of &quot;editorial&quot; control is generally not enough to make Dustin the publisher of my comments.  Again, no liability.

Now, let&#039;s say that Dustin copied my post and then added his substantive comments to it thereby creating &quot;new&quot; material.  In that case, it is possible that Dustin has crossed the line from being the &quot;provider&quot; of the blog to being the &quot;publisher&quot; of defamatory words.  As a result, Dustin would be liable as if he initially typed the words himself.

I suggest that bloggers adopt a stated policy on moderation.  Some bloggers may adopt a &quot;moderate every post&quot; policy while others may adopt a &quot;never moderate&quot; policy and others somewhere in the middle.  There is no &quot;right&quot; policy.  Whatever that policy is, stick to it and apply it consistently across the board.

Blogging is fun and can be a tremendous marketing medium.  It is not without peril if used without common sense.

-Russ</description>
		<content:encoded><![CDATA[<p>Back from lunch&#8230;had a Salmon Burger.  Yum!</p>
<p>Anyway, I agree with you Dustin that blog operators are generally not going to be liable for defamatory content posted by visitors to the blog. The basis of this immunization is the Communications Decency Act of 1996 which was enacted primarily to control the exposure of indecent material to minors.  </p>
<p>Some of the provisions in the CDA were enacted in response to the decision in Stratton Oakmont, Inc. v. Prodigy Services Co.  In this case, Prodigy was held liable for publishing defamatory statements on one of its online bulletin boards. The court determined that Prodigy should be responsible for the statements on its bulletin board because it monitored the information posted and occasionally removed offensive material. </p>
<p>Congress was concerned that this standard of liability would deter web site operators from removing objectionable material posted by others that may be accessed by minors because the act of removing the material would subject the service provider to &#8220;publisher&#8221; liability.  Congress reasoned that making someone liable for trying to clean up the Internet was a bad road to go down.</p>
<p>At a high level, you should know that the CDA protects providers and users of &#8220;interactive computer services&#8221; from defamation liability arising out of information &#8220;provided by another information content provider.&#8221;   Do typical blogs qualify as an &#8220;interactive computer service&#8221;?  Yes.  The key limitation here, though, is that the protection applies only to information provided by another.</p>
<p>Let&#8217;s say that I make a defamatory post about someone else on RCG.  Regardless of whether Dustin chooses to leave my post up or to remove it, he would have no liability for my defamatory statements even though he operates this blog.  He did not create the content and will not be deemed to have &#8220;published&#8221; it.</p>
<p>Now, let&#8217;s say that Dustin partially edits some of my comments to make them more appropriate in his mind but leaving intact the substance of what I was trying to say.  Courts have held that this type of &#8220;editorial&#8221; control is generally not enough to make Dustin the publisher of my comments.  Again, no liability.</p>
<p>Now, let&#8217;s say that Dustin copied my post and then added his substantive comments to it thereby creating &#8220;new&#8221; material.  In that case, it is possible that Dustin has crossed the line from being the &#8220;provider&#8221; of the blog to being the &#8220;publisher&#8221; of defamatory words.  As a result, Dustin would be liable as if he initially typed the words himself.</p>
<p>I suggest that bloggers adopt a stated policy on moderation.  Some bloggers may adopt a &#8220;moderate every post&#8221; policy while others may adopt a &#8220;never moderate&#8221; policy and others somewhere in the middle.  There is no &#8220;right&#8221; policy.  Whatever that policy is, stick to it and apply it consistently across the board.</p>
<p>Blogging is fun and can be a tremendous marketing medium.  It is not without peril if used without common sense.</p>
<p>-Russ</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Will Hicks</title>
		<link>http://raincityguide.com/2006/06/06/website-owners-not-liable-for-comments/#comment-8265</link>
		<dc:creator>Will Hicks</dc:creator>
		<pubDate>Tue, 06 Jun 2006 22:52:09 +0000</pubDate>
		<guid isPermaLink="false">http://raincityguide.com/2006/06/06/website-owners-not-liable-for-comments/#comment-8265</guid>
		<description>Thanks for the info. I had two people who got $300 conned out of them, slandering the local Coyote Ugly and an &quot;investor&quot; in their company. Turns out Coyote Ugly&#039;s never heard of the guy.</description>
		<content:encoded><![CDATA[<p>Thanks for the info. I had two people who got $300 conned out of them, slandering the local Coyote Ugly and an &#8220;investor&#8221; in their company. Turns out Coyote Ugly&#8217;s never heard of the guy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dustin</title>
		<link>http://raincityguide.com/2006/06/06/website-owners-not-liable-for-comments/#comment-8264</link>
		<dc:creator>Dustin</dc:creator>
		<pubDate>Tue, 06 Jun 2006 19:56:48 +0000</pubDate>
		<guid isPermaLink="false">http://raincityguide.com/2006/06/06/website-owners-not-liable-for-comments/#comment-8264</guid>
		<description>I was hoping you might jump in here, and give us the low-down.  I look forward to reading what you come up with!</description>
		<content:encoded><![CDATA[<p>I was hoping you might jump in here, and give us the low-down.  I look forward to reading what you come up with!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Russ Cofano</title>
		<link>http://raincityguide.com/2006/06/06/website-owners-not-liable-for-comments/#comment-8263</link>
		<dc:creator>Russ Cofano</dc:creator>
		<pubDate>Tue, 06 Jun 2006 18:37:54 +0000</pubDate>
		<guid isPermaLink="false">http://raincityguide.com/2006/06/06/website-owners-not-liable-for-comments/#comment-8263</guid>
		<description>Dustin

As with all things legal, there are usually few things that are black and white.  And so it goes with this issue.  I generally agree with the essence of your post but will later post a more in-depth analysis of the 9th Circuit case that was referenced (Batzel v. Smith) and what it means and doesn&#039;t mean.  Gotta go to lunch first....

-Russ</description>
		<content:encoded><![CDATA[<p>Dustin</p>
<p>As with all things legal, there are usually few things that are black and white.  And so it goes with this issue.  I generally agree with the essence of your post but will later post a more in-depth analysis of the 9th Circuit case that was referenced (Batzel v. Smith) and what it means and doesn&#8217;t mean.  Gotta go to lunch first&#8230;.</p>
<p>-Russ</p>
]]></content:encoded>
	</item>
</channel>
</rss>
