Anyway, we're currently okay with monthly bandwidth, but we're eating diskspace like nobody's business. We've been live almost 2 months and we're 44% through our HD storage.
We can upgrade as far as 550MB (we're currently at 154 of 350). But that's more money. And then what?
Well, around 38 MB of this is the archived threads from WX and TT, plus another 10 MB of threads that I haven't even put up yet, so one possible work around would be to put them back where they were, and just point archives@buffista.org at the martzmountain address. The filk site is only about 3 MB, but we could put that back, too, if need be.
As far as the bandwidth issue, one problem seems to be that even if you only hit the 'back' key, php goes back and rebuilds the page from scratch. From what I could see from Googling around on this subject, this is by design, and the fact that it doesn't do it in Opera is considered a bug. The only way around it for other browsers seems to be to use a page caching program at the server. Can we do this? Would this help us?
Hostrocket WILL shut us down and demand more money if we exceed our bandwidth. It's what happened last month to the SaveFarscape / Frell Me Dead forum over on wdsection.com.
We've got a fair amount of people who have webspace of their own. Surely we can get some volunteers and spread the archived threads around so no one person takes too big of a hit.
Now, once we start having to archive Phoenix Board threads, that's probably going to put a dent in searchability, but it's still doable, right?
I have webspace I'm not yet using, because I'm lazy and haven't shifted my site to it. I think I've got 200 megs and a fair amount of bandwidth.
I stand corrected. Dammit.
Re: tagline-character-counting scripts:
we need to have it count hard returns as two characters, not one.
But I fixed that ages ago.
I put a version up for testing at [link] a few days ago.
It gives annoying messages, but just for debugging purposes. It finds the length, then checks for returns and adds one to the length variable for each one it finds.
I just would like it tested on Windows and *NIX computers because I'm not quite sure what "\\r" means on other platforms. We might need to use ("\\r" or "\\n") for instance.
Did you tell me you'd done that? Last I heard, you said you were
going to
do it. I'll check it out.
It's not working on my Windows ME machine. It's still treating returns as one character.
Correction: It's doing something in IE, but not in Mozilla.
Sorry about the confusion. From memory, I said something ambiguous like "want to check it out?".
It's not working on my Windows ME machine. It's still treating returns as one character.
OK so if you put in text with returns, it says "original length x", and then the next dialog that appears says "adjusted length x"?