File sharing - Revision history

Uf001 at 07:56, 20 January 2016

2016-01-20T07:56:48Z

TheFeynmanParticle: /* Avoiding detection */

2014-01-30T00:42:33Z

‎Avoiding detection

Peterawnislowspatsy: /* Legal risks */

2013-01-27T04:25:36Z

‎Legal risks

Peterawnislowspatsy: /* Legal risks */

2013-01-27T04:24:01Z

‎Legal risks

Peterawnislowspatsy: /* Legal risks */

2013-01-27T04:22:59Z

‎Legal risks

Peterawnislowspatsy: Updated guide and replaced outdated information. MPAA/RIAA ceased targeting Columbia several months after this article was last updated 5 years ago

2013-01-27T04:22:17Z

Updated guide and replaced outdated information. MPAA/RIAA ceased targeting Columbia several months after this article was last updated 5 years ago

Reaganaut at 04:30, 22 November 2012

2012-11-22T04:30:54Z

TheFeynmanParticle: /* Bandwidth limitations */

2012-09-14T19:52:05Z

‎Bandwidth limitations

TheFeynmanParticle: /* Bandwidth limitations */ Bandwidth quotas were raised some time ago

2012-04-29T00:55:52Z

‎Bandwidth limitations: Bandwidth quotas were raised some time ago

160.39.156.179: /* Bandwidth limitations */

2009-09-29T22:32:36Z

‎Bandwidth limitations

