DISQUS

louisgray.com: http://blog.louisgray.com/2009/06/tweetstats-down-more-than-24-hours-as.html

  • Sheamus · 6 months ago
    I feel bad for TweetStats and it's yet another example of Twitter acting like amateurs over a professional issue, but in the scheme of things it's a relatively minor problem for the bulk of the network, most of whom won't (and didn't) even notice the 'via web' status display.

    Meantime, Twitter's from: search function has been inactive for about 48 hours for a large part of the userbase (and is sporadic for the rest), which seems to have gone generally unreported but is having a much bigger impact, as many folks are not getting a lot of their replies. According to Twitter search, I haven't posted a tweet in the last two days.

    http://search.twitter.com/search?q=from:sheamus

    Which of course is far from true. :) I've had several @s and DMs about it, but it's hard to give a reasonable response when Twitter don't even seem to have realised themselves. Search was "temporarily down" a week ago.
  • Louis Gray · 6 months ago
    These issues all seem minor until you recognize a few things: They have downstream impact, and they point to a pattern. In regards to the issues with Twitter Search, we covered some of those problems in depth over the last few weeks. I was even called "obsessed" just yesterday, so posting again would make some people explode. Here are the previous comments:

    1) Twitter's Search Engine Is Very, Very, Broken
    http://louisgray.com/live/2009/05/twitter-searc...

    2) Twitter's Real-Time Search Hits Pause. Six Hours And Counting.
    http://www.louisgray.com/live/2009/05/twitters-...

    3) Twitter Search is Stuck Again (on FriendFeed)
    http://friendfeed.com/louisgray/fa4570d0/twitte...
  • Sheamus · 6 months ago
    Yeah, I know you covered it at length. :) This is a slightly different development, though. Search itself is working, but the from: function seems to be inactive for a certain percentage, and any external apps that rely on that for @replies are being impacted.

    The point being that Twitter were aware of search being an issue a week ago, then claimed it was fixed, but this is a new thing that, thinking about it, may actually be tied in with their choice to disable part of the system as the timing is probably a bit too coincidental.