<?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:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: How Filtering Affects ISPs</title>
	<atom:link href="http://blogs.law.harvard.edu/infolaw/2009/03/14/how-filtering-affects-isps/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.law.harvard.edu/infolaw/2009/03/14/how-filtering-affects-isps/</link>
	<description>Information, Law, and the Law of Information</description>
	<lastBuildDate>Tue, 24 Nov 2009 00:08:14 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Info/Law &#187; Interview with Background Briefing on Australian Broadcasting Corporation</title>
		<link>http://blogs.law.harvard.edu/infolaw/2009/03/14/how-filtering-affects-isps/comment-page-1/#comment-83973</link>
		<dc:creator>Info/Law &#187; Interview with Background Briefing on Australian Broadcasting Corporation</dc:creator>
		<pubDate>Tue, 17 Mar 2009 15:58:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/infolaw/?p=469#comment-83973</guid>
		<description>[...] to the report on-line or download it. For my take on how filtering alters the role of ISPs, see my write-up here, and for my thoughts on the Australian situation, see my SSRN piece [...]</description>
		<content:encoded><![CDATA[<p>[...] to the report on-line or download it. For my take on how filtering alters the role of ISPs, see my write-up here, and for my thoughts on the Australian situation, see my SSRN piece [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TJ McIntyre</title>
		<link>http://blogs.law.harvard.edu/infolaw/2009/03/14/how-filtering-affects-isps/comment-page-1/#comment-83238</link>
		<dc:creator>TJ McIntyre</dc:creator>
		<pubDate>Sat, 14 Mar 2009 16:15:11 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/infolaw/?p=469#comment-83238</guid>
		<description>An insightful piece this. I&#039;m in general agreement with your argument (and enjoyed the Cylon reference!) but have to quibble slightly with this point:

&quot;There can be benefits from requiring ISPs to act as enforcers. The application of restrictions is likely to be more uniform than with controls on end users directly....&quot;

In the UK context (which I&#039;m currently researching) this doesn&#039;t seem to have been the case. While government policy requiring filtering of (alleged) child pornography is itself reasonably uniform - being based on the IWF blacklist - the application of that filtering has been anything but. While the majority of ISPs have been using a two stage filter looking at individual URLs, one ISP - Be Unlimited - is reported to have used crude IP address blocking, preventing access to innocent websites sharing the same physical server [1]. A similar issue happened in respect of the Internet Archive, where Demon Internet&#039;s application of the filtering system resulted in substantial collateral damage - even to users on *other* ISPs [2]. Transparency has also been patchy: ISPs have differed as to whether they notify users as to why a page is blocked. Demon Internet does [3] while the majority of others appear to use a deceptive error page instead.

I&#039;m also slightly sceptical as to what we mean by uniformity. Centralised systems such as the IWF blacklist may be uniform in the sense that each user is subjected to the same restrictions - this is not, however, a guarantee that those restrictions are uniform within themselves. (In the sense that different sites are subject to the same rules and procedures.) For example, the IWF climbdown over the Wikipedia / Scorpions album cover suggests to me that there may be questions as to the legitimacy and accountability of the IWF&#039;s procedures, as well as disparities between the treatment of high-profile and media savvy sites and others and between the treatment of online and offline content [4].

[1] http://www.thinkbroadband.com/news/3235-be-unlimited-causes-stir-in-effort-of-blocking-child-abuse-images.html
[2] http://www.ispreview.co.uk/news/EkFEAFAyyACWhcpXZJ.html ; http://www.theregister.co.uk/2009/01/16/demon_resolves_wayback_issue/
[3] http://www.demon.net/error/403-blocked.html
[4] http://tjmcintyre.com/2008/12/some-thoughts-on-iwf-wikipedia-debacle.html</description>
		<content:encoded><![CDATA[<p>An insightful piece this. I&#8217;m in general agreement with your argument (and enjoyed the Cylon reference!) but have to quibble slightly with this point:</p>
<p>&#8220;There can be benefits from requiring ISPs to act as enforcers. The application of restrictions is likely to be more uniform than with controls on end users directly&#8230;.&#8221;</p>
<p>In the UK context (which I&#8217;m currently researching) this doesn&#8217;t seem to have been the case. While government policy requiring filtering of (alleged) child pornography is itself reasonably uniform &#8211; being based on the IWF blacklist &#8211; the application of that filtering has been anything but. While the majority of ISPs have been using a two stage filter looking at individual URLs, one ISP &#8211; Be Unlimited &#8211; is reported to have used crude IP address blocking, preventing access to innocent websites sharing the same physical server [1]. A similar issue happened in respect of the Internet Archive, where Demon Internet&#8217;s application of the filtering system resulted in substantial collateral damage &#8211; even to users on *other* ISPs [2]. Transparency has also been patchy: ISPs have differed as to whether they notify users as to why a page is blocked. Demon Internet does [3] while the majority of others appear to use a deceptive error page instead.</p>
<p>I&#8217;m also slightly sceptical as to what we mean by uniformity. Centralised systems such as the IWF blacklist may be uniform in the sense that each user is subjected to the same restrictions &#8211; this is not, however, a guarantee that those restrictions are uniform within themselves. (In the sense that different sites are subject to the same rules and procedures.) For example, the IWF climbdown over the Wikipedia / Scorpions album cover suggests to me that there may be questions as to the legitimacy and accountability of the IWF&#8217;s procedures, as well as disparities between the treatment of high-profile and media savvy sites and others and between the treatment of online and offline content [4].</p>
<p>[1] <a href="http://www.thinkbroadband.com/news/3235-be-unlimited-causes-stir-in-effort-of-blocking-child-abuse-images.html" rel="nofollow">http://www.thinkbroadband.com/news/3235-be-unlimited-causes-stir-in-effort-of-blocking-child-abuse-images.html</a><br />
[2] <a href="http://www.ispreview.co.uk/news/EkFEAFAyyACWhcpXZJ.html" rel="nofollow">http://www.ispreview.co.uk/news/EkFEAFAyyACWhcpXZJ.html</a> ; <a href="http://www.theregister.co.uk/2009/01/16/demon_resolves_wayback_issue/" rel="nofollow">http://www.theregister.co.uk/2009/01/16/demon_resolves_wayback_issue/</a><br />
[3] <a href="http://www.demon.net/error/403-blocked.html" rel="nofollow">http://www.demon.net/error/403-blocked.html</a><br />
[4] <a href="http://tjmcintyre.com/2008/12/some-thoughts-on-iwf-wikipedia-debacle.html" rel="nofollow">http://tjmcintyre.com/2008/12/some-thoughts-on-iwf-wikipedia-debacle.html</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
