<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
>

<channel>
	<title>The Website and Blog of Joshua R. Kagan &#187; Internet</title>
	<atom:link href="http://joshkagan.com/tag/internet/feed/" rel="self" type="application/rss+xml" />
	<link>http://joshkagan.com</link>
	<description>Counsel for Technology, Entertainment, and Business</description>
	<lastBuildDate>Tue, 25 May 2010 22:59:30 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<!-- podcast_generator="podPress/8.8" - maintenance_release="8.8.4" -->
		<copyright>2008 </copyright>
		<managingEditor>contact@JoshKagan.com (The Website and Blog of Joshua R. Kagan)</managingEditor>
		<webMaster>contact@JoshKagan.com (The Website and Blog of Joshua R. Kagan)</webMaster>
		<category>posts</category>
		<ttl>1440</ttl>
<br />
<b>Warning</b>:  htmlentities() expects at most 3 parameters, 4 given in <b>/home/content/j/r/k/jrkagan/html/blog/wp-content/plugins/podpress/podpress_feed_functions.php</b> on line <b>31</b><br />
		<itunes:keywords></itunes:keywords>
<br />
<b>Warning</b>:  htmlentities() expects at most 3 parameters, 4 given in <b>/home/content/j/r/k/jrkagan/html/blog/wp-content/plugins/podpress/podpress_feed_functions.php</b> on line <b>31</b><br />
		<itunes:subtitle></itunes:subtitle>
