<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; ">It's really just a matter of changing ports in your torrent client. My university receives a lot of complaints and threats from lawyears every month, but can't do anything to stop it as students just use "safe" ports. They can't see what's a torrent being downloaded and what is academic material :)<DIV><BR><DIV><DIV>On 28. sep. 2007, at 21.57, Laura Scott wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite">This would necessitate some evangelizing and education regarding torrents in general (which I am not against). If we go this way, I'd be happy to draft up a "torrent tips" handbook page to point to background info links. I'd need some help collecting names/links of good clients -- my torrential experience is limited to Azureus/Vuze.<DIV><BR class="khtml-block-placeholder"></DIV><DIV>However, another consideration might be that some ISPs like Comcast and many universities are (rumored to be) blocking torrent packets (under the assumption that if it's a torrent, it *must* be illegal). </DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Laura</DIV><DIV><BR><DIV><DIV>On Sep 28, 2007, at 8:44 AM, Robin Monks wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite">With webseeding, it would be ideal.<BR><BR>Robin<BR><BR><DIV><SPAN class="gmail_quote">On 9/28/07, <B class="gmail_sendername">Tomas J. Fulopp</B> <<A href="mailto:tomi@vacilando.org">tomi@vacilando.org</A>> wrote:</SPAN> <BLOCKQUOTE class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <DIV bgcolor="#ffffff" text="#000000"> Sounds like providing the videos (or any larger files) using the bittorrent is the most advantageous approach. Why not using it since Drupal already has a very good module developed for it?<BR><SPAN class="sg"> <BR> Tomas</SPAN><DIV><SPAN class="e" id="q_1154c880560706c1_2"><BR> <BR> <BR> <BR> Christopher Bradford wrote: <BLOCKQUOTE cite="http://midaca0a0cc0709280719i4f3fecaqbf3d6c6ba3083c1d@mail.gmail.com" type="cite">Hello,<BR> The bittorrent module has an integrated tracker and supports the web-seeding extension. This means two things:<BR> a) The tracker will not have to be run from the command line<BR> b) Should no seeds be available the torrent clients would pull data from the server over HTTP (should the client support it) <BR> <BR> There are two quasi-standards for webseeding (Azureus supporting both). One is the BitTornado spec, which uses a PHP file to retrieve the necessary bytes from the file thus allowing fine grain access control and the ability to throttle. Since it sounds as though the videos would be available to download directly from the server anyway, I would go with the GetRight implementation which uses HTTP byte ranges to query the server directly, eliminating the "middle-man" PHP file, but it loses the access control. <BR> <BR> The documentation for the module is a bit lacking at the moment, but this should be fixed shortly.<BR> <BR> ~Chris<BR> <BR> <DIV><SPAN class="gmail_quote">On 9/28/07, <B class="gmail_sendername">mark burdett</B> <<A href="mailto:mfburdett@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> mfburdett@gmail.com</A>> wrote:</SPAN> <BLOCKQUOTE class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi, for bittorrent you just need a tracker, which you can run from the <BR> command-line on a server, and then a .torrent file for each video (to<BR> generate the torrent file you just need the video file itself and the<BR> tracker url, and pass that into e.g. maketorrent-console).<BR> <BR> I'm not particularly motivated to create the torrents at the moment <BR> since download time for a video seems to be ~30 minutes, or shorter<BR> than the video itself.<BR> <BR> but at least for next time, it would be a good idea to post .torrent<BR> files simultaneously with the videos..<BR> <BR> --mark<BR> <BR> On 9/28/07, Gerhard Killesreiter <<A href="mailto:gerhard@killesreiter.de" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">gerhard@killesreiter.de</A>> wrote:<BR> > -----BEGIN PGP SIGNED MESSAGE-----<BR> > Hash: SHA1<BR> ><BR> > Steven Peck schrieb: <BR> > > Isn't it called bit torrent? :)<BR> ><BR> > Does anybody have experience in setting these up? I've asked OSUOSL and<BR> > they have no experiecne with these things. Neither have I.<BR> ><BR> > Cheers, <BR> > Gerhard<BR> > -----BEGIN PGP SIGNATURE-----<BR> > Version: GnuPG v1.4.6 (GNU/Linux)<BR> ><BR> > iD8DBQFG/KtMfg6TFvELooQRAgjtAJ9insObleczgU3JJ0JwJJujM8oQTACfbYcB<BR> > wqLqm2yP4oglVZTQIJo03wA=<BR> > =Qhth<BR> > -----END PGP SIGNATURE-----<BR> ><BR> </BLOCKQUOTE> </DIV> <BR> <BR clear="all"> <BR> -- <BR> Christopher P. Bradford<BR> </BLOCKQUOTE> </SPAN></DIV></DIV> </BLOCKQUOTE></DIV><BR><BR clear="all"><BR>-- <BR>Robin Monks<BR>@ <A href="http://www.civicspacelabs.org">www.civicspacelabs.org</A><BR>@ <A href="http://www.gmking.org">www.gmking.org</A><BR>@ <A href="http://www.multimediachurches.org"> www.multimediachurches.org</A><BR><BR>Fax: (419) 791-8076<BR><BR>"Finally, my brethren, be strong in the Lord, and in the power of his might." ~ Ephesians 6:10</BLOCKQUOTE></DIV><BR></DIV></BLOCKQUOTE></DIV><BR></DIV></BODY></HTML>