-
Website
http://mashable.com/ -
Original page
http://mashable.com/2009/01/06/sans-steve-jobs-twitter-still-cant-handle-macworld/ -
Subscribe
All Comments -
Community
-
Top Commenters
-
Robert Basil
142 comments · 8 points
-
Jennifer Van Grove
151 comments · 23 points
-
r0cketman22
317 comments · 52 points
-
rajagiri4
160 comments · 2 points
-
barringtonarch
152 comments · 4 points
-
-
Popular Threads
-
Enter the Zappos Sharing Happiness $3,000 Shopping Spree Giveaway Contest
12 hours ago · 112 comments
-
MySpace Shuts Down imeem and Its App Community
1 hour ago · 8 comments
-
Redbox: The Enemy of the Entertainment Industry? [STUDY]
4 hours ago · 14 comments
-
Your Next Car Radio Might Be Pandora
12 hours ago · 32 comments
-
REVEALED: Details on YouTube’s VEVO Music Video Site
5 hours ago · 12 comments
-
Enter the Zappos Sharing Happiness $3,000 Shopping Spree Giveaway Contest
I noticed a peak delay of around 42 minutes, right now it is down to about 21 minutes.
Typical case of #tweetlag, could be caused by too much activity due to macworld and a switched off fail whale...
Time for a tweetlag measuring app :-)
the right direction! Plus, it's a free service :-)
spike and that was the culprit behind their issues.
This story http://blog.twitter.com/2009/01/dont-blame-geek... links to the reasons for the Twitter issues. I'm not all that highly connected and even I'd read in
Twitter's own service blog, that they were having a (fairly boring) caching
problem, which was ongoing.
I know it is cool to assume that the geeks are the ghost in the machine, but
this tsk-tsking seems snarky and, well, frankly, wrong.
Mollena
A Perverted & Profane Twitter User.
File that you are currently viewing
Linkname: Sans Steve Jobs, Twitter Still Can't Handle MacWorld
URL: http://mashable.com/2009/01/06/sans-steve-jobs-...
Link that you currently have selected
Linkname: Don't Blame the Geeks! | RSS To Twitter
URL: http://rsstotwitter.com/?p=58
->
406 Not Acceptable
Not Acceptable
An appropriate representation of the requested resource / could not be
found on this server.
Additionally, a 404 Not Found error was encountered while trying to
use an ErrorDocument to handle the request.