<br />
<b>Warning</b>:  htmlentities() expects at most 3 parameters, 4 given in <b>/home/content/j/r/k/jrkagan/html/blog/wp-content/plugins/podpress/podpress_feed_functions.php</b> on line <b>31</b><br />
		<itunes:summary></itunes:summary>
		<itunes:author>The Website and Blog of Joshua R. Kagan</itunes:author>
		<itunes:category text="Society &amp; Culture"/>
		<itunes:owner>
			<itunes:name>The Website and Blog of Joshua R. Kagan</itunes:name>
			<itunes:email>contact@JoshKagan.com</itunes:email>
		</itunes:owner>
		<itunes:block>No</itunes:block>
		<itunes:explicit>no</itunes:explicit>
		<itunes:image href="http://singularitylaw.com/sing_white_big.jpg" />
		<image>
			<url>http://singularitylaw.com/sing_white_small.jpg</url>
			<title>The Website and Blog of Joshua R. Kagan</title>
			<link>http://joshkagan.com</link>
			<width>144</width>
			<height>144</height>
		</image>
		<item>
		<title>Briefly This Week</title>
		<link>http://joshkagan.com/2008/04/04/briefly-this-week/</link>
		<comments>http://joshkagan.com/2008/04/04/briefly-this-week/#comments</comments>
		<pubDate>Sat, 05 Apr 2008 05:01:09 +0000</pubDate>
		<dc:creator>Joshua Kagan</dc:creator>
				<category><![CDATA[Briefly]]></category>
		<category><![CDATA[Copyright in the Digital Age]]></category>
		<category><![CDATA[Secondary Liability Online]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[class-action]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Internet]]></category>
		<category><![CDATA[Perfect 10]]></category>
		<category><![CDATA[Section 230]]></category>

		<guid isPermaLink="false">http://joshkagan.com/blog/?p=10</guid>
		<description><![CDATA[Here&#8217;s a summary of the stories I&#8217;ve been following this week:

Elektra v. Barker and London-Sire v. Doe:  Can merely &#8220;making available&#8221; a file on a P2P network constitute copyright infringement, or does infringement require that a plaintiff prove that the file was actually downloaded by a third party?  Maybe not.  Coincidentally, I&#8217;m currently working on a [...]]]></description>
			<content:encoded><![CDATA[<p>Here&#8217;s a summary of the stories I&#8217;ve been following this week:</p>
<ul>
<li><em>Elektra v. Barker</em> and <em>London-Sire v. Doe</em>:  Can merely &#8220;<a href="http://www.eff.org/deeplinks/2008/04/making-available-distribution-says-court-london-sire-v-doe">making available</a>&#8221; a file on a P2P network constitute copyright infringement, or does infringement require that a plaintiff prove that the file was actually downloaded by a third party?  Maybe not.  Coincidentally, I&#8217;m currently working on a seminar paper on this very topic.</li>
<li><em>Fair Housing Council of San Fernando Valley v. Roommates.com, LLC.</em>:  Roommates.com was denied § 230 immunity by the Court of Appeals for the Ninth Circuit.  <a href="http://blog.ericgoldman.org/archives/2008/04/roommatescom_de_1.htm">Eric Goldman comments on his blog.<br />
</a></li>
<li><em>Perfect 10 v. Visa</em>:  This is a secondary liability suit in which a copyright owner unsuccessfully sought damages from a group of credit card companies that process transactions for infringers overseas.  On appeal, the plaintiff has now been joined with an amicus brief filed by the MPAA, RIAA, and others, as well as another amicus brief filed by the an organization that polices with counterfeit apparel and sneakers.  I&#8217;ll comment on this sometime soon once I&#8217;ve had an opportunity to read the briefs.</li>
<li>A class-action was settled by Apple last week after some consumers complained that the flat panel displays on their Apple notebook computers don&#8217;t display as many colors as they should, leading to inferior image quality.  This week, an identical suit was filed complaining that Apple&#8217;s &#8220;iMac&#8221; line of all-in-one desktop computers have the same problem.  Apple might settle again simply to avoid negative press, but the truth here is that all flat panel displays from all manufacturers have this issue.  No flat panel display can mimic every color that the human eye can see, so they all fake it using a technique called <a href="http://en.wikipedia.org/wiki/Dithering#Digital_photography_and_image_processing">dithering</a>.</li>
</ul>



Share:


	<a rel="nofollow"  href="http://digg.com/submit?phase=2&amp;url=http%3A%2F%2Fjoshkagan.com%2F2008%2F04%2F04%2Fbriefly-this-week%2F&amp;title=Briefly%20This%20Week&amp;bodytext=Here%27s%20a%20summary%20of%20the%20stories%20I%27ve%20been%20following%20this%20week%3A%0D%0A%0D%0A%09Elektra%20v.%20Barker%C2%A0and%20London-Sire%20v.%20Doe%3A%20%C2%A0Can%20merely%20%22making%20available%22%20a%20file%20on%20a%20P2P%20network%20constitute%20copyright%20infringement%2C%20or%20does%20infringement%20require%20that%20a%20plaintiff%20pro" title="Digg"><img src="http://joshkagan.com/blog/wp-content/plugins/sociable/images/digg.png" title="Digg" alt="Digg" class="sociable-hovers" /></a>
	<a rel="nofollow"  href="http://slashdot.org/bookmark.pl?title=Briefly%20This%20Week&amp;url=http%3A%2F%2Fjoshkagan.com%2F2008%2F04%2F04%2Fbriefly-this-week%2F" title="Slashdot"><img src="http://joshkagan.com/blog/wp-content/plugins/sociable/images/slashdot.png" title="Slashdot" alt="Slashdot" class="sociable-hovers" /></a>
	<a rel="nofollow"  href="http://delicious.com/post?url=http%3A%2F%2Fjoshkagan.com%2F2008%2F04%2F04%2Fbriefly-this-week%2F&amp;title=Briefly%20This%20Week&amp;notes=Here%27s%20a%20summary%20of%20the%20stories%20I%27ve%20been%20following%20this%20week%3A%0D%0A%0D%0A%09Elektra%20v.%20Barker%C2%A0and%20London-Sire%20v.%20Doe%3A%20%C2%A0Can%20merely%20%22making%20available%22%20a%20file%20on%20a%20P2P%20network%20constitute%20copyright%20infringement%2C%20or%20does%20infringement%20require%20that%20a%20plaintiff%20pro" title="del.icio.us"><img src="http://joshkagan.com/blog/wp-content/plugins/sociable/images/delicious.png" title="del.icio.us" alt="del.icio.us" class="sociable-hovers" /></a>
	<a rel="nofollow"  href="http://www.linkedin.com/shareArticle?mini=true&amp;url=http%3A%2F%2Fjoshkagan.com%2F2008%2F04%2F04%2Fbriefly-this-week%2F&amp;title=Briefly%20This%20Week&amp;source=The+Website+and+Blog+of+Joshua+R.+Kagan+Counsel+for+Technology%2C+Entertainment%2C+and+Business&amp;summary=Here%27s%20a%20summary%20of%20the%20stories%20I%27ve%20been%20following%20this%20week%3A%0D%0A%0D%0A%09Elektra%20v.%20Barker%C2%A0and%20London-Sire%20v.%20Doe%3A%20%C2%A0Can%20merely%20%22making%20available%22%20a%20file%20on%20a%20P2P%20network%20constitute%20copyright%20infringement%2C%20or%20does%20infringement%20require%20that%20a%20plaintiff%20pro" title="LinkedIn"><img src="http://joshkagan.com/blog/wp-content/plugins/sociable/images/linkedin.png" title="LinkedIn" alt="LinkedIn" class="sociable-hovers" /></a>
	<a rel="nofollow"  href="http://www.facebook.com/share.php?u=http%3A%2F%2Fjoshkagan.com%2F2008%2F04%2F04%2Fbriefly-this-week%2F&amp;t=Briefly%20This%20Week" title="Facebook"><img src="http://joshkagan.com/blog/wp-content/plugins/sociable/images/facebook.png" title="Facebook" alt="Facebook" class="sociable-hovers" /></a>
	<a rel="nofollow"  href="http://twitter.com/home?status=Briefly%20This%20Week%20-%20http%3A%2F%2Fjoshkagan.com%2F2008%2F04%2F04%2Fbriefly-this-week%2F" title="Twitter"><img src="http://joshkagan.com/blog/wp-content/plugins/sociable/images/twitter.png" title="Twitter" alt="Twitter" class="sociable-hovers" /></a>


<br/><br/>]]></content:encoded>
			<wfw:commentRss>http://joshkagan.com/2008/04/04/briefly-this-week/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>T-Mobile Claims to Own the Color Magenta</title>
		<link>http://joshkagan.com/2008/03/31/t-mobile-claims-to-own-the-color-magenta/</link>
		<comments>http://joshkagan.com/2008/03/31/t-mobile-claims-to-own-the-color-magenta/#comments</comments>
		<pubDate>Tue, 01 Apr 2008 00:13:59 +0000</pubDate>
		<dc:creator>Joshua Kagan</dc:creator>
				<category><![CDATA[Trademarks and Brands]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[Internet]]></category>
		<category><![CDATA[trademark dilution]]></category>

		<guid isPermaLink="false">http://joshkagan.com/blog/?p=7</guid>
		<description><![CDATA[The writers of Engadget Mobile, a technology weblog that reports on wireless phones and carriers, reported today that they have received a letter from Deutsche Telekom, the parent company of T-Mobile.  In the letter, attorneys for Deutche Telekom ask that Engadget stop using the color magenta in the blog&#8217;s logo and headings because it threatens [...]]]></description>
			<content:encoded><![CDATA[<p>The writers of Engadget Mobile, a technology weblog that reports on wireless phones and carriers, <a href="http://www.engadget.com/2008/03/31/deutsche-telekom-t-mobile-demands-engadget-mobile-discontinue/">reported today that they have received a letter from Deutsche Telekom</a>, the parent company of T-Mobile.  In the letter, attorneys for Deutche Telekom ask that Engadget stop using the color magenta in the blog&#8217;s logo and headings because it threatens to dilute Deutche Telekom&#8217;s trademark.</p>
<p>Trademark law is intended to protect the public from confusion in the marketplace while protecting merchants who have spent time, energy, and money in presenting a product to the public.  A typical action for trademark infringement would require that there be some competition between the owner of the mark (here Deutche Telekom) and the using party, and&#8211;most importantly&#8211;some likelihood of confusion, mistake, or deception of consumers.  But here, T-Mobile and the Engadget blogs are not in competition with one another.  Each company provides very different products and services.  There&#8217;s also virtually no chance that a consumer could ever be confused about whether an Engadget blog was a service of T-Mobile, or vice versa.  Trademark infringement protects a trademark owner from having his or her mark used in connection with competing goods and services.  It does not, however, prohibit another from using that mark in connection with non-competing goods and services.  So long as the trademark is used in connection with goods and services that do not compete with the goods and services of the trademark owner, the trademark has not been infringed.  But Deutche Telekom is not claiming &#8220;infringement&#8221; here; they&#8217;re claiming &#8220;dilution.&#8221;  &#8221;Dilution&#8221; under the U.S. Federal Trademark Dilution Act is a separate action that is available to provide protection even absent infringement, in response to trademark blurring and tarnishment of famous marks.</p>
<p><a href="http://joshkagan.com/blog/wp-content/uploads/2008/03/t-mobile-vs-engadget-mobile.png"><img class="alignright alignnone size-medium wp-image-8" style="float: right;" title="t-mobile-vs-engadget-mobile" src="http://joshkagan.com/blog/wp-content/uploads/2008/03/t-mobile-vs-engadget-mobile-300x178.png" alt="T-Mobile Logo vs. Engadget Mobile Logo" width="300" height="178" /></a>Let&#8217;s assume that the T-Mobile mark is sufficiently famous to qualify for protection under the Trademark Dilution Act.  To maintain a cause of action for trademark dilution, Deutche Telekom would need to show that Engadget Mobile&#8217;s use of the color magenta blurs the distinctiveness or tarnishes the trademark it holds.  The logo of the T-Mobile brand includes a solid magenta &#8220;T&#8221; with three horizontal gray squares; the logo of the Engadget Mobile blog includes the word &#8220;mobile&#8221; in graded magenta with three magenta rectangles in a vertical line that have been styled to mimic the signal bars on a wireless phone&#8217;s display.  &#8221;Blurring,&#8221; the most basic kind of dilution, occurs when the use of a mark is &#8220;blurred&#8221; from association with only one market (here cellular phone services) to signify other products in other markets (here a weblog about mobile phones).  In <em>Toys R Us v. Feinberg</em>, the U.S. District Court for the Southern District of New York clarified that &#8220;blurring&#8221; occurs when a use of a mark lessens the capacity of a trademark owner&#8217;s identify and distinguish their goods or services.  26 F. Supp. 2d 639, 644.  Ergo, the obvious question here is whether the use of the color magenta in a blog about mobile phones would cause any &#8220;blurring&#8221; of T-Mobile&#8217;s mark.  Setting aside any feelings we might have about T-Mobile effectively claiming ownership over a color, does Engadget&#8217;s use of that color as an accent on its weblog affect the effectiveness of the magenta accent in T-Mobile&#8217;s branding?</p>
<p>Probably not.  The weblog&#8217;s use of magenta is not solid and pervasive like T-Mobile&#8217;s.  On my notebook computer&#8217;s display, it&#8217;s not even the same shade of magenta.  It is merely a one-off use of magenta in a logo.  Deutche Telekom might have a case if the Engadget Mobile weblog used design elements like gray squares in horizontal lines, or used magenta pervasively in the same way that T-Mobile&#8217;s materials use it, but the use of a similar shade of magenta probably would not be enough because it does not lessen the &#8220;punch&#8221; that T-Mobile&#8217;s magenta branding has on its website, stores, and marketing materials.  Under the controlling authority of <em>Toys R Us</em> and other dilution cases, a court would probably not allow Deutche Telekom to limit the ability of a non-competing website to use the color magenta in a way that does not mimic T-Mobile&#8217;s use of the color as a pervasive accent throughout its branding.</p>
<p><em>Disclaimer: This weblog is an informational resource only. It is not designed to offer legal advice.</em></p>



Share:


	<a rel="nofollow"  href="http://digg.com/submit?phase=2&amp;url=http%3A%2F%2Fjoshkagan.com%2F2008%2F03%2F31%2Ft-mobile-claims-to-own-the-color-magenta%2F&amp;title=T-Mobile%20Claims%20to%20Own%20the%20Color%20Magenta&amp;bodytext=The%20writers%20of%20Engadget%20Mobile%2C%20a%20technology%20weblog%20that%20reports%20on%20wireless%20phones%20and%20carriers%2C%20reported%20today%20that%20they%20have%20received%20a%20letter%20from%20Deutsche%20Telekom%2C%20the%20parent%20company%20of%20T-Mobile.%20%C2%A0In%20the%20letter%2C%20attorneys%20for%20Deutche%20Telekom%20as" title="Digg"><img src="http://joshkagan.com/blog/wp-content/plugins/sociable/images/digg.png" title="Digg" alt="Digg" class="sociable-hovers" /></a>
	<a rel="nofollow"  href="http://slashdot.org/bookmark.pl?title=T-Mobile%20Claims%20to%20Own%20the%20Color%20Magenta&amp;url=http%3A%2F%2Fjoshkagan.com%2F2008%2F03%2F31%2Ft-mobile-claims-to-own-the-color-magenta%2F" title="Slashdot"><img src="http://joshkagan.com/blog/wp-content/plugins/sociable/images/slashdot.png" title="Slashdot" alt="Slashdot" class="sociable-hovers" /></a>
	<a rel="nofollow"  href="http://delicious.com/post?url=http%3A%2F%2Fjoshkagan.com%2F2008%2F03%2F31%2Ft-mobile-claims-to-own-the-color-magenta%2F&amp;title=T-Mobile%20Claims%20to%20Own%20the%20Color%20Magenta&amp;notes=The%20writers%20of%20Engadget%20Mobile%2C%20a%20technology%20weblog%20that%20reports%20on%20wireless%20phones%20and%20carriers%2C%20reported%20today%20that%20they%20have%20received%20a%20letter%20from%20Deutsche%20Telekom%2C%20the%20parent%20company%20of%20T-Mobile.%20%C2%A0In%20the%20letter%2C%20attorneys%20for%20Deutche%20Telekom%20as" title="del.icio.us"><img src="http://joshkagan.com/blog/wp-content/plugins/sociable/images/delicious.png" title="del.icio.us" alt="del.icio.us" class="sociable-hovers" /></a>
	<a rel="nofollow"  href="http://www.linkedin.com/shareArticle?mini=true&amp;url=http%3A%2F%2Fjoshkagan.com%2F2008%2F03%2F31%2Ft-mobile-claims-to-own-the-color-magenta%2F&amp;title=T-Mobile%20Claims%20to%20Own%20the%20Color%20Magenta&amp;source=The+Website+and+Blog+of+Joshua+R.+Kagan+Counsel+for+Technology%2C+Entertainment%2C+and+Business&amp;summary=The%20writers%20of%20Engadget%20Mobile%2C%20a%20technology%20weblog%20that%20reports%20on%20wireless%20phones%20and%20carriers%2C%20reported%20today%20that%20they%20have%20received%20a%20letter%20from%20Deutsche%20Telekom%2C%20the%20parent%20company%20of%20T-Mobile.%20%C2%A0In%20the%20letter%2C%20attorneys%20for%20Deutche%20Telekom%20as" title="LinkedIn"><img src="http://joshkagan.com/blog/wp-content/plugins/sociable/images/linkedin.png" title="LinkedIn" alt="LinkedIn" class="sociable-hovers" /></a>
	<a rel="nofollow"  href="http://www.facebook.com/share.php?u=http%3A%2F%2Fjoshkagan.com%2F2008%2F03%2F31%2Ft-mobile-claims-to-own-the-color-magenta%2F&amp;t=T-Mobile%20Claims%20to%20Own%20the%20Color%20Magenta" title="Facebook"><img src="http://joshkagan.com/blog/wp-content/plugins/sociable/images/facebook.png" title="Facebook" alt="Facebook" class="sociable-hovers" /></a>
	<a rel="nofollow"  href="http://twitter.com/home?status=T-Mobile%20Claims%20to%20Own%20the%20Color%20Magenta%20-%20http%3A%2F%2Fjoshkagan.com%2F2008%2F03%2F31%2Ft-mobile-claims-to-own-the-color-magenta%2F" title="Twitter"><img src="http://joshkagan.com/blog/wp-content/plugins/sociable/images/twitter.png" title="Twitter" alt="Twitter" class="sociable-hovers" /></a>


<br/><br/>]]></content:encoded>
			<wfw:commentRss>http://joshkagan.com/2008/03/31/t-mobile-claims-to-own-the-color-magenta/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>JuicyCampus and the Limits of Section 230</title>
		<link>http://joshkagan.com/2008/03/25/juicycampus-and-the-limits-of-section-230/</link>
		<comments>http://joshkagan.com/2008/03/25/juicycampus-and-the-limits-of-section-230/#comments</comments>
		<pubDate>Wed, 26 Mar 2008 01:41:15 +0000</pubDate>
		<dc:creator>Joshua Kagan</dc:creator>
				<category><![CDATA[Defamation Online]]></category>
		<category><![CDATA[Secondary Liability Online]]></category>
		<category><![CDATA[Internet]]></category>
		<category><![CDATA[Section 230]]></category>

		<guid isPermaLink="false">http://joshkagan.com/blog/?p=6</guid>
		<description><![CDATA[JuicyCampus is an Internet forum that encourages visitors to post gossip and rumors relating to people at any of a number of colleges and universities in the U.S. (currently 59).  The operators of the website purport to offer complete anonymity to posters by way of IP address masking and other policies; they claim that [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.juicycampus.com/">JuicyCampus</a> is an Internet forum that encourages visitors to post gossip and rumors relating to people at any of a number of colleges and universities in the U.S. (currently 59).  The operators of the website purport to offer complete anonymity to posters by way of IP address masking and other policies; they claim that this fosters free speech that otherwise could not be possible.  The website has been in service since sometime in August 2007.  In the short period of time that has passed since then, it has already become a target of controversy because of its potential for anonymously spreading objectionable content like hate speech, libel, and privacy invasions.  I have been periodically checking the website&#8217;s home page since I first learned of it two days ago; since then I have read front-page posts that purport to challenge particular students&#8217; sexualities (typically called out by the targets&#8217; full names), defend anti-Semitic viewpoints, and much more.</p>
<p>The most obvious potential for litigation against JuicyCampus, aside from the largely meritless consumer fraud action brewing against them in New Jersey, is a suit for libel by a hypothetical student who claims s/he has been defamed by something posted by a visitor to the website.  Defamation is the communication of a false statement of fact that may harm the reputation of an individual.  Courts have held that the posting of a defamatory statement to an Internet website is libel, the strongest form of defamation which is characterized by having the harmful statement published in a fixed medium.  Section 230(c)(1) of the Communications Decency Act of 1996 provides immunity from certain kinds of civil liability, including defamation, for &#8220;providers of interactive computer services&#8221; who publish information provided by others.  &#8220;Interactive computer services&#8221; includes website operators such as the operators of JuicyCampus.  The relevant caselaw suggests that even when a website operator does not take steps to police content on his/her site, s/he will not be liable as a publisher for statements posted to the site by third-party visitors.  The law instead views the website operator as more akin to an owner of a newsstand, distributing content written by others and not directly responsible for that content.</p>
<p>Section 230, a law that took effect in 1996, was inspired in part by <em>Stratton Oakmont, Inc. v. Prodigy Services Co.</em>, a 1995 case in the New York State Supreme Court, in which a controversial opinion held that the defendant (an ISP and forum operator) could in fact be treated as the publisher of third-party postings to its Internet forum because it had an ability to police and delete messages that it found to be offensive.  Service providers feared that the <em>Stratton Oakmont</em> decision would force them into one of two extreme positions, both of which were likely to cause backlash from users and would threaten the development of the Internet.  On the one hand, service providers could opt to police Internet forums vigorously, filtering messages and aggressively deleting objectionable content to limit their liability.  On the other hand, service providers could opt to shut their eyes entirely, refraining from moderating any posts whatsoever such that they could argue that they did not exercise any editorial control over the forum.  With § 230, Congress gave service providers the safe harbor they required to build services like Internet forums free from fears of liability over content contributed by others.  Section 230 also allowed for the proliferation of other Internet phenomena such as blogging, social networking, and content sharing.  For example, could you imagine the burden that would be imposed on the authors of popular blogs if they were forced to moderate and research the accuracy of each and every comment that third parties post?  In a world without § 230, it is likely that most popular bloggers would have preferred to disallow commenting entirely in order to avoid the burdens associated with it.</p>
<p>But JuicyCampus is not a blog.  It is also not a typical Internet forum.  There are at least two good reasons for this.</p>
<p>First, on most Internet websites that allow third-party contributions, users are required to identify themselves in some way.  For example, if you choose to comment to this post on my blog, you are asked to provide an email address and choose a name.  The name you choose may not be the name you use in real life, but it is designed to identify you in the discussion of comments that follows this post.  This creates accountability in that your reputation&#8211;as pseudonymous as it may be&#8211;is attached to each comment you post.  In contrast, JuicyCampus seems to make no such attributions.  When a user writes a post on JuicyCampus, s/he has no incentive to warrant the accuracy or objectivity of the post.  The website is entirely anonymous, which promotes a platform for posters who wish to recklessly disregard the truth, or worse.</p>
<p>Secondly, most Internet websites that allow third-party contributions keep certain logs about users that contribute content.  For example, if you decide to leave a comment on this post as described above, the server that hosts this blog will also make note of your computer&#8217;s IP address, which is an identifier that could in most cases be used to accurately determine your identity if necessary.  In the event that a plaintiff decides to bring an action against me as the publisher of information that you posted, I would be able to (and a court would probably order me to) provide the plaintiff with that information, helping the plaintiff to find the true publisher of the objectionable content.  Ergo, although the plaintiff will not be successful in an action against me as publisher, the plaintiff might still have a cause of action against the third-party poster.  In the case of this blog, that plaintiff still has a way to recover for his/her damages.  But the same would not be true for an equivalent plaintiff bringing an action against JuicyCampus.  Under the current body of caselaw associated with § 230, that plaintiff&#8217;s action against JuicyCampus would likely fail because the court would find that JuicyCampus is a mere distributor, and the plaintiff would probably not be able to ascertain the identity of third-party poster who is the proper defendant.</p>
<p>The operators of JuicyCampus would likely argue that their website is analogous to a big open area where anyone can speak without identifying himself.  But, in the real world, even when people speak anonymously to strangers in an open area, they reveal certain aspects about themselves to that group, such as their voice and face.  Internet posts often contain no such identifying characteristics.  The consequences of this are clear:  some victims of online torts may be left with absolutely no way to recover where the third-party poster&#8211;unquestionably the true tortfeasor&#8211;cannot be identified due to the anonymity policies of forums like JuicyCampus.</p>
<p>I&#8217;m not yet sure of the best solution to this problem.  Should websites like JuicyCampus be prohibited from providing such complete anonymity to posters?  Or, should they be required to give up some of their § 230 immunity in exchange for providing such anonymity?  Or, can we as a society simply find it acceptable that, in this new age of technology, some plaintiffs simply will not be able to recover for their damages because of the anonymity required to allow free speech on sites like JuicyCampus?</p>
<p><em>Disclaimer: This weblog is an informational resource only. It is not designed to offer legal advice.</em></p>



Share:


	<a rel="nofollow"  href="http://digg.com/submit?phase=2&amp;url=http%3A%2F%2Fjoshkagan.com%2F2008%2F03%2F25%2Fjuicycampus-and-the-limits-of-section-230%2F&amp;title=JuicyCampus%20and%20the%20Limits%20of%20Section%20230&amp;bodytext=JuicyCampus%20is%20an%20Internet%20forum%20that%20encourages%20visitors%20to%20post%20gossip%20and%20rumors%20relating%20to%20people%20at%20any%20of%20a%20number%20of%20colleges%20and%20universities%20in%20the%20U.S.%20%28currently%2059%29.%20%20The%20operators%20of%20the%20website%20purport%20to%20offer%20complete%20anonymity%20to%20po" title="Digg"><img src="http://joshkagan.com/blog/wp-content/plugins/sociable/images/digg.png" title="Digg" alt="Digg" class="sociable-hovers" /></a>
	<a rel="nofollow"  href="http://slashdot.org/bookmark.pl?title=JuicyCampus%20and%20the%20Limits%20of%20Section%20230&amp;url=http%3A%2F%2Fjoshkagan.com%2F2008%2F03%2F25%2Fjuicycampus-and-the-limits-of-section-230%2F" title="Slashdot"><img src="http://joshkagan.com/blog/wp-content/plugins/sociable/images/slashdot.png" title="Slashdot" alt="Slashdot" class="sociable-hovers" /></a>
	<a rel="nofollow"  href="http://delicious.com/post?url=http%3A%2F%2Fjoshkagan.com%2F2008%2F03%2F25%2Fjuicycampus-and-the-limits-of-section-230%2F&amp;title=JuicyCampus%20and%20the%20Limits%20of%20Section%20230&amp;notes=JuicyCampus%20is%20an%20Internet%20forum%20that%20encourages%20visitors%20to%20post%20gossip%20and%20rumors%20relating%20to%20people%20at%20any%20of%20a%20number%20of%20colleges%20and%20universities%20in%20the%20U.S.%20%28currently%2059%29.%20%20The%20operators%20of%20the%20website%20purport%20to%20offer%20complete%20anonymity%20to%20po" title="del.icio.us"><img src="http://joshkagan.com/blog/wp-content/plugins/sociable/images/delicious.png" title="del.icio.us" alt="del.icio.us" class="sociable-hovers" /></a>
	<a rel="nofollow"  href="http://www.linkedin.com/shareArticle?mini=true&amp;url=http%3A%2F%2Fjoshkagan.com%2F2008%2F03%2F25%2Fjuicycampus-and-the-limits-of-section-230%2F&amp;title=JuicyCampus%20and%20the%20Limits%20of%20Section%20230&amp;source=The+Website+and+Blog+of+Joshua+R.+Kagan+Counsel+for+Technology%2C+Entertainment%2C+and+Business&amp;summary=JuicyCampus%20is%20an%20Internet%20forum%20that%20encourages%20visitors%20to%20post%20gossip%20and%20rumors%20relating%20to%20people%20at%20any%20of%20a%20number%20of%20colleges%20and%20universities%20in%20the%20U.S.%20%28currently%2059%29.%20%20The%20operators%20of%20the%20website%20purport%20to%20offer%20complete%20anonymity%20to%20po" title="LinkedIn"><img src="http://joshkagan.com/blog/wp-content/plugins/sociable/images/linkedin.png" title="LinkedIn" alt="LinkedIn" class="sociable-hovers" /></a>
	<a rel="nofollow"  href="http://www.facebook.com/share.php?u=http%3A%2F%2Fjoshkagan.com%2F2008%2F03%2F25%2Fjuicycampus-and-the-limits-of-section-230%2F&amp;t=JuicyCampus%20and%20the%20Limits%20of%20Section%20230" title="Facebook"><img src="http://joshkagan.com/blog/wp-content/plugins/sociable/images/facebook.png" title="Facebook" alt="Facebook" class="sociable-hovers" /></a>
	<a rel="nofollow"  href="http://twitter.com/home?status=JuicyCampus%20and%20the%20Limits%20of%20Section%20230%20-%20http%3A%2F%2Fjoshkagan.com%2F2008%2F03%2F25%2Fjuicycampus-and-the-limits-of-section-230%2F" title="Twitter"><img src="http://joshkagan.com/blog/wp-content/plugins/sociable/images/twitter.png" title="Twitter" alt="Twitter" class="sociable-hovers" /></a>


<br/><br/>]]></content:encoded>
			<wfw:commentRss>http://joshkagan.com/2008/03/25/juicycampus-and-the-limits-of-section-230/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
