Tube FHGs - would you want one long video or 3 shorter ones on a FHG?

here let me start things off:


"Oh yes, I prefer 1 long trailer because it's closer to a tube experience and that way I can kinda have a mgp with tube galleries so I don't have to really change what I do but kind of have a hybrid model"

I think alot of my clients that use TEVS would prefer 3-4 clips merged into 1 larger (1 min) clip.

Cheers, it's not really about TEVS or tube script users though. I understand that scraping the gals and getting it into an actual tube site like TEVS would mean 1 longer clip is better, but we already offer the longer one hosted as an option. I'm talking more about your general TGP/MGP owner wanting to put flv type gals on their site.

so more like 3 short flvs like:
http://myteenvideo.com/flash/perfect...6Mw,0,0,0,6252

or 1 big flv (pretending it doesn't have everything and the kitchen sink like this particular one) like:
http://www.freedpxxx.com/fhgs2/mgp/8...zoy,0,0,0,1010

Bump, I would like to know this myself.

Oh well, people will just have to make do with what we give.

one clip please

What I've done with the claudia-marie.com hosted galleries is I put 2 1 minute long .flv's and 6 .jpg's on each gallery. I also write different verbiage for each gallery and "seo" it up a bit with different alt tags for each image and gallery.

I'll tell you another advantage of .flv over .wmv galleries. Earlier this year claudia-marie.com was getting shut down from an attack. And what the guy was doing was he was hitting every .wmv on my tour trailers and hosted galleries.

So to try and stop that we put in a script to allowed an ip to watch a .wmv in the tour area 3 times within a 24 hour period.

Then we found out that windows media player requires THREE requests to play ONE time!!!

Had no idea about that. So that mean that each of the thousands of ips that were hitting us were still allowed 9 times for EACH trailer and vid clip on galleries. So we were still running bandwidth and shutting down the network card and overloading the cpu on the server.

So then we started a random re-name of every .wmv on the server every 30 minutes. So every 30 minutes the .wmv's were all individually renamed and the .html was changed to reflect it.

That worked for about a day. Then the jackass changed his bot's script to compensate.

Really pissed me off.

Finally I sat down and re-encoded EVERY .wmv on the server over to a .flv by hand. It took me a LOT of time and work. And no, I didn't want to do it server side...though we tried it, and the vids looked like shit. So I sat down with Adobe Premiere Pro and did it by hand to ensure quality. And then did all the html by hand just to make positively 10000000% sure that it was right.

Too much money to rely on a script.

Well sir, that fixed the problem. FLV's are "one request/one get" And then if the user wants to watch it again...it's cached.

So anyway...you don't need to be ddos attacked to understand that .flv = ONE request .wmv = THREE requests

That's good food for thought. Thanks Robbie!