Continued img.4chan.org downtime

So, it has been a while and img is still down, presumably powered down to prevent DDoS by a bunch of retards. Now, I I wouldn't normally care about /b/ and /r9k/, but the the truth is that the lost sheep are slowly but certainly seeping into the other boards. The performance hit is already quite noticeable, especially zip is awfully slow and unresponsive at times.

This brings me to question why moot hasn't started to employ some sort of countermeasure. While I realize that DDoS is generally hard to prevent, there should be at least some options depending on the form of attack, like TCP syn cookies, firewalling certain packet types, etc.

Insight into this topic would be much appreciated.

Noone actually gives a fuck that /b/ is down at this point except retards who still haven't realized there are other boards to fag up (I personally use /x/ or 420chan), and the fag(s) behind this who get to fap to "Connection Interrupted" errors eight times a day.  During the first two days or so, there's always the confusion over whether it'll be back soon and we just have to wait it out, or if it's gone long-term and we might as well find somewhere else to hang out semi-permanently in the meantime.

When/if it does come back, someone who knows about that kind of shit will arrange for whoever did it to get ddos'd or spammed or arrested, and I'll cheer them on from the sidelines (especially if it's Kimmo), but mostly I'll just change the button on my bookmarks toolbar back to pointing to /b/ and go back to posting Diaperfur threads. ^^