Twitter event wasn't Cache poisoning; it was poisoned at the authority in charge of their domain. Same as the Comcast hack.
12:36 PM - 18 Dec 2009
0 replies
3 retweets
1 like
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.