Twitter’s big Thursday afternoon crash (ongoing for us as of 1:20 p.m. EDT) produced a weird landing page that sent Tumblr users into a screencapping frenzy, in part because unless you’ve programmed in or studied Ruby on Rails, the programming language upon which Twitter was originally built, you probably won’t recognize blank Ruby variables like “<%= reason %>” or “<%= deadline %>.”
Reactions ranged from Debby in Germany, who took the opportunity to abuse Twitter with profanity:
It appears that the Internet is greatly enjoying fucking with us today. Earlier this morning, Gchat experienced an outage, and as of 20 minutes ago, Twitter went dead. Strangely, obsessively refreshing does not fix the problem, and yields only a sad “This webpage is not available” message from our browser of choice (Chrome, duh).
The Twitter Status blog updated 19 minutes ago with the following message:
Users may be experiencing issues accessing Twitter. Our engineers are currently working to resolve the issue.
Seven users have somehow managed to tweet this message, through a method we can only describe as black magic.