Don't waste the money. :S

Even if there's not the space/transfer on this server, it takes a few seconds to point podcast.tehforum.co.uk at any server/site you want...

www.podcast.tehforum.co.uk ?

 

that would be the link?

What Pete said.

Bandwidth wouldn't be an issue, we're barely tickling our allowance, but is it wise to start hosting large files (publicly) on Teh and for us to have to suddenly start paying fees if we going over?

Could maybe set up a private torrent tracker on here or some other decentralised distribution platform that we can use. Might even be able to tie it into the Beehive user authentication.

podcast.tehforum.co.uk would be it - no need for extra letters.

Using www is a convention - it has never been required to be at the start of a URL.

Bullshit!!!!

Seriously!?

(goes off to try..)

I really did not know that.
Firefox still adds it in, is it browser dependent? Would older browser not work without www?

Files size are currently about 70 - 100 mb per 1hr - 1.20min episodes

It has nothing to do with the browser* - it is up to the server to handle.

Some servers, if you type domain.com will redirect you to www.domain.com (e.g. http://google.com adds the www )
Others, if you type www.domain.com will redirect you to domain.com (e.g. http://www.stackoverflow.com removes the www )

You may sometimes come across badly configured servers which do fail if they receive the non-www version, but I can't recall any examples of that (it did happen once to me recently, on some site that should have known better, but I forget the specifics.)

*Of course, because it is a convention, some browsers may well sometimes do stuff that involves adding www, but almost certainly what you're referring to is not browser-driven, but the server sending the redirect request. (You can use Firebug's Net panel to see this occur.)

It's server dependent.

Teh redirects you to www because it can, but it doesn't have to.

100mb downloaded 100 times is ~10GB of data transfer, which is 5% of our monthly allowance for one episode.

I don't know how likely getting 1k+ subscribers is, but having some distributed system (like torrents) to spread that load and make sure it's not an issue is probably a good idea.

Didn't know that, cheers

would that still be linkable to itunes etc? I never done torrent setups etc

I've never done torrent setups or iTunes, so haven't got a clue. :P


I might have enough space/transfer on my server - not sure, and have to go now - if a fixed host is needed I'll check the numbers later.

I've got some reseller hosting your welcome to use while you gauge things. I can limit the bandwidth to prevent it running away - I have 500GB a month to play with and barely tickle it really.

 

Don't know how feasible it is in the long term, but as I say, totally happy to help if I can.

 

I wonder if, between that, Teh and anyone else we could fix up a simple CDN. What do you think Matt, could just do it round robin style, or even just random.
 
Edit: I personally dislike the idea of using torrents for this, primarily because I don't have a torrenting program installed and it's a bit iffy running it when I'm on-site or at work.

Dropbox.

how would that work if we wanted to get onto iTunes eventually?

No idea.

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.