<?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: Library to block porn websites</title>
	<atom:link href="http://ndlaonline.org/ifblog/?feed=rss2&#038;p=2470" rel="self" type="application/rss+xml" />
	<link>http://ndlaonline.org/ifblog/?p=2470</link>
	<description></description>
	<lastBuildDate>Fri, 03 May 2013 20:29:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Eric</title>
		<link>http://ndlaonline.org/ifblog/?p=2470&#038;cpage=1#comment-7631</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Fri, 28 Sep 2012 15:58:45 +0000</pubDate>
		<guid isPermaLink="false">http://ndlaonline.org/ifblog/?p=2470#comment-7631</guid>
		<description><![CDATA[Any time there is a dramatic response to a negligible issue, it raises a red flag for me. 

&quot;The new filters would not have prevented the August incident&quot; - So, this &quot;solution&quot; would have done nothing to prevent the situation it&#039;s a response to? That&#039;s the definition of a project unworthy of undertaking. 

What&#039;s more, the person involved in the incident (who apparently was not even viewing pornography) could have requested a filter override since he was 22 at the time and the library would be legally obligated to oblige him with no questions asked.

According to the article, this library has had a total of 6 incidents over the course of 1.6 million library visits, including 400,000 computer sessions. Just looking at the computer sessions, that&#039;s 0.0015% of the time, or once every 66,667 transactions. This is not a real problem. The solution imposed, may be a problem, however. 

Escalating the filter levels always means escalating the extent to which you over-filter. Depending on how this is handled, it can also open the door for lawsuits (consider all the cases of over-filtering preventing access to health information and LGBT community sites leading to successful suits against school libraries). 

The good news? It&#039;s still illegal to do illegal things, even if you do them in a library. Hence, the dude being arrested. Public display of obscene materials is illegal. It&#039;s almost certain to be a violation of this library&#039;s internet access policy, as well.]]></description>
		<content:encoded><![CDATA[<p>Any time there is a dramatic response to a negligible issue, it raises a red flag for me. </p>
<p>&#8220;The new filters would not have prevented the August incident&#8221; &#8211; So, this &#8220;solution&#8221; would have done nothing to prevent the situation it&#8217;s a response to? That&#8217;s the definition of a project unworthy of undertaking. </p>
<p>What&#8217;s more, the person involved in the incident (who apparently was not even viewing pornography) could have requested a filter override since he was 22 at the time and the library would be legally obligated to oblige him with no questions asked.</p>
<p>According to the article, this library has had a total of 6 incidents over the course of 1.6 million library visits, including 400,000 computer sessions. Just looking at the computer sessions, that&#8217;s 0.0015% of the time, or once every 66,667 transactions. This is not a real problem. The solution imposed, may be a problem, however. </p>
<p>Escalating the filter levels always means escalating the extent to which you over-filter. Depending on how this is handled, it can also open the door for lawsuits (consider all the cases of over-filtering preventing access to health information and LGBT community sites leading to successful suits against school libraries). </p>
<p>The good news? It&#8217;s still illegal to do illegal things, even if you do them in a library. Hence, the dude being arrested. Public display of obscene materials is illegal. It&#8217;s almost certain to be a violation of this library&#8217;s internet access policy, as well.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
