<?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:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
>

<channel>
	<title>Info/Law &#187; Privacy</title>
	<atom:link href="http://blogs.law.harvard.edu/infolaw/category/privacy/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.law.harvard.edu/infolaw</link>
	<description>Information, Law, and the Law of Information</description>
	<lastBuildDate>Sun, 15 Nov 2009 16:52:30 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
		<item>
		<title>Defining Network Neutrality</title>
		<link>http://blogs.law.harvard.edu/infolaw/2009/10/26/defining-network-neutrality/</link>
		<comments>http://blogs.law.harvard.edu/infolaw/2009/10/26/defining-network-neutrality/#comments</comments>
		<pubDate>Mon, 26 Oct 2009 23:01:24 +0000</pubDate>
		<dc:creator>Derek Bambauer</dc:creator>
				<category><![CDATA[Digital Media]]></category>
		<category><![CDATA[Filtering]]></category>
		<category><![CDATA[ISP]]></category>
		<category><![CDATA[Intermediaries]]></category>
		<category><![CDATA[Internet & Society]]></category>
		<category><![CDATA[Network Neutrality]]></category>
		<category><![CDATA[Privacy]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[Spam]]></category>
		<category><![CDATA[VoIP]]></category>
		<category><![CDATA[badware]]></category>

		<guid isPermaLink="false">http://blogs.law.harvard.edu/infolaw/?p=837</guid>
		<description><![CDATA[The net neutrality fight is on, as FCC Chairman Julius Genachowski&#8217;s proposal for new rules moved on to a Notice of Proposed Rulemaking. Now, the two sides are digging in: AT&#38;T, telcos, and unions on one side; Google and content providers on the other.
I tend to favor protecting end-to-end in the Internet context, but I&#8217;m [...]]]></description>
			<content:encoded><![CDATA[<p>The net neutrality fight is on, as FCC Chairman Julius Genachowski&#8217;s proposal for new rules moved on to a <a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-294159A1.pdf" target="_blank">Notice of Proposed Rulemaking</a>. Now, the <a href="http://online.wsj.com/article/SB10001424052748704224004574489323364051390.html" target="_blank">two sides are digging in</a>: AT&amp;T, telcos, and unions on one side; Google and content providers on the other.</p>
<p>I tend to favor protecting <a href="http://portal.acm.org/citation.cfm?id=357402" target="_blank">end-to-end</a> in the Internet context, but I&#8217;m a bit worried about what the net neutrality rules will look like in practice. There are two ways to think of this problem. First, who is the target of regulatory action? The FCC&#8217;s rules seem to look at the CEO or CTO of an ISP or telecom company. I think the correct focus is farther down the corporate ladder: the IT folks who have to implement rules on their routers. The new rules seem fine as policy statements, but how do they translate into what you can and can&#8217;t do with bits?</p>
<p>Second, what existing practices are covered by the net neutrality rules? I worry there are some laudable practices that might run afoul of the rules &#8211; even if it&#8217;s unlikely the FCC would seek enforcement against them. (Safety that depends on agency discretion is not particularly comforting.) Here&#8217;s a fast list of practices that might violate net neutrality right now:<span id="more-837"></span></p>
<ul>
<li><strong>Port blocking</strong> &#8211; can ISPs prevent you from sending e-mail except through their servers by blocking port 25? Many, <a href="http://www22.verizon.com/ResidentialHelp/HighSpeed/General+Support/Top+Questions/QuestionsOne/124274.htm" target="_blank">including Verizon</a>, already do. (See Rule 2 in the <a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-294159A1.pdf" target="_blank">Press Release</a>.)</li>
<li><strong>Network Address Translation</strong> &#8211; <a href="http://www.howstuffworks.com/nat.htm" target="_blank">NAT</a> rewrites IP addresses to ensure that packets reach their destination. Does altering header information violate the rules? (Rule 6 at least, maybe Rule 4.)</li>
<li><strong>Spam filtering</strong> &#8211; ISPs routinely drop connections, or quarantine messages, from known spammers and spam-friendly destinations. (Rules 1, 4.)</li>
<li><a href="http://en.wikipedia.org/wiki/Voice_over_Internet_Protocol#Quality_of_Service" target="_blank"><strong>VoIP routing</strong></a> &#8211; some telcos route their own VoIP traffic across their network rather than the public Internet, which is more efficient (assuming both ends of the conversation have the same provider). That&#8217;s almost certainly out. (Rule 5.)</li>
<li><strong>Virus prevention</strong> &#8211; some educational institutions <a href="http://www.mac.edu/resources/it_access.asp" target="_blank">scan</a> connecting devices for Trojans / viruses / malware, or software that protects against them, and condition network access on passing this scan. (Rule 3, though doubtless the FCC would use the &#8220;harm&#8221; criterion as a dodge.)</li>
</ul>
<p>So, I&#8217;m worried about how the FCC&#8217;s legal rules are implemented in code. I think we need a lot more guidance from the agency, particularly since net neutrality still feels somewhat like a solution in search of a problem&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.law.harvard.edu/infolaw/2009/10/26/defining-network-neutrality/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
	<creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
	</item>
		<item>
		<title>Rafal Rohozinski on Internet Surveillance and Monitoring</title>
		<link>http://blogs.law.harvard.edu/infolaw/2009/10/09/rafal-rohozinski-on-internet-surveillance-and-monitoring/</link>
		<comments>http://blogs.law.harvard.edu/infolaw/2009/10/09/rafal-rohozinski-on-internet-surveillance-and-monitoring/#comments</comments>
		<pubDate>Fri, 09 Oct 2009 21:15:31 +0000</pubDate>
		<dc:creator>Derek Bambauer</dc:creator>
				<category><![CDATA[Berkman]]></category>
		<category><![CDATA[Digital Media]]></category>
		<category><![CDATA[Filtering]]></category>
		<category><![CDATA[Intermediaries]]></category>
		<category><![CDATA[Internet & Society]]></category>
		<category><![CDATA[Media]]></category>
		<category><![CDATA[NSA]]></category>
		<category><![CDATA[Privacy]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[badware]]></category>
		<category><![CDATA[international]]></category>
		<category><![CDATA[national security]]></category>

		<guid isPermaLink="false">http://blogs.law.harvard.edu/infolaw/?p=827</guid>
		<description><![CDATA[My former ONI colleague Rafal Rohozinski, now of Information Warfare Monitor, has a great interview where he discusses methodology and findings for both projects. Well worth a read!
]]></description>
			<content:encoded><![CDATA[<p>My former <a href="http://opennet.net/" target="_blank">ONI</a> colleague Rafal Rohozinski, now of <a href="http://www.infowar-monitor.net/" target="_blank">Information Warfare Monitor</a>, has a <a href="http://www.net-security.org/article.php?id=1314" target="_blank">great interview where he discusses methodology and findings for both projects</a>. Well worth a read!</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.law.harvard.edu/infolaw/2009/10/09/rafal-rohozinski-on-internet-surveillance-and-monitoring/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	<creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
	</item>
		<item>
		<title>Social Marketing Article Published</title>
		<link>http://blogs.law.harvard.edu/infolaw/2009/09/03/soc-mktg-published/</link>
		<comments>http://blogs.law.harvard.edu/infolaw/2009/09/03/soc-mktg-published/#comments</comments>
		<pubDate>Thu, 03 Sep 2009 21:43:57 +0000</pubDate>
		<dc:creator>William McGeveran</dc:creator>
				<category><![CDATA[Blogging]]></category>
		<category><![CDATA[Digital Media]]></category>
		<category><![CDATA[Intermediaries]]></category>
		<category><![CDATA[Internet & Society]]></category>
		<category><![CDATA[Peer Production]]></category>
		<category><![CDATA[Privacy]]></category>
		<category><![CDATA[Scholarship]]></category>
		<category><![CDATA[Social Networking]]></category>
		<category><![CDATA[Trademarks]]></category>

		<guid isPermaLink="false">http://blogs.law.harvard.edu/infolaw/?p=788</guid>
		<description><![CDATA[From blog post to journal article! I am pleased to report that the new issue of the University of Illinois Law Review includes my article, Disclosure, Endorsement, and Identity in Social Marketing. The ideas for the article began in posts on this blog, starting here and continuing here.
Here&#8217;s the full abstract of the new article:

Social [...]]]></description>
			<content:encoded><![CDATA[<p>From blog post to journal article! I am pleased to report that the new issue of the <em><a href="http://home.law.uiuc.edu/lrev/index.html">University of Illinois Law Review</a></em> includes my article, <em><a href="http://home.law.uiuc.edu/lrev/publications/2000s/2009/2009_4/McGeveran.pdf">Disclosure, Endorsement, and Identity in Social Marketing</a></em>. The ideas for the article began in posts on this blog, starting <a href="http://blogs.law.harvard.edu/infolaw/2007/11/08/facebook-social-ads/">here</a> and continuing <a href="http://blogs.law.harvard.edu/infolaw/2007/11/09/more-thoughts-on-facebooks-social-ads/">here</a>.</p>
<p>Here&#8217;s the full abstract of the new article:</p>
<blockquote><p>
Social marketing is among the newest advertising trends now emerging on the internet. Using online social networks such as Facebook or MySpace, marketers could send personalized promotional messages featuring an ordinary customer to that customer’s friends.  Because they reveal a customer’s browsing and buying patterns, and because they feature implied endorsements, the messages raise significant concerns about disclosure of personal matters, information quality, and individuals’ ability to control the commercial exploitation of their identity. Yet social marketing falls through the cracks between several different legal paradigms that might allow its regulation—spanning from privacy to trademark and unfair competition to consumer protection to the appropriation tort and rights of publicity.</p>
<p>This Article examines potential concerns with social marketing and the various legal responses available. It demonstrates that none of the existing legal paradigms, which all evolved in response to particular problems, addresses the unique new challenges posed by social marketing.  Even though policymakers ultimately may choose not to regulate social marketing at all, that decision cannot be made intelligently without first contemplating possible problems and solutions. The Article concludes by suggesting a legal response that draws from existing law and requires only small changes. In doing so, it provides an example for adapting existing law to new technology, and it argues that law should play a more active role in establishing best practices for emerging online trends.</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://blogs.law.harvard.edu/infolaw/2009/09/03/soc-mktg-published/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	<creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
	</item>
		<item>
		<title>Adjusting Facebook Privacy</title>
		<link>http://blogs.law.harvard.edu/infolaw/2009/08/17/adjusting-facebook-privacy/</link>
		<comments>http://blogs.law.harvard.edu/infolaw/2009/08/17/adjusting-facebook-privacy/#comments</comments>
		<pubDate>Tue, 18 Aug 2009 01:43:17 +0000</pubDate>
		<dc:creator>William McGeveran</dc:creator>
				<category><![CDATA[Anonymity]]></category>
		<category><![CDATA[Intermediaries]]></category>
		<category><![CDATA[Privacy]]></category>
		<category><![CDATA[Social Networking]]></category>

		<guid isPermaLink="false">http://blogs.law.harvard.edu/infolaw/?p=763</guid>
		<description><![CDATA[Michael Zimmer has updated and re-posted his extremely helpful directions for adjusting Facebook privacy settings.  Do yourself a favor, stop what you are doing, go read and follow his instructions.
]]></description>
			<content:encoded><![CDATA[<p><a href="http://michaelzimmer.org/bio/">Michael Zimmer</a> has updated and re-posted his <a href="http://michaelzimmer.org/2009/08/12/how-to-adjust-your-facebook-privacy-settings-2009/">extremely helpful directions for adjusting Facebook privacy settings</a>.  Do yourself a favor, stop what you are doing, go read and follow his instructions.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.law.harvard.edu/infolaw/2009/08/17/adjusting-facebook-privacy/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	<creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
	</item>
		<item>
		<title>Canadian Privacy Commissioner: Facebook Violates National Law</title>
		<link>http://blogs.law.harvard.edu/infolaw/2009/07/17/canada-fcbk-report/</link>
		<comments>http://blogs.law.harvard.edu/infolaw/2009/07/17/canada-fcbk-report/#comments</comments>
		<pubDate>Fri, 17 Jul 2009 19:33:41 +0000</pubDate>
		<dc:creator>William McGeveran</dc:creator>
				<category><![CDATA[Digital Media]]></category>
		<category><![CDATA[Intermediaries]]></category>
		<category><![CDATA[Internet & Society]]></category>
		<category><![CDATA[Privacy]]></category>
		<category><![CDATA[Scholarship]]></category>
		<category><![CDATA[Social Networking]]></category>

		<guid isPermaLink="false">http://blogs.law.harvard.edu/infolaw/?p=671</guid>
		<description><![CDATA[The Privacy Commissioner of Canada, a federal regulator responsible for overseeing compliance with that country&#8217;s broad data protection statute, has issued a long-awaited report on Facebook&#8217;s privacy practices. The investigation was triggered by a formal complaint filed by students at the University of Ontario&#8217;s cyberlaw clinic. The result is a comprehensive and sophisticated analysis that [...]]]></description>
			<content:encoded><![CDATA[<p>The <a href="http://www.priv.gc.ca/index_e.cfm">Privacy Commissioner of Canada</a>, a federal regulator responsible for overseeing compliance with that country&#8217;s <a href="http://www.priv.gc.ca/leg_c/leg_c_p_e.cfm#contenttop">broad data protection statute</a>, has issued a long-awaited report on Facebook&#8217;s privacy practices. The investigation was triggered by a <a href="http://www.cippic.ca/uploads/CIPPICFacebookComplaint_29May08.pdf">formal complaint</a> filed by students at the University of Ontario&#8217;s <a href="http://www.cippic.ca/en/">cyberlaw clinic</a>. The result is a comprehensive and sophisticated analysis that gives Facebook deserved credit for attention to privacy in some areas, but identifies troubling aspects of its practices that are unlawful in Canada. The <a href="http://www.priv.gc.ca/cf-dc/2009/2009_008_0716_e.cfm">full report</a> is worth a look; an <a href="http://www.priv.gc.ca/media/nr-c/2009/bg_090716_e.cfm">official summary</a> is here; and Canadian cyberprof extraordinaire Michael Geist has <a href="http://www.michaelgeist.ca/content/view/4139/125/">written up a good overview</a> as well.</p>
<p>As news coverage (see <a href="http://www.theglobeandmail.com/news/technology/ottawa-takes-on-social-media-giant-for-violating-canadas-law/article1220428/">here</a> and <a href="http://news.bbc.co.uk/2/hi/americas/8155367.stm">here</a>) emphasizes, the Commissioner&#8217;s main concerns are the extent to which third-party applications within the Facebook platform <a href="http://www.ft.com/cms/s/0/2a58acfa-5c35-11de-aea3-00144feabdc0.html">slurp up personal information</a> irrelevant to their functions. The report also identifies some ways in which Facebook&#8217;s disclosures of its practices are insufficiently clear and criticizes certain data retention practices (particularly after deactivation of accounts). The Commissioner suggested changes Facebook could make to comply with the law; after 30 days if Facebook has not taken adequate corrective action the Commissioner may initiate a lawsuit in Canadian court.</p>
<p>I highlighted the Ottawa clinic&#8217;s complaint in my <a href="http://papers.ssrn.com/sol3/papers.cfm?abstract_id=1334406">article about social marketing</a> (which, of course, went to the printer just a few days too early to add mention of the report!). So I was especially interested in the report&#8217;s <a href="http://www.priv.gc.ca/cf-dc/2009/2009_008_0716_e.cfm#sect3">analysis of Facebook&#8217;s advertising practices</a>. In my view, the Commissioner gets it partly, but not entirely, right, stating:</p>
<p><span id="more-671"></span></p>
<blockquote><p>A Social Ad uses the individual’s actions, thumbnail photo and name to promote a certain product or service. The ad then becomes part of the News Feed and intertwines itself in the regular interactions of the user and his or her friends. In effect, the Social Ad takes on the appearance of an endorsement of the product by the user. For this reason, users would not reasonably expect their information to be used in such a manner and they should, as is the current situation, be able to opt out of such an active use of their personal information.</p></blockquote>
<p>It seems to me, and I argue in the article, that a social marketing endorsement like the one described here should require an opt <strong><em>in</em></strong> &#8212; not only for privacy and reputation reasons, but also for information quality (to ensure it is a true endorsement). In practice, though, since the effective <a href="http://blogs.law.harvard.edu/infolaw/2008/09/30/is-facebook-beacon-gone/">demise of Facebook&#8217;s Beacon program</a>, these sorts of social ads only occur when you take actions <em>within</em> Facebook, and in those situations it seems to me reasonable to assume implicit opt-in &#8212; after all, why do you &#8220;become a fan&#8221; of something in Facebook if not to &#8220;share&#8221; with your friends? The report does go on to criticize the clarity of disclosure about the use of information for social marketing and the difficulty of locating the opt-out. The Commissioner proposed more frequent reminders, but Facebook objected, and the report concludes that if Facebook makes its policies clearer and more accessible that will be good enough.</p>
<p>Overall, a great example of the careful (and collaborative) work a robust privacy regulator can do if given the necessary legal muscle and adequate resources. Now let&#8217;s see how Facebook responds next month&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.law.harvard.edu/infolaw/2009/07/17/canada-fcbk-report/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	<creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
	</item>
		<item>
		<title>More Fun With Section 230</title>
		<link>http://blogs.law.harvard.edu/infolaw/2009/07/06/risch-230/</link>
		<comments>http://blogs.law.harvard.edu/infolaw/2009/07/06/risch-230/#comments</comments>
		<pubDate>Mon, 06 Jul 2009 19:05:49 +0000</pubDate>
		<dc:creator>William McGeveran</dc:creator>
				<category><![CDATA[Blogging]]></category>
		<category><![CDATA[Intermediaries]]></category>
		<category><![CDATA[Internet & Society]]></category>
		<category><![CDATA[Privacy]]></category>
		<category><![CDATA[Trademarks]]></category>

		<guid isPermaLink="false">http://blogs.law.harvard.edu/infolaw/?p=658</guid>
		<description><![CDATA[There is some back-and-forth between Michael Risch and me about section 230, building on my earlier post here, now posted on PrawfsBlawg.
]]></description>
			<content:encoded><![CDATA[<p>There is some back-and-forth between Michael Risch and me about section 230, building on <a href="http://blogs.law.harvard.edu/infolaw/2009/06/25/impersonation-and-230/">my earlier post here</a>, now <a href="http://prawfsblawg.blogs.com/prawfsblawg/2009/07/limiting-online-provider-immunity.html">posted on PrawfsBlawg</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.law.harvard.edu/infolaw/2009/07/06/risch-230/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	<creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
	</item>
		<item>
		<title>Judge Rescinds Lori Drew Conviction</title>
		<link>http://blogs.law.harvard.edu/infolaw/2009/07/02/drew-acquittal/</link>
		<comments>http://blogs.law.harvard.edu/infolaw/2009/07/02/drew-acquittal/#comments</comments>
		<pubDate>Thu, 02 Jul 2009 22:23:35 +0000</pubDate>
		<dc:creator>William McGeveran</dc:creator>
				<category><![CDATA[Computer crime]]></category>
		<category><![CDATA[Court Decisions]]></category>
		<category><![CDATA[Intermediaries]]></category>
		<category><![CDATA[Internet & Society]]></category>
		<category><![CDATA[Privacy]]></category>
		<category><![CDATA[Social Networking]]></category>
		<category><![CDATA[Virtual Worlds]]></category>

		<guid isPermaLink="false">http://blogs.law.harvard.edu/infolaw/?p=644</guid>
		<description><![CDATA[A federal judge has set aside last fall&#8217;s convictions of Lori Drew on misdemeanor criminal charges arising from the cyberbullying and resulting suicide of Missouri teenager Megan Meier. Given the awful consequences of the nasty hoax against Meier, it is hard to exactly celebrate. But I did sign an amicus brief arguing that the prosecution [...]]]></description>
			<content:encoded><![CDATA[<p>A federal judge <a href="http://latimesblogs.latimes.com/lanow/2009/07/myspace-sentencing.html">has set aside</a> last fall&#8217;s convictions of Lori Drew on misdemeanor criminal charges arising from the cyberbullying and resulting suicide of Missouri teenager Megan Meier. Given the awful consequences of the nasty hoax against Meier, it is hard to exactly celebrate. But I did <a href="http://blogs.law.harvard.edu/infolaw/2008/08/04/drew-amicus/">sign an amicus brief</a> arguing that the prosecution stretched the <a href="http://www.law.cornell.edu/uscode/18/1030.html">Computer Fraud and Abuse Act</a> well beyond acceptable boundaries, setting an alarming precedent. Apparently that&#8217;s <a href="http://www.wired.com/threatlevel/2009/07/drew_court/">exactly what the judge ruled</a> (a written decision is expected next week). As I did before when I wrote about this, I will just quote Justice Oliver Wendell Holmes:</p>
<blockquote><p>Great cases, like hard cases, make bad law. For great cases are called great, not by reason of their real importance in shaping the law of the future, but because of some accident of immediate overwhelming interest which appeals to the feelings and distorts the judgment. These immediate interests exercise a kind of hydraulic pressure which makes what previously was clear seem doubtful, and before which even well settled principles of law will bend. <em><a href="http://www.law.cornell.edu/supct/html/historics/USSC_CR_0193_0197_ZD1.html">Northern Securities Co. v. United States</em>, 193 U.S. 197 (1904) (Holmes, J., dissenting)</a>.</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://blogs.law.harvard.edu/infolaw/2009/07/02/drew-acquittal/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	<creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
	</item>
		<item>
		<title>Supreme Court Leaves Info/Law Alone</title>
		<link>http://blogs.law.harvard.edu/infolaw/2009/06/29/scotus-ayotte-cablevision/</link>
		<comments>http://blogs.law.harvard.edu/infolaw/2009/06/29/scotus-ayotte-cablevision/#comments</comments>
		<pubDate>Mon, 29 Jun 2009 18:07:14 +0000</pubDate>
		<dc:creator>William McGeveran</dc:creator>
				<category><![CDATA[Copyright]]></category>
		<category><![CDATA[Court Decisions]]></category>
		<category><![CDATA[First Amendment]]></category>
		<category><![CDATA[Media]]></category>
		<category><![CDATA[Privacy]]></category>
		<category><![CDATA[Voting]]></category>

		<guid isPermaLink="false">http://blogs.law.harvard.edu/infolaw/?p=613</guid>
		<description><![CDATA[Most commentary about the Supreme Court today surely will focus on the controversial Ricci employment discrimination case and its impact on Judge Sotomayor&#8217;s confirmation hearings.  But the Court also announced two important orders in Info/Law, both concerning decisions that it will not make.  By refusing to grant cert. in these cases, the Court [...]]]></description>
			<content:encoded><![CDATA[<p>Most commentary about the Supreme Court today surely will focus on the <a href="http://www.washingtonpost.com/wp-dyn/content/article/2009/06/29/AR2009062901608.html">controversial <em>Ricci </em>employment discrimination case</a> and its impact on Judge Sotomayor&#8217;s confirmation hearings.  But the Court also announced two important orders in Info/Law, both concerning decisions that it will <em>not </em>make.  By refusing to grant cert. in these cases, the Court lets two very good appellate rulings remain in force.</p>
<p>First, the <a href="http://www.reuters.com/article/domesticNews/idUSTRE55S3C420090629">Court denied cert.</a> in <em>IMS Health v. Ayotte</em>.  This case involved data miners&#8217; First Amendment challenge to a New Hampshire law that prohibits the transfer of physicians&#8217; prescribing records for use by pharmaceutical company representatives in their efforts to promote certain drugs to individual doctors. The First Circuit&#8217;s <a href="http://epic.org/privacy/imshealth/11_18_08_order.pdf">thorough decision</a> in the case upheld the law on two distinct grounds: the transfer of the records was conduct rather than speech; and anyway if it was commercial speech the law satisfied the narrow tailoring requirements of the <em>Central Hudson</em> test.  There is somewhat mixed case law on the First Amendment status of data mining, but I think the pro-privacy side is winning overall.  (For more on this complex topic, see Neil Richards&#8217; great <a href="http://papers.ssrn.com/sol3/papers.cfm?abstract_id=598370">law review article</a>). While it might have been nice if the Supreme Court took the case and delivered the death blow to data miners&#8217; constitutional arguments, that would have been very risky; it is better to leave Judge Selya&#8217;s strong opinion &#8212; and New Hampshire&#8217;s law, imitated by some other states &#8212; in place. (<a href="http://epic.org/2009/06/supreme-court-let-stand-new-ha.html">EPIC has more information</a> on this one.)</p>
<p>The second decision is close to my co-blogger Tim&#8217;s heart, as he has <a href="http://blogs.law.harvard.edu/infolaw/2007/06/11/ip-professors-amicus-brief-in-20th-century-fox-v-cablevision/">described before</a>.  The Supreme Court refused to review the <a href="http://blogs.law.harvard.edu/infolaw/2008/08/05/2nd-circuit-a-copy-that-exists-for-1-second-is-no-copy-at-all/">Second Circuit&#8217;s opinion</a> finding that Cablevision&#8217;s proposed new DVR system does not violate copyright law.  (<a href="http://www.publicknowledge.org/node/2509">Public Knowledge has more discussion</a> on this one.)</p>
<p>(And by the way, if you share my side interest in election law, <a href="http://www.washingtonpost.com/wp-dyn/content/article/2009/06/29/AR2009062901773.html">today&#8217;s announcement</a> that the Court will hear more arguments in the campaign finance case about the Hillary Clinton documentary rather than deciding it &#8212; and consider much broader issues about corporate political donations &#8212; is also a bombshell.  Probably a <a href="http://www.slate.com/id/2221753/">very bad sign</a> for advocates of campaign finance regulation.  Lots of big news other than <em>Ricci </em>today!)</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.law.harvard.edu/infolaw/2009/06/29/scotus-ayotte-cablevision/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	<creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
	</item>
		<item>
		<title>Celebrity Impersonation and Section 230</title>
		<link>http://blogs.law.harvard.edu/infolaw/2009/06/25/impersonation-and-230/</link>
		<comments>http://blogs.law.harvard.edu/infolaw/2009/06/25/impersonation-and-230/#comments</comments>
		<pubDate>Thu, 25 Jun 2009 20:55:19 +0000</pubDate>
		<dc:creator>William McGeveran</dc:creator>
				<category><![CDATA[Anonymity]]></category>
		<category><![CDATA[Digital Media]]></category>
		<category><![CDATA[First Amendment]]></category>
		<category><![CDATA[Intermediaries]]></category>
		<category><![CDATA[Internet & Society]]></category>
		<category><![CDATA[Privacy]]></category>
		<category><![CDATA[Social Networking]]></category>
		<category><![CDATA[Trademarks]]></category>

		<guid isPermaLink="false">http://blogs.law.harvard.edu/infolaw/?p=597</guid>
		<description><![CDATA[Cyberprof Michael Risch has posted some interesting thoughts on the emerging complexity of Section 230.  We&#8217;ve talked about this provision on the blog many times before. And Mark Lemley wrote a good paper on it a while back. The provision pretty much immunizes web sites and other internet providers from liability for a host [...]]]></description>
			<content:encoded><![CDATA[<p>Cyberprof <a href="http://law.wvu.edu/faculty/full_time_+faculty/michael_v_risch">Michael Risch</a> has posted some interesting thoughts on the emerging complexity of <a href="http://www.techlawjournal.com/courts/zeran/47usc230.htm">Section 230</a>.  We&#8217;ve talked about this provision on the blog <a href="http://blogs.law.harvard.edu/infolaw/?s=section+230">many times before</a>. And Mark Lemley wrote a <a href="http://papers.ssrn.com/sol3/papers.cfm?abstract_id=979836">good paper</a> on it a while back. The provision pretty much immunizes web sites and other internet providers from liability for a host of legal infractions arising from user-generated content, including defamation and invasion of privacy.  While some cases are pretty simple, now we are seeing more complex situations arising.</p>
<p>Among the newest is the <a href="http://www.citmedialaw.org/sites/citmedialaw.org/files/2009-05-06-La%20Russa%20Complaint.pdf">recent lawsuit</a> filed by St. Louis Cardinals manager Tony LaRussa against Twitter. A user who claimed to be LaRussa opened a Twitter account in his name and said some nasty things, including mocking references to the deaths of two Cardinals pitchers. Twitter denied initial reports that the suit had been settled in a somewhat bellicose <a href="http://blog.twitter.com/2009/06/not-playing-ball.html">blog post</a> (remember, lawyers: it isn&#8217;t a settlement until the other guy&#8217;s client signs off). Twitter then removed the case (that is, transferred it) from state to federal court, where it currently remains active on the docket of the Northern District of California. (The best news coverage is <a href="http://www.businessweek.com/technology/content/jun2009/tc2009069_767898.htm">here </a>and <a href="http://www.law.com/jsp/article.jsp?id=1202431321477">here</a>.) The phony LaRussa account was terminated long ago; impersonation violates Twitter&#8217;s terms of service.</p>
<p>LaRussa&#8217;s actual grievances sound like they should give rise to defamation or false light, or perhaps the appropriation tort.  But these would all be blocked, quite routinely, by section 230. Of course, LaRussa could go after the individual impostor, assuming that person could be found. Instead, his lawyers framed much of his complaint in terms of trademark infringement. Why? It&#8217;s no coincidence that section 230(d) carves out IP (along with criminal law) from the special immunity, stating, &#8220;Nothing in this section shall be construed to limit or expand any law pertaining to intellectual property.&#8221;</p>
<p>But to prevail on the trademark infringement claim, LaRussa has to prove that the phony account was likely to confuse consumers into thinking he endorsed Twitter, thus harming him.  That is why his complaint emphasizes:<br />
<span id="more-597"></span></p>
<blockquote><p>The Site states in large lettering, &#8216;Tony LaRussa is using Twitter,&#8217; and encourages users to &#8216;Join today to start receiving Tony LaRussa&#8217;s updates.&#8221; It also contains a picture of Plaintiff with his name printed next to ít. Beneath the picture, the Site contains written entries that are impliedly written by Plaintiff himself when in fact they are not.</p></blockquote>
<p>In this particular case, proving confusion and harm <a href="http://www.columbiamissourian.com/stories/2009/06/07/experts-say-la-russas-twitter-suit-was-long-shot/">will be very difficult</a>, since (1) the account only had four followers; (2) it included a notation in the user&#8217;s profile section, &#8220;Bio Parodies are fun for everyone;&#8221; (3) it&#8217;s not clear a statement (even a false one) that LaRussa used the service can fairly be called an endorsement of the service (though the &#8220;endorsement&#8221; concept can be slippery, as I have <a href="http://papers.ssrn.com/sol3/papers.cfm?abstract_id=1334406">written elsewhere</a>). Trademark <em>dilution </em>does not require confusion or monetary harm, but LaRussa pleaded under federal dilution law, which allows only injunctive relief &#8212; now moot since the profile is gone &#8212; and completely exempts &#8220;noncommercial use&#8221; of a trademark.</p>
<p>More generally, however, this case highlights the possibility of a loophole for celebrities who can recast privacy-like claims under trademark law (and possibly also rights of publicity, if those are interpreted as intellectual property under the language of section 230(d)). Where would that leave us? Well, it shows (again) that the apparently bright lines of section 230 sometimes aren&#8217;t.  But it might also create what I&#8217;d consider a pernicious double standard: celebrities maligned by anonymous online impostors could plead around section 230 by claiming trademark or publicity rights in their name, while many <a href="http://blogs.law.harvard.edu/infolaw/2009/02/13/margolick-on-autoadmit/">ordinary people victimized by defamation or cyber-bullying</a> would have their claims blocked.  Other law, defamation in particular, expects celebrities to have thicker skin and tolerates more insensitive speech about them.  If LaRussa pulled off this <a href="http://en.wikipedia.org/wiki/Squeeze_play_(baseball)">suicide squeeze</a>, that sensible dichotomy might get turned on its head.</p>
<p>[UPDATE:  I plumb forgot to mention another crucial angle: Twitter <a href="http://twitter.com/help/verified">now wants to sell verified accounts</a> to celebrities (as in, &#8220;This is the real Tony LaRussa tweeting.&#8221;)  Those wouldn&#8217;t fetch a very high price if the fake accounts from which the celebs are trying to distinguish themselves are unlawful and Twitter is liable for them.)</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.law.harvard.edu/infolaw/2009/06/25/impersonation-and-230/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
	<creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
	</item>
		<item>
		<title>Google, Encryption, and Security</title>
		<link>http://blogs.law.harvard.edu/infolaw/2009/06/16/google-encryption-and-security/</link>
		<comments>http://blogs.law.harvard.edu/infolaw/2009/06/16/google-encryption-and-security/#comments</comments>
		<pubDate>Tue, 16 Jun 2009 16:58:01 +0000</pubDate>
		<dc:creator>Derek Bambauer</dc:creator>
				<category><![CDATA[Computer crime]]></category>
		<category><![CDATA[Digital Media]]></category>
		<category><![CDATA[Encryption]]></category>
		<category><![CDATA[ISP]]></category>
		<category><![CDATA[Intermediaries]]></category>
		<category><![CDATA[Internet & Society]]></category>
		<category><![CDATA[Law School]]></category>
		<category><![CDATA[Media]]></category>
		<category><![CDATA[Privacy]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[badware]]></category>

		<guid isPermaLink="false">http://blogs.law.harvard.edu/infolaw/?p=566</guid>
		<description><![CDATA[The Washington Post covers a letter by security researchers and academics urging Google to adopt encryption (HTTPS) as the default for all of its services. (Disclosure: I signed the letter.) The letter makes the case convincingly:
Google uses industry-standard Hypertext Transfer Protocol Secure (HTTPS) encryption technology to protect customers’ login information. However, encryption is not enabled [...]]]></description>
			<content:encoded><![CDATA[<p>The <a href="http://voices.washingtonpost.com/securityfix/2009/06/top_security_minds_urge_google.html?hpid=news-col-blog" target="_blank">Washington Post covers</a> a <a href="http://voices.washingtonpost.com/securityfix/google-letter-final.pdf" target="_blank">letter by security researchers and academics urging Google to adopt encryption (HTTPS) as the default</a> for all of its services. (Disclosure: I signed the letter.) The letter makes the case convincingly:</p>
<blockquote><p>Google uses industry-standard Hypertext Transfer Protocol Secure (HTTPS) encryption technology to protect customers’ login information. However, encryption is not enabled by default to protect other information transmitted by users of Google Mail, Docs or Calendar. As a result, Google customers who compose email, documents, spreadsheets, presentations and calendar plans from a public connection (such as open wireless networks in coffee shops, libraries, and schools) face a very real risk of data theft and snooping, even by unsophisticated attackers. Tools to steal information are widely available on the Internet.</p></blockquote>
<p><a href="http://www.wired.com/threatlevel/2009/06/google_ssl/">Thanks to Chris Soghoian</a> for his leadership on this one!</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.law.harvard.edu/infolaw/2009/06/16/google-encryption-and-security/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	<creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
	</item>
	</channel>
</rss>
