GUROchan is using more bandwith than the current hos is allowing, which means it's time to move to a payhost. I need to find a good host that allows guro and has enough (which means lots) bandwith at a fair price.
Cyrillthefish is using DreamHost, they have this "triple the bandwith"-offer that looks like a good deal. Guro doesn't crash with their ToS, it seems.
Does anyone reccommend any other hosts, or should I go with DreamHost?
People seem to be cautiously optimistic about DreamHost. As I recall, they only have Perl 5.6, but with the latest Wakaba and Kareha versions this should not be a problem any more.
...however, you were running Wakaba Zero, right? If you want to copy that over it won't work... Hmm. On Dreamhost, you can run the full Wakaba instead, but then you can't get the old posts copied over.
It might be possible to fix up Wakaba Zero to work on Perl 5.6, though. If you really want that, then I might give it a shot.
Naruhodo...
Actually, I was planning to upgrade to the full Wakaba, so you don't need to bother fixing Wakaba Zero.
If the old Perl version is DreamHost's biggest problem, I'll probably use them.
No complaints about DreamHost so far. My SQL server was down for a while once, but after I submitted a trouble ticket, it came back up right quick. The old Perl didn't break older versions of Wakaba either...
It did, but you just didn't notice because the only thing that broke was unicode in the name cookie. The new version works around this, though, so not even that rare case is a problem.
As for dreamhost hosting the only problem i've had is the 'caching HTML' thing they do, so if someone posts something it won't show up for a few minutes :(
apart from that the service is absolutelutely faultless. silly amounts of bandwidth for hardly anything at all (i worked out i'm paying more per GB on my 1mbit ADSL account than i do for dreamhost :O)
>>7: I've never had this caching problem...
I had the caching problem with piichan and cyril.dreamhost.
Basically, if I upload something, I have to refresh manually to see it unless somebody else has posted something new until then.
Odd, I never had that problem... Then again, Safari's caching system is rather jacked. Would it be fixed by a "no-cache" (or whatever it's called) pragma tag in the template?
It might, but I've not put it in there because I hear it causes problems with IE (such as not caching thumbnails).
Sending a Pragma: no-cache header is better, but on hosts that don't let you do that, it's a problem.
I believe it was Vary: * that IE couldn't handle, not no-cache, although it's possible. It's no big secret that IE generally has a broken caching mechanism.
This is what was used for IIchan. I put several hours of research and testing into it, and we never had complaints once it was implemented:
<Files *.html>
Header add Expires "Mon, 26 Jul 1997 05:00:00 GMT"
Header add Pragma "no-cache"
Header add Cache-Control "max-age=0; must-revalidate; no-cache"
Header unset Vary
</Files>
It's a sledgehammer approach, but should work on pretty much every broken browser, proxy, etc out there. I tried implementing something similar in the HTML of /os/ and /mai/ (host didn't like mod_headers, gah) as well, and haven't heard anyone gripe about it.
Elsewhere some people have noted that IE works better if you put the expiration meta at the end of the HTML. For example:
<html>
<body>
blah blah
</body>
<head>
headers
</head>
</html>
I haven't tested it though, so YMMV.