I had a little bit of Comcast info I wanted to tweet about, but Twitter went down as I was typing.
Oh, before I forget…
Dear Fucktards at Comcast: Please stop breaking the Internet by replacing valid DNS error messages with search (plus ads!) pages. If any customers want you to break their Internet access, let them opt IN, instead.
Where was I? Oh, right. Twitter.
Twitter has been down for the better part of an hour now, so I went to Facebook to bitch to my meatspace friends and family about not being able to tweet. Turns out Facebook is all kerfucked, too. Attempts to post, to filter who is displayed, or even to load some pages fail with a variety of internal Facebook errors (“AJAX timeout… Are you connected to the Internet?”) or general HTTP failures (“The page at http://facebook.com/ is taking too long to respond…”).
I grumbled to myself, then remembered I run a blog. Moments later I was typing this post and reveling in self-hosted uptime goodness.
Twitter and Facebook = FAIL
TANcast = WIN
PS: If you’re a Comcast subscriber (and oh my <deity>, do I wish there was actual competition in the broadband market), you can fix your DNS behavior by opting out of their fucktacular mess.
PPS: I’ve added “fucktard”, “kerfucked”, and “fucktacular” to my browser’s spell check dictionary.