<?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: Distributor of Software That Blocks (Alleged) Adware and Malware Immune Under 47 U.S.C. &#167; 230 from Suit by Company Whose Software Was Blocked:</title>
	<atom:link href="http://volokh.com/2009/06/25/distributor-of-software-that-blocks-alleged-adware-and-malware-immune-under-47-u-s-c-230-from-suit-by-company-whose-software-was-blocked/feed/" rel="self" type="application/rss+xml" />
	<link>http://volokh.com/2009/06/25/distributor-of-software-that-blocks-alleged-adware-and-malware-immune-under-47-u-s-c-230-from-suit-by-company-whose-software-was-blocked/</link>
	<description>Commentary on law, public policy, and more</description>
	<lastBuildDate>Tue, 14 Feb 2012 11:07:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Best Virus Protection &#8211; Kaspersky Anti-Virus</title>
		<link>http://volokh.com/2009/06/25/distributor-of-software-that-blocks-alleged-adware-and-malware-immune-under-47-u-s-c-230-from-suit-by-company-whose-software-was-blocked/comment-page-1/#comment-890881</link>
		<dc:creator>Best Virus Protection &#8211; Kaspersky Anti-Virus</dc:creator>
		<pubDate>Thu, 29 Jul 2010 18:04:48 +0000</pubDate>
		<guid isPermaLink="false">http://208.43.137.32/~volokhc/wp/?p=17225#comment-890881</guid>
		<description>[...] Distributor of Software That Blocks (Alleged) Adware and Malware Immune Under 47 U.S.C. § 230 from ... I&#8217;m afraid I don&#8217;t have time to blog more about this now, but I thought I&#8217;d note it, since it seems like a pretty important cyberspace law decision. The case is Zango, Inc. v. Kaspersky Lab, Inc., handed down today by the Ninth Circuit. Thanks to How Appealing for the &#8230; [...]</description>
		<content:encoded><![CDATA[<p>[...] Distributor of Software That Blocks (Alleged) Adware and Malware Immune Under 47 U.S.C. § 230 from &#8230; I&#8217;m afraid I don&#8217;t have time to blog more about this now, but I thought I&#8217;d note it, since it seems like a pretty important cyberspace law decision. The case is Zango, Inc. v. Kaspersky Lab, Inc., handed down today by the Ninth Circuit. Thanks to How Appealing for the &#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AnthonyJ</title>
		<link>http://volokh.com/2009/06/25/distributor-of-software-that-blocks-alleged-adware-and-malware-immune-under-47-u-s-c-230-from-suit-by-company-whose-software-was-blocked/comment-page-1/#comment-578413</link>
		<dc:creator>AnthonyJ</dc:creator>
		<pubDate>Fri, 26 Jun 2009 04:35:11 +0000</pubDate>
		<guid isPermaLink="false">http://208.43.137.32/~volokhc/wp/?p=17225#comment-578413</guid>
		<description>Pretty sure Conficker is illegal on other grounds, though in theory if you deliberately installed it it would be legal for it to block your access to AV sites.
</description>
		<content:encoded><![CDATA[<p>Pretty sure Conficker is illegal on other grounds, though in theory if you deliberately installed it it would be legal for it to block your access to AV sites.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Its_real</title>
		<link>http://volokh.com/2009/06/25/distributor-of-software-that-blocks-alleged-adware-and-malware-immune-under-47-u-s-c-230-from-suit-by-company-whose-software-was-blocked/comment-page-1/#comment-578412</link>
		<dc:creator>Its_real</dc:creator>
		<pubDate>Fri, 26 Jun 2009 02:14:26 +0000</pubDate>
		<guid isPermaLink="false">http://208.43.137.32/~volokhc/wp/?p=17225#comment-578412</guid>
		<description>At least one botnet trojan does &quot;improve&quot; security of the zombie and prevent/clean infections of a number of other trojans.... so the PC will not experience slowdowns and problems from multiple infections -- this prolongs the &quot;life&quot; of the zombie for the botnet.
</description>
		<content:encoded><![CDATA[<p>At least one botnet trojan does &#8220;improve&#8221; security of the zombie and prevent/clean infections of a number of other trojans&#8230;. so the PC will not experience slowdowns and problems from multiple infections &#8212; this prolongs the &#8220;life&#8221; of the zombie for the botnet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: xyzzy</title>
		<link>http://volokh.com/2009/06/25/distributor-of-software-that-blocks-alleged-adware-and-malware-immune-under-47-u-s-c-230-from-suit-by-company-whose-software-was-blocked/comment-page-1/#comment-578411</link>
		<dc:creator>xyzzy</dc:creator>
		<pubDate>Thu, 25 Jun 2009 23:52:11 +0000</pubDate>
		<guid isPermaLink="false">http://208.43.137.32/~volokhc/wp/?p=17225#comment-578411</guid>
		<description>&lt;blockquote&gt;&lt;i&gt;Can a virus-maker get the statute&#039;s protection simply by blocking one objectionable site and linking to a server, with immunity to block access to whatever it wants </description>
		<content:encoded><![CDATA[<blockquote><p><i>Can a virus-maker get the statute&#8217;s protection simply by blocking one objectionable site and linking to a server, with immunity to block access to whatever it wants</i></p></blockquote>
]]></content:encoded>
	</item>
	<item>
		<title>By: zippypinhead</title>
		<link>http://volokh.com/2009/06/25/distributor-of-software-that-blocks-alleged-adware-and-malware-immune-under-47-u-s-c-230-from-suit-by-company-whose-software-was-blocked/comment-page-1/#comment-578410</link>
		<dc:creator>zippypinhead</dc:creator>
		<pubDate>Thu, 25 Jun 2009 23:51:18 +0000</pubDate>
		<guid isPermaLink="false">http://208.43.137.32/~volokhc/wp/?p=17225#comment-578410</guid>
		<description>Clearly a correct decision under the controlling safe harbor language of the CDA.  But Judge Fisher&#039;s concurrence is even more interesting than the actual holding:&lt;blockquote&gt;Congress plainly intended to give computer users the tools to filter the Internet</description>
		<content:encoded><![CDATA[<p>Clearly a correct decision under the controlling safe harbor language of the CDA.  But Judge Fisher&#8217;s concurrence is even more interesting than the actual holding:<br />
<blockquote>Congress plainly intended to give computer users the tools to filter the Internet</p></blockquote>
]]></content:encoded>
	</item>
	<item>
		<title>By: ReaderY</title>
		<link>http://volokh.com/2009/06/25/distributor-of-software-that-blocks-alleged-adware-and-malware-immune-under-47-u-s-c-230-from-suit-by-company-whose-software-was-blocked/comment-page-1/#comment-578409</link>
		<dc:creator>ReaderY</dc:creator>
		<pubDate>Thu, 25 Jun 2009 23:35:23 +0000</pubDate>
		<guid isPermaLink="false">http://208.43.137.32/~volokhc/wp/?p=17225#comment-578409</guid>
		<description>If the 9th Circuit had given &quot;otherwise objectionable&quot; some sort of limiting definition and provided for review to see whether the blocked party might be perceived by a reasonable person as possibly fitting that definition, it would be a different case (although not a different outcome -- the existence of the FTC consent decree against Zango would likely be sufficient by itself to invoke the safe harbor under any reasonable limiting definition of &quot;objectionable&quot;.)
&lt;BR /&gt;
&lt;BR /&gt;But by expressly declining to do this, and leaving the meaning of &quot;objectionable&quot; to reflect whatever the filterer objects to, the case appears to open up the prospect of unexpected kinds of objections leading to filtering being used for offensive as distinct from purely defensive purposes -- perhaps even protecting kinds of filtering that  consumers find so offensive that they might consider the filtering itself to be malicious.
</description>
		<content:encoded><![CDATA[<p>If the 9th Circuit had given &#8220;otherwise objectionable&#8221; some sort of limiting definition and provided for review to see whether the blocked party might be perceived by a reasonable person as possibly fitting that definition, it would be a different case (although not a different outcome &#8212; the existence of the FTC consent decree against Zango would likely be sufficient by itself to invoke the safe harbor under any reasonable limiting definition of &#8220;objectionable&#8221;.)</p>
<p>But by expressly declining to do this, and leaving the meaning of &#8220;objectionable&#8221; to reflect whatever the filterer objects to, the case appears to open up the prospect of unexpected kinds of objections leading to filtering being used for offensive as distinct from purely defensive purposes &#8212; perhaps even protecting kinds of filtering that  consumers find so offensive that they might consider the filtering itself to be malicious.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ReaderY</title>
		<link>http://volokh.com/2009/06/25/distributor-of-software-that-blocks-alleged-adware-and-malware-immune-under-47-u-s-c-230-from-suit-by-company-whose-software-was-blocked/comment-page-1/#comment-578408</link>
		<dc:creator>ReaderY</dc:creator>
		<pubDate>Thu, 25 Jun 2009 23:22:29 +0000</pubDate>
		<guid isPermaLink="false">http://208.43.137.32/~volokhc/wp/?p=17225#comment-578408</guid>
		<description>If a company provided both
&lt;BR /&gt;
&lt;BR /&gt;(a) an update feature on its products (involving multiple users accessing a server) amd (b) a token filter that restricted access to a single pornographic website),
&lt;BR /&gt;
&lt;BR /&gt;would it then have complete immunity to block access to whatever it wanted, e.g. websites on competitors products or consumer websites containing negative reviews of its products?
&lt;BR /&gt;
&lt;BR /&gt;The opinion appears to leave the definition of &quot;objectionable&quot; completely undefined and equally within the discretion of the consumer and the provider? It&#039;s a broad term. What does it mean? What happens if the provider&#039;s concept of what it considers &quot;objectionable&quot; turns completely different from the consumer&#039;s? Does the provider have to even consider consumer&#039;s interests or Congressional purposes in making such a determination or is its discretion absolute under the safe harbor?  What happens if the provider&#039;s concept of &quot;objectionable&quot; is so so different from the ideas Congress appeared to have had in mind or from consumers&#039; perception of their interests, indeed so self-serving, that consumers might think its blocking behavior against their interests and malicious?
&lt;BR /&gt;
&lt;BR /&gt;Does the safe harbor, with these critical terms left undefined, open the door for companies to block access to each other&#039;s products as a competitive tool?
&lt;BR /&gt;
&lt;BR /&gt;Can a virus-maker get the statute&#039;s protection simply by blocking one objectionable site and linking to a server, with immunity to block access to whatever it wants -- the entire internet if the virus-maker has Luddite-type objections to the internet as a whole?
&lt;BR /&gt;
&lt;BR /&gt;After all, a key difficulty this case illustrates is that one person&#039;s &quot;filtering&quot; may be another&#039;s &quot;service disruption&quot;. Perhaps all that perveyors of service disruption have to do is get a little legal advice and jump through a few simple hoops to get their disruptions to fit into the definition of &quot;filtering&quot; and into the protection of the safe harbor.
</description>
		<content:encoded><![CDATA[<p>If a company provided both</p>
<p>(a) an update feature on its products (involving multiple users accessing a server) amd (b) a token filter that restricted access to a single pornographic website),</p>
<p>would it then have complete immunity to block access to whatever it wanted, e.g. websites on competitors products or consumer websites containing negative reviews of its products?</p>
<p>The opinion appears to leave the definition of &#8220;objectionable&#8221; completely undefined and equally within the discretion of the consumer and the provider? It&#8217;s a broad term. What does it mean? What happens if the provider&#8217;s concept of what it considers &#8220;objectionable&#8221; turns completely different from the consumer&#8217;s? Does the provider have to even consider consumer&#8217;s interests or Congressional purposes in making such a determination or is its discretion absolute under the safe harbor?  What happens if the provider&#8217;s concept of &#8220;objectionable&#8221; is so so different from the ideas Congress appeared to have had in mind or from consumers&#8217; perception of their interests, indeed so self-serving, that consumers might think its blocking behavior against their interests and malicious?</p>
<p>Does the safe harbor, with these critical terms left undefined, open the door for companies to block access to each other&#8217;s products as a competitive tool?</p>
<p>Can a virus-maker get the statute&#8217;s protection simply by blocking one objectionable site and linking to a server, with immunity to block access to whatever it wants &#8212; the entire internet if the virus-maker has Luddite-type objections to the internet as a whole?</p>
<p>After all, a key difficulty this case illustrates is that one person&#8217;s &#8220;filtering&#8221; may be another&#8217;s &#8220;service disruption&#8221;. Perhaps all that perveyors of service disruption have to do is get a little legal advice and jump through a few simple hoops to get their disruptions to fit into the definition of &#8220;filtering&#8221; and into the protection of the safe harbor.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fub</title>
		<link>http://volokh.com/2009/06/25/distributor-of-software-that-blocks-alleged-adware-and-malware-immune-under-47-u-s-c-230-from-suit-by-company-whose-software-was-blocked/comment-page-1/#comment-578407</link>
		<dc:creator>Fub</dc:creator>
		<pubDate>Thu, 25 Jun 2009 22:21:02 +0000</pubDate>
		<guid isPermaLink="false">http://208.43.137.32/~volokhc/wp/?p=17225#comment-578407</guid>
		<description>From the decision, FN 3:&lt;blockquote&gt;&lt;i&gt;Zango entered into a consent decree with the Federal Trade Commission in November 2006 following an FTC investigation into Zango</description>
		<content:encoded><![CDATA[<p>From the decision, FN 3:<br />
<blockquote><i>Zango entered into a consent decree with the Federal Trade Commission in November 2006 following an FTC investigation into Zango</i></p></blockquote>
]]></content:encoded>
	</item>
</channel>
</rss>

