in short, twitter didn't DDoS them, it was the result of all the various bots that look for new urls posted to twitter and fetch them for whatever reason. the

in short, twitter didn't DDoS them, it was the result of all the various bots that look for new urls posted to twitter and fetch them for whatever reason. the article says the "DDos" was "80 requests within the span of 2-3 seconds". if that amount of traffic causes as much trouble to your server as it did for that site (load average of 31, out of swap memory, server reboots), you have a really shitty architecture. it sounds like twitter did these guys a favor by pointing out how poorly engineered their site was. why they posted about it and drew attention to their problem, i have no idea.