Agreed. I have gobs of bandwidth that I'm not using as well as storage space.

All cool cheers guys.

 

Think iTunes uses a single RSS feed for podcast. I have only created these using a single folder holding all episodes.

 

Sure we can work it out as required though :)

 

cheers

My bandwidth limit is bigger than your bandwidth limit. :>

Can also do monitoring/limiting/etc, so yeah, we could do a CDN/mirror thing and definitely not have anything to worry about.


http://www.transmissionbt.com/
or
https://en.wikipedia.org/wiki/Comparison_of_BitTorrent_clients


It's no less iffy than running an FTP program when you're on-site or at work.

Torrenting is a perfectly valid tech for distributing load and downloading files whilst responding to changes in network speed.

Anyway, no reason why we can't have both traditional mirrors, as well as [at least one] permanent torrent seed, and let people use whichever method they prefer. Options good. :)

I agree, I think it makes sense to have both a traditional http feed, but also a torrent feed. It should reduce the server bandwidth a lot if Teh members all use the torrent, but also means the podcast can be served to itunes.etc.