Richard Lyman wrote:
Please don't 'bittorrent-only' anything. There are those of use who
aren't involved in Bittorrent-anything.Thanks!
-Rich
What are the reasons people do not use bittorrent?
I'm thinking of torrent-only for any videos served from ruby-doc.org, as it seems like a good solution for controlling bandwidth and sharing distribution.
James
Does anyone have, or know of, snake-simple instructions on how to host
large files in a public server, making them available only through
bittorrent.I poked around, and can see how to make a torrent file, and then get
that torrent file to a tracker, but I gather from this that the target
file is expected to be available form my PC, and only when I run a
bittorrent client. I want to serve the files form ruby-doc.org, not my
home box.
On the ruby-doc.org server, you would upload the file and its
corresponding torrent to a private area, then run
btdownloadheadless.py on the torrent file.
There also has to be a tracker involved, which should also probably
run on the ruby-doc.org server.
I use screen or its simple incarnation, dtach, to run bittorrent
downloads (and uploads; they are the same thing)
Ari
Does anyone have, or know of, snake-simple instructions on how to host
large files in a public server, making them available only through
bittorrent.
I followed the docs in the Python BT implementation
(Bram’s Thoughts | Bram Cohen | Substack), and there's a guide
to it here:
I poked around, and can see how to make a torrent file, and then get
that torrent file to a tracker, but I gather from this that the target
file is expected to be available form my PC, and only when I run a
bittorrent client. I want to serve the files form ruby-doc.org, not my
home box.
Yup, per Ari's email, you can run a BT peer on ruby-doc.org itself.
I expect that I will need to run a tracker on the server hosting the
files. Is this what RubyForge does?
Yup, right on. I suppose you could simply use RubyForge's tracker; that
should work, I think.
This is off-topic for Ruby in general, but handy info as large
Ruby-related files become available.
BT is good stuff. Ikkei and I are working on a BT Ruby library here -
http://aversa.rubyforge.org/ - so look for more BT jibber-jabber in the
future.
Yours,
Tom
On Thu, 2004-09-09 at 12:34, James Britt wrote:
I've never used BT before and don't even know what it is. But if
someone wants to save bandwidth, that's their prerogative. I'll
learn. Of course, someone else _might_ put the files up in full.
My suggestion: make the recordings available on CD for $X, money going
to RubyCentral to help cover costs of the conference (and make a
little on the side).
Not mutually exlusive, but I'd rather pay a fee to a worthy cause than
slave over a download manager.
Cheers,
Gavin
On Friday, September 10, 2004, 2:17:18 AM, Richard wrote:
Please don't 'bittorrent-only' anything. There are those of use who
aren't involved in Bittorrent-anything.
Thanks!
-Rich
On Fri, 10 Sep 2004 00:35:42 +0900, Chad Fowler <chadfowler@gmail.com> wrote:
On Fri, 10 Sep 2004 00:08:22 +0900, Richard Kilmer <rich@infoether.com> wrote:
> We are going to have my buddy's audio mixing board, a wireless mic, and a
> pre-amp. We can run the board into a camera also directly into a laptop to
> record directly to MP3. I am gonna try and confirm borrowing a projector,
> since my company does not own one itself. So, we will be set this year re:
> getting solid recordings of the talks and be able to post things up quickly.
> Actually, getting a list of sites before hand that would host these MP3's of
> the conference would make it far easier to post quickly.
>We can obviously put them on the rubyconf website, though I'm thinking
this is a good bittorrent-only kind of thing.Chad
>
> On 9/9/04 8:49 AM, "Gavin Sinclair" >> <gsinclair@soyabean.com.au> wrote:
>
> >
> > That being the case, is it possible to try and get plain audio
> > recordings as well? I mean, shoot for video, but someone else can be
> > recording audio, which will be better than nothing if the video
> > doesn't turn out well.
> >
> > Cheers,
> > Gavin
>
>
He's probably right, but you should never listen to a Kiwi on Aussie
pronunciation, or vice versa. But especially the former 
Gavin
On Friday, September 10, 2004, 6:09:04 AM, Joel wrote:
Plus the two two can be muxed (is that the right word?) [...]
If you're from New Zealand
Gavin
Hehe.
And if you're from Australia, is it "meexed"?
(I knew a math grad student from NZ who said that 6 is pronounced
"seeks" in Australia, but "sucks" in NZ.)
fear of having to learn a new tech
lack of knowledge/experience
lack of time to find/learn about new tech
lack of machine resources (ok, that's a pretty 'old' answer)
at one time or another, I've suffered from combinations of the above.
by random chance, I've recently installed a BT app, so this isn't one
of those cases
On Fri, 10 Sep 2004 01:38:34 +0900, James Britt <jamesunderbarb@neurogami.com> wrote:
Richard Lyman wrote:
> Please don't 'bittorrent-only' anything. There are those of use who
> aren't involved in Bittorrent-anything.
>
> Thanks!
>
> -RichWhat are the reasons people do not use bittorrent?
--
Bill Guindon (aka aGorilla)
James Britt wrote:
Richard Lyman wrote:
Please don't 'bittorrent-only' anything. There are those of use who
aren't involved in Bittorrent-anything.Thanks!
-Rich
What are the reasons people do not use bittorrent?
I'm thinking of torrent-only for any videos served from ruby-doc.org, as it seems like a good solution for controlling bandwidth and sharing distribution.
In my case the campus network blocks it, because the admins think that anything P2P is only used for illegal stuff. Although I guess I could download it on another network.
Yup, all you need is a BT client, i.e., Azureus:
Yours,
Tom
On Thu, 2004-09-09 at 12:32, Hal Fulton wrote:
But I thought it was a server-side issue, am I wrong? Shouldn't anyone
be able to access a file served vis BT?
Right on. For the RubyForge torrents (http://bt.rubyforge.org/\), I run
a client on a computer on my home network (connected via DSL). So far -
in about two weeks - my home network has uploaded about 350 MB of
traffic in Ruby torrents. This is good, since that's traffic that
didn't clog up the RubyForge pipes.
Yours,
Tom
On Thu, 2004-09-09 at 13:18, Aredridel wrote:
On the ruby-doc.org server, you would upload the file and its
corresponding torrent to a private area, then run
btdownloadheadless.py on the torrent file.
What are the reasons people do not use bittorrent?
One potential reason is losing seeders in the 'cloud' once something
has been going for a while. On some music related bittorrent sites
there's usually never a shortage of posts like "Can someone seed? I'm
stuck at 97%"
--
Chris
http://clabs.org
Almost invariably for me the problem is firewalling. Opening all of
those ports is usually difficult or impossible to get your network
admin to do. At home I often have a situation where I'm roaming
around the house with a laptop on a wireless DHCP connection, so
setting up port forwarding to go to my dynamic IP is impractical.
On Fri, 10 Sep 2004 01:38:34 +0900, James Britt <jamesunderbarb@neurogami.com> wrote:
Richard Lyman wrote:
> Please don't 'bittorrent-only' anything. There are those of use who
> aren't involved in Bittorrent-anything.
>
> Thanks!
>
> -RichWhat are the reasons people do not use bittorrent?
I'm thinking of torrent-only for any videos served from ruby-doc.org, as
it seems like a good solution for controlling bandwidth and sharing
distribution.James
I think both CDs and Bittorrents should be available. Otherwise,
folks who are curious about ruby aren't going to watch them. They
won't want to pony up cash to support a cause that they don't believe
in yet.
On Fri, 10 Sep 2004 06:56:01 +0900, Gavin Sinclair <gsinclair@soyabean.com.au> wrote:
I've never used BT before and don't even know what it is. But if
someone wants to save bandwidth, that's their prerogative. I'll
learn. Of course, someone else _might_ put the files up in full.My suggestion: make the recordings available on CD for $X, money going
to RubyCentral to help cover costs of the conference (and make a
little on the side).Not mutually exlusive, but I'd rather pay a fee to a worthy cause than
slave over a download manager.Cheers,
GavinOn Friday, September 10, 2004, 2:17:18 AM, Richard wrote:
> Please don't 'bittorrent-only' anything. There are those of use who
> aren't involved in Bittorrent-anything.> Thanks!
> -Rich
> On Fri, 10 Sep 2004 00:35:42 +0900, Chad Fowler <chadfowler@gmail.com> wrote:
>> On Fri, 10 Sep 2004 00:08:22 +0900, Richard Kilmer <rich@infoether.com> wrote:
>> > We are going to have my buddy's audio mixing board, a wireless mic, and a
>> > pre-amp. We can run the board into a camera also directly into a laptop to
>> > record directly to MP3. I am gonna try and confirm borrowing a projector,
>> > since my company does not own one itself. So, we will be set this year re:
>> > getting solid recordings of the talks and be able to post things up quickly.
>> > Actually, getting a list of sites before hand that would host these MP3's of
>> > the conference would make it far easier to post quickly.
>> >
>>
>> We can obviously put them on the rubyconf website, though I'm thinking
>> this is a good bittorrent-only kind of thing.
>>
>> Chad
>>
>>
>>
>> >
>> > On 9/9/04 8:49 AM, "Gavin Sinclair" > >> <gsinclair@soyabean.com.au> wrote:
>> >
>> > >
>> > > That being the case, is it possible to try and get plain audio
>> > > recordings as well? I mean, shoot for video, but someone else can be
>> > > recording audio, which will be better than nothing if the video
>> > > doesn't turn out well.
>> > >
>> > > Cheers,
>> > > Gavin
>> >
>> >
>>
>>
Sorry, didn't catch your "not mutually exclusive."
On Fri, 10 Sep 2004 06:56:01 +0900, Gavin Sinclair <gsinclair@soyabean.com.au> wrote:
Not mutually exlusive, but I'd rather pay a fee to a worthy cause than
slave over a download manager.
Torrent is a good way yes, but I would only consider
torrenting as an alterior means for downloading
software for alternate site transfers. It just looks
unprofessional in a way if you know what I mean.
--David Ross
--- James Britt <jamesUNDERBARb@neurogami.com> wrote:
Richard Lyman wrote:
> Please don't 'bittorrent-only' anything. There are
those of use who
> aren't involved in Bittorrent-anything.
>
> Thanks!
>
> -RichWhat are the reasons people do not use bittorrent?
I'm thinking of torrent-only for any videos served
from ruby-doc.org, as
it seems like a good solution for controlling
bandwidth and sharing
distribution.James
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail
Tom Copeland wrote:
> On the ruby-doc.org server, you would upload the file and its
> corresponding torrent to a private area, then run
> btdownloadheadless.py on the torrent file.Right on. For the RubyForge torrents (http://bt.rubyforge.org/\), I run
a client on a computer on my home network (connected via DSL). So far -
in about two weeks - my home network has uploaded about 350 MB of
traffic in Ruby torrents. This is good, since that's traffic that
didn't clog up the RubyForge pipes.
Please excuse my ignorance as I know next-to-nothing about BT...
If I installed the BT client you recommended on the server on my hom network
(also DSL), is that all I need to do? Or do I also need to use that client
to download the files that I want to help serve?
Thanks,
Curt
On Thu, 2004-09-09 at 13:18, Aredridel wrote:
Yup. Hopefully a few folks could keep Ruby-related seeds running most
of the time. Anyone who's got a home DSL or cable modem could share a
few megs a day... shouldn't be too burdensome since most BT clients
allow you to regulate how much data goes out...
Tom
On Thu, 2004-09-09 at 14:26, Chris Morris wrote:
One potential reason is losing seeders in the 'cloud' once something
has been going for a while. On some music related bittorrent sites
there's usually never a shortage of posts like "Can someone seed? I'm
stuck at 97%"
Bill Guindon wrote:
James Britt wrote:
What are the reasons people do not use bittorrent?
fear of having to learn a new tech
lack of knowledge/experience
lack of time to find/learn about new tech
lack of machine resources (ok, that's a pretty 'old' answer)at one time or another, I've suffered from combinations of the above.
I have termed this "aggressive incompetence" based on some comments made
by one of the Dave Thomases a couple years ago in the XP mailing list,
http://groups.yahoo.com/group/extremeprogramming/message/55146
Yahoo | Mail, Weather, Search, Politics, News, Finance, Sports & Videos
I have found the phrase to be extremely provocative, powerful, and
motivating.
Regards,
--
Bil Kleb, Hampton, Virginia
True, although in both these situations you can leave the BT client
running and it'll connect to folks who have port 6881 open. I've shared
about 10 GB of the Fedora ISO images in the few weeks by doing that...
Yours,
Tom
On Thu, 2004-09-09 at 16:21, Carl Youngblood wrote:
Almost invariably for me the problem is firewalling. Opening all of
those ports is usually difficult or impossible to get your network
admin to do. At home I often have a situation where I'm roaming
around the house with a laptop on a wireless DHCP connection, so
setting up port forwarding to go to my dynamic IP is impractical.
Chris Morris wrote:
What are the reasons people do not use bittorrent?
One potential reason is losing seeders in the 'cloud' once something
has been going for a while. On some music related bittorrent sites
there's usually never a shortage of posts like "Can someone seed? I'm
stuck at 97%"
Um, what does this mean in English?
Assuming that the file is served from the same machine as a tracker and the torrent file, is this a problem?
Thanks,
James
There was something posted to slashdot a few months back about a service
that would cache and serve up large files for you.
Something like Coral [http://www.scs.cs.nyu.edu/coral/\] (which would
work too, but this one was specifically for serving up large files)
martin
Carl Youngblood <carl.youngblood@gmail.com> wrote:
Almost invariably for me the problem is firewalling. Opening all of
those ports is usually difficult or impossible to get your network
admin to do. At home I often have a situation where I'm roaming
around the house with a laptop on a wireless DHCP connection, so
setting up port forwarding to go to my dynamic IP is impractical.