<?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: How NYU Handles Piracy: Don&#8217;t Get Caught Or Else&#8230;</title>
	<atom:link href="http://www.crunchgear.com/2007/08/27/how-nyu-handles-piracy-dont-get-caught-or-else/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.crunchgear.com/2007/08/27/how-nyu-handles-piracy-dont-get-caught-or-else/</link>
	<description>Gadgets, gear and computer hardware.</description>
	<lastBuildDate>Thu, 03 Dec 2009 20:35:59 -0500</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: IRT</title>
		<link>http://www.crunchgear.com/2007/08/27/how-nyu-handles-piracy-dont-get-caught-or-else/comment-page-1/#comment-1008947</link>
		<dc:creator>IRT</dc:creator>
		<pubDate>Mon, 20 Apr 2009 02:29:20 +0000</pubDate>
		<guid isPermaLink="false">http://crunchgear.com/2007/08/27/how-nyu-handles-piracy-dont-get-caught-or-else/#comment-1008947</guid>
		<description>I&#039;m not at NYU (I go to Hunter) but my friend lets me use his login to access the VPN, which allows me to get around Hunter&#039;s block on torrent traffic.

Does torrenting through VPN fall under the same category of &quot;danger&quot; as torrenting when actually ON the SSID NYU-ROAM3/etc.?</description>
		<content:encoded><![CDATA[<p>I&#8217;m not at NYU (I go to Hunter) but my friend lets me use his login to access the VPN, which allows me to get around Hunter&#8217;s block on torrent traffic.</p>
<p>Does torrenting through VPN fall under the same category of &#8220;danger&#8221; as torrenting when actually ON the SSID NYU-ROAM3/etc.?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Former CTO</title>
		<link>http://www.crunchgear.com/2007/08/27/how-nyu-handles-piracy-dont-get-caught-or-else/comment-page-1/#comment-387018</link>
		<dc:creator>Former CTO</dc:creator>
		<pubDate>Mon, 27 Aug 2007 20:14:22 +0000</pubDate>
		<guid isPermaLink="false">http://crunchgear.com/2007/08/27/how-nyu-handles-piracy-dont-get-caught-or-else/#comment-387018</guid>
		<description>I used to be the CTO (2005 to 2007) of the student government for a small private liberal arts college in SoCal called Claremont Mckenna College. 

I too was very amused when our college published it&#039;s copyright policy saying that students were on their own. However, when one of our sister schools got their asses sued because they decided to protect their students, all of a sudden, the policy looked less silly. (fyi, they are still in court). 

The final policy that I ended up accepting from the IT guys was the &quot;three strikes&quot; policy - if the school gets a DMCA notice, the school will protect the student as long as its the first or second offense. we notify the student, put a letter in their student records, etc. If a student commits an offense a third time, they are put in front of the judicial board, kicked off the network (or worse, given a 56 kbps network connection), and/or turned over to the RIAA/MPAA - as long as they have a valid subpoena ...

personally, i think thats a great approach, but larger universities have a problem with it. but if we protect our students because we start with the assumption that these kids need to be educated on the dangers of &quot;breaking the law&quot;, and they stop, then we have taught them something (isnt that what college is about?). If they still continue to break the law after we notify them twice ... well then they are just plain idiots, and deserve to get whats coming to them.</description>
		<content:encoded><![CDATA[<p>I used to be the CTO (2005 to 2007) of the student government for a small private liberal arts college in SoCal called Claremont Mckenna College. </p>
<p>I too was very amused when our college published it&#8217;s copyright policy saying that students were on their own. However, when one of our sister schools got their asses sued because they decided to protect their students, all of a sudden, the policy looked less silly. (fyi, they are still in court). </p>
<p>The final policy that I ended up accepting from the IT guys was the &#8220;three strikes&#8221; policy &#8211; if the school gets a DMCA notice, the school will protect the student as long as its the first or second offense. we notify the student, put a letter in their student records, etc. If a student commits an offense a third time, they are put in front of the judicial board, kicked off the network (or worse, given a 56 kbps network connection), and/or turned over to the RIAA/MPAA &#8211; as long as they have a valid subpoena &#8230;</p>
<p>personally, i think thats a great approach, but larger universities have a problem with it. but if we protect our students because we start with the assumption that these kids need to be educated on the dangers of &#8220;breaking the law&#8221;, and they stop, then we have taught them something (isnt that what college is about?). If they still continue to break the law after we notify them twice &#8230; well then they are just plain idiots, and deserve to get whats coming to them.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
