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.
Too bad.
Tho, after this point, I say good riddance. EVERY time something goes wrong with /b, the /b collective goes APESHIT and throws a massive tantrum, and a wave of spam spreads across the boards.
Well it's finally dying down. Your average internet troll has an attention span of about that of a small 2 year old. REMARKABLY focused for a time, then ooooh, shiny.
They're losing steam, the ones who don;t know how to cheat bans are already removed by now, and while there's still some spam, but it's slowing as they are cut off. Do we really want /b back? Do we really need a place to post pics of gaping open head wounds with the caption 'I'd fuck that'? Sure, /b served to corral them, but it was also a swamp for the breeding of new retardism. Is it really such a bad thing to let it go? They'll eventually start to gather somewhere else, but for now, who needs that much freak in one place?
Name:
Anonymous2009-05-11 10:59
you can firewall and bake cookies all you like, but there's still moar water than the tubes can handle
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. ^^
>>10
Stop bringing Peter Noone into this. I'm quite sure he doesn't appreciate it.
Name:
Anonymous2009-05-11 16:33
From status.4chan.org:
Apparently the DDoS attack is being caused by a trojan some 4chan users have downloaded. If you've downloaded ANY FILES linked on 4chan, please immediately go to this link and download the removal tool: Trojan.Vundo Removal Tool @ Symantec. Otherwise, all users are encouraged to run a full system scan to ensure their system is clean. The sooner people do this, the sooner /b/ & /r9k/ will return.
>>12
I cannot believe that people were actually that stupid to download this shit.
Name:
Anonymous2009-05-11 17:16
>>12
/b/tards downloading shit that infects their computers isn't exactly new. It provides great ammo whenever someone tries to claim that "/b/tards aren't idiots, they just act like idiots" like /prog/ ;-).
≫⑭
The thing about idiots is that their easily fooled by the „act“ into thinking they belong þair⁎ As a result, ../b/ has been ❪on average❫ sinking further into actual idiocy each yeir⁎ That doesn`t mean they´re isn˅t still some of the most brilliant stuff on the ℹnter–net coming out of it⁎ ❤ ❤
On reflection, I like this more than what I wrote: filter (uncurry (==) . (uncurry ((+) `on` (^2)) *** (^2)) . (liftM2 (,) =<< join (liftM2 (,))) . enumFromTo 1
To convert ((a,b),c) to (a,b,c), you can use (uncurry.uncurry) (,,), but I think it's fine as it is.
That liftA2.liftA2.liftA2 is awesome, confused me for a while.