Site has been down for the past few hours because my poor little shared server can’t handle the slashdot traffic that has recently been pointed at my article on H1N1. On the one hand, I don’t have ads on this blog; on the other hand, it means I can’t afford a server strong enough to handle the occasional slashdot DoS.
I have reconfigured the permalinks and caching behavior in an attempt to bring it back up. If you encounter broken links to this site or if you observe strange behavior, I’d appreciate a note here as to what you are seeing. My impression is that this caching plugin causes the pages to look a little bit nasty at first when you load them when the server is under load, and eventually they get a bit prettier with all the images and backgrounds when things lighten up, but I could be wrong.
Thanks for your patience!
Update: post backlog limited to 5 posts and images removed from the latest name that wares to try and keep server load down. Will restore normal reading settings once the slashdot attack is over.
Update #2 (9/3): I thought the traffic would be down by now but my ISP is still recommending I keep the blog in lock-down with “ugly” pages and no images otherwise they might have to pull the plug again. I’m not particularly fond of tinkering around with the mechanics of wordpress, php and mySQL so I’m just going to hunker down and weather the storm for another couple of days.
Update #3 (9/5): Looks like traffic is down, I’m gradually re-enabling features of the blog. Hopefully, now if you see the blog it should look “pretty” i.e., the header is loading properly and the CSS is being served. I will try turning on images on the front page tomorrow if things are still going well. Thanks for your continued patience.
Update #4 (9/8): I think everything is back to normal after the holiday. Hi-res images should be back now. If you do see anything amiss, please do report it. The backlog of posts shown on the front page is trimmed to 5 instead of the usual 10.
Why don’t you try to use the coral cache?
you could redirect http://www.bunniestudios.com/blog/?p=353 to something like
http://www.bunniestudios.com.nyud.net/blog/influenza
and clone the article to
http://www.bunniestudios.com/blog/influenza
this way the traffic would be served by the coral cache
I was wondering what happened. Things did look messed up at first (I was thinking about taking a screenshot), but things look the way they should now. I also got a 503 error once as well.
I am kind of disappointed slashdot doesn’t coralcache links themselves. or offer to, or whatnot. Also surprised they didn’t find that post ages ago. [Maybe it took it a while past submission? not really recent news though.]
Anyways, Enjoy the added attention, and thanks for the update.
Sorry, Bunnie. I’m the one who submitted the link to Slashdot. (I gave it to Bruce as well, but he’s not as well traveled as /.).
I certainly didn’t mean to cause you pain, but the article certainly was worthy. As for it’s timeliness, well, I guess it took me a while to find it!
Anyway, sorry to DoS you. It wasn’t my intent. And now that I have your attention for 30 seconds or so, I just got “Hacking the XBox” (talk about old news!) and I really have to compliment you on your hardware hacking approach. Very well done!
Best of luck!
pegr