BlackBolt's Journal: Slashcode Redux... Slashdot Fixed? Somewhat?

Just a quick note to all my fellow "Suffering Slashdotters" (not to rip off a Sylvester the cat saying), but I've noticed brief glimpses of greatness here on Slashdot, both last night and today (No, it's not the "iTunes on Windows story, part 6"). Instead of getting one of the great selection of error messages I've recently been getting, I occasionally get -- blinding speed. I can't explain it, but a few pages have loaded at least twice as fast as the old, non-broken Slashdot! Wow.

If this keeps up, I'm gonna have to apologize to someone. If you have any ideas who, please tell me. I'm sure I've offended someone.

Arrrghhhh! Stupid 500 and 64 errors!

[spumoni_fettuccini]

Actually it has been fine for me for the last two days. I gave up on /. for a coupla days and before that struggled through pages for a week and a half or so. /. seems to have improved [back to normal, have not noticed better] in the last few days. I saw in various JE's and some e-mail they were mucking around with the slashcode and it looks like they really jacked up /. for a bit. I'm sure by the time I noticed it they had thousands of e-mails/messages about it so I just bided my time until it was better.

Re:Arrrghhhh! Stupid 500 and 64 errors!

[BlackBolt]

I guess I'm just a late bloomer ;-)

I think this is what you were looking for....

[protogoogoo69]

CmdrTaco just wrote a piece in his journal, "Server Wackiness, Carnivale, G5" [slashdot.org]. He seems to go into detail about the problems you were describing earlier. It doesnt sound like they totally diagnosed the problem yet either.