@@ Line 16: / Line 16: @@
 * [http://www.g2p.org/ G2P Beta: Using Google to locate MP3s]
 * [http://www.alluc.org/ AllUC]
 == Bandwidth limitations ==

← Older revision		Revision as of 00:42, 30 January 2014
Line 43:		Line 43:

	Others use public network jacks in the libraries and classrooms. These cannot be traced to individual users unless CUIT tries to match UNI login records (eg, for [[Cubmail]], [[Courseworks]], or [[SSOL]]) with connection records.		Others use public network jacks in the libraries and classrooms. These cannot be traced to individual users unless CUIT tries to match UNI login records (eg, for [[Cubmail]], [[Courseworks]], or [[SSOL]]) with connection records.
		+
		+	A foolproof way to avoid getting caught is to go to somewhere with free Wi-Fi such as Starbucks or Uni Cafe and then torrent off of their network.

	=== Columbia policy ===		=== Columbia policy ===

@@ Line 24: / Line 24: @@
 == Legal risks ==
-In late 2008, the RIAA and MPAA ceased their antipiracy strategy of suing individual users,<ref>http://www.wired.com/business/2008/12/riaa-says-it-pl/</ref> partially because [[Harvard|braver universities]] announced they would no longer hand over student information voluntarily.<ref>http://arstechnica.com/tech-policy/2009/02/tell-the-riaa-to-take-a-hike-how-harvard-law-threw-down-the-gauntlet/</ref> The myth that copyright organizations still pursue lone filesharers persists, no thanks to CUIT leaving harshly-worded antipiracy posters up in most computer labs.
+In late 2008, the RIAA and MPAA ceased their antipiracy strategy of suing individual users,<ref>http://www.wired.com/business/2008/12/riaa-says-it-pl/</ref> partially because [[Harvard|braver universities]] announced they would no longer hand over student information voluntarily.<ref>http://arstechnica.com/tech-policy/2009/02/tell-the-riaa-to-take-a-hike-how-harvard-law-threw-down-the-gauntlet/</ref> The myth that copyright organizations still pursue lone filesharers persists, with help from harshly-worded CUIT antipiracy posters in most computer labs and residence halls.
 Although large rightsholder organizations no longer pursue students, CUIT still takes it upon itself to penalize filesharers.

@@ Line 24: / Line 24: @@
 == Legal risks ==
-In late 2008, the RIAA and MPAA ceased their antipiracy strategy of suing individual users,<ref>http://www.wired.com/business/2008/12/riaa-says-it-pl/</ref> in part because [[Harvard|braver universities]] announced they would no longer hand over student information voluntarily.<ref>http://arstechnica.com/tech-policy/2009/02/tell-the-riaa-to-take-a-hike-how-harvard-law-threw-down-the-gauntlet/</ref> The myth that copyright organizations still pursue lone filesharers persists, in part due to CUIT leaving antipiracy posters up in most computer labs.
+In late 2008, the RIAA and MPAA ceased their antipiracy strategy of suing individual users,<ref>http://www.wired.com/business/2008/12/riaa-says-it-pl/</ref> partially because [[Harvard|braver universities]] announced they would no longer hand over student information voluntarily.<ref>http://arstechnica.com/tech-policy/2009/02/tell-the-riaa-to-take-a-hike-how-harvard-law-threw-down-the-gauntlet/</ref> The myth that copyright organizations still pursue lone filesharers persists, no thanks to CUIT leaving harshly-worded antipiracy posters up in most computer labs.
 Although large rightsholder organizations no longer pursue students, CUIT still takes it upon itself to penalize filesharers.

@@ Line 24: / Line 24: @@
 == Legal risks ==
-In late 2008, the RIAA and MPAA ceased their antipiracy strategy of suing individual users,<ref>http://www.wired.com/business/2008/12/riaa-says-it-pl/</ref> in part because [[Harvard|braver universities]] announced they would no longer hand over student information voluntarily.<ref>http://arstechnica.com/tech-policy/2009/02/tell-the-riaa-to-take-a-hike-how-harvard-law-threw-down-the-gauntlet/</ref> The myth that copyright organizations still pursue lone filesharers persists, in part due to CUIT continuing to display antipiracy posters in most computer labs.
+In late 2008, the RIAA and MPAA ceased their antipiracy strategy of suing individual users,<ref>http://www.wired.com/business/2008/12/riaa-says-it-pl/</ref> in part because [[Harvard|braver universities]] announced they would no longer hand over student information voluntarily.<ref>http://arstechnica.com/tech-policy/2009/02/tell-the-riaa-to-take-a-hike-how-harvard-law-threw-down-the-gauntlet/</ref> The myth that copyright organizations still pursue lone filesharers persists, in part due to CUIT leaving antipiracy posters up in most computer labs.
 Although large rightsholder organizations no longer pursue students, CUIT still takes it upon itself to penalize filesharers.

@@ Line 24: / Line 24: @@
 == Legal risks ==
-=== RIAA legal action ===
+In late 2008, the RIAA and MPAA ceased their antipiracy strategy of suing individual users,<ref>http://www.wired.com/business/2008/12/riaa-says-it-pl/</ref> in part because [[Harvard|braver universities]] announced they would no longer hand over student information voluntarily.<ref>http://arstechnica.com/tech-policy/2009/02/tell-the-riaa-to-take-a-hike-how-harvard-law-threw-down-the-gauntlet/</ref> The myth that copyright organizations still pursue lone filesharers persists, in part due to CUIT continuing to display antipiracy posters in most computer labs.
-=== MPAA legal action ===
+Although large rightsholder organizations no longer pursue students, CUIT still takes it upon itself to penalize filesharers.
 === Detection ===
@@ Line 36: / Line 34: @@
 If the user was logged on in a [[computer lab]], CUIT compares the IP to a time log and can therefore still identify the particular user.
 === Avoiding detection ===
 Some file sharers try to avoid detection by connecting to file-sharing networks via another computer (a proxy). The user can then connect to file-sharing networks and use the internet as normal, except that the IP address by which their computer is visible to these networks is that of the other computer (the proxy). This way, if the RIAA or MPAA or some other organization wants to make a claim, they will address it to the proxy rather than the end-user file-sharer. This is useful if the proxy is in a jurisdiction with lax copyright laws like Sweden. By connecting to file-sharing networks via a Swedish proxy, it is almost impossible for any such organization mentioned above to make a claim against the user.
-Some file sharers also avoid detection on the Columbia [[wifi]] network by changing or "spoofing" their MAC address once their previous MAC address has been identified as violating copyright.<ref>http://www.klcconsulting.net/change_mac_w2k.htm</ref> It is unclear whether this is legal. However, students who do it generally don't care because there is no easy way for CUIT to learn whether your MAC address is genuine or spoofed.
+Some file sharers also avoid detection on the Columbia [[wifi]] network by changing or "spoofing" their MAC address once their previous MAC address has been identified as violating copyright.<ref>http://www.klcconsulting.net/change_mac_w2k.htm</ref> It is unclear whether this is legal. However, students who do it generally don't care because there is no easy way for CUIT to learn whether your MAC address is genuine or spoofed. In 2011, an anonymous Columbia redditor released an initial guide to doing so <ref>http://www.reddit.com/r/columbia/comments/kh9kp/a_simple_explanation_of_how_busting_torrenters/]</ref>
 Others use public network jacks in the libraries and classrooms. These cannot be traced to individual users unless CUIT tries to match UNI login records (eg, for [[Cubmail]], [[Courseworks]], or [[SSOL]]) with connection records.

← Older revision		Revision as of 04:30, 22 November 2012
Line 59:		Line 59:
	== External links ==		== External links ==

−	[[Category:IT]]	+	[[Category:File sharing\|*]]

@@ Line 18: / Line 18: @@
 == Bandwidth limitations ==
-Almost every node on the Columbia network is restricted to downloading 2000 MB per hour and uploading 700 MB per hour. A 700 MB movie would take 45 minutes to download going at maximum speed on the Columbia network, or about 2.5 hours at throttled speed. Users who exceed the above limits are restricted to a severely throttled bandwidth for between 20 minutes and 4 hours depending on how much they went over the limits. The throttled bandwidth is extremely slow; only fast enough for slowly surfing basic web pages. Thus, if you plan to download a large file, you may want to limit your download speed to 275 KB/s and your upload speed to 95 KB/s.
+Almost every node on the Columbia network is restricted to downloading 2000 MB per hour and uploading 700 MB per hour. A 700 MB movie would take 45 minutes to download going at maximum speed on the Columbia network, or about 2.5 hours at throttled speed. Users who exceed the above limits are restricted to a severely throttled bandwidth for between 20 minutes and 4 hours depending on how much they went over the limits. The throttled bandwidth is extremely slow; only fast enough for slowly surfing basic web pages. Thus, if you plan to download a large file, you may want to limit your download speed to 570 KB/s and your upload speed to 200 KB/s.
 Bandwidth limits are currently only applied from 10am to midnight. So from midnight to 10am, you can download at unrestricted speeds, up to four times faster than the restricted speeds mentioned above. In practical terms, this means you can download up to 3.5 GB per hour, equivalent to about 1 MB/s. You can also upload at similar speeds.