Home » Media, Ramblings

Twitter. Again.

30 May 2008 4 views 4 Comments

I know hundreds of keen Twitter users. We’ve been there since the start, and loved it all the way. However, it seems that now the huge media boom surrounding it, and other social networking systems, it’s struggling to keep up. Constantly being bombarded with excuses, errors and more does not help its user-count.

image

It’s a classic case of the developers doing the business-man’s job. Having received over $80 million in funding, and still unable to afford scalable servers is quite frankly a scare.

Twitter’s always been built on Ruby, from the start, but, as the web developers know, Ruby/Rails was never designed to scale to such huge numbers. Even Twitter themselves know that! The question is, why are they refusing to rewrite? Ruby/Rails isn’t the only AJAX-enabled engine in the world, and it wouldn’t be hard to rewrite.

It’s not just the technology. There’s been a huge row between users recently, when Twitter allegedly refused to uphold their own Terms of Use, for fear of legal issues (considering there could have been a legal issue from either party). Link.

image

Solutions

  1. Rewrite. This is the most obvious way out of this mess. They could switch to a more stable environment. Obvious? Apparently not. There are reasons why a rewrite is impractical in the short term.
  2. Local servers. Having a central (Ruby) server clearly isn’t working. Why don’t they do what all other international platforms do, which is to hold a data bank, that one server per continent takes data from, periodically? This will speed up access time, and reduce server load 10 (-ish) fold.
  3. More servers. They can afford it! A simple upgrade of machines would go a great deal further than constant errors.
  4. Restrict use. Oh my goodness. They’re on the verge of this already. They’re already shutting down features on a temporary basis. You may be thinking, "oh no, how can we live without pagination?" in a semi-sarcastic manner, but you may not have noticed the 30 refreshes/hour limit on the API. This is not a solution, Twitter.

image

Anyway, what’s your take on this? Have you got any more solutions? Edit: Those that don’t involve (that much) violence, thank you commenters.

P.S. http://www.twitter.com/lawrencejob

1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)
Loading ... Loading ...

4 Comments »

  • Keehun Nam said:

    You know, in my opinion, I think twitter knows what its doing, and let’s just be patient. Imagine: a kid needs to fall countless times in order to walk, and to learn how to run well. Twitter hasn’t fallen before, and let’s hope this fluke will make them immune from anything else in the future.

  • Lawrence (author) said:

    You have a point, Keehun, and it really makes your previous Tweets make a whole lot more sense. How many times must it fall before it can be considered countless though?

    It regards itself as a communication tool, not a Social Network. Did BT (AT&T, for you) collapse at the first, second and third hurdle?

  • Keehun Nam said:

    But guess what, Twitter fell for the first time!
    And are you comparing AT&T and Twitter? If you gave Twitter AT&T’s resources (staff, funding, etc) Twitter would take over the world.

  • Lawrence (author) said:

    Assumed you’d read it, before commenting:

    We have deleted accounts for more straightforward violations of the existing Terms. That being said, we are engaged in an editorial review of those Terms to make it more clear what actions we will and won’t take. Essentially, Twitter is a communication utility, not a mediator of content.

    They refuse to accept this this website is a social network. That is one example. They see themselves as a communication tool, they do compare themselves to AT&T at one point.

Leave your response!

Add your comment below, or trackback from your own site. You can also subscribe to these comments via RSS.

Be nice. Keep it clean. Stay on topic. No spam.

You can use these tags:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

This is a Gravatar-enabled weblog. To get your own globally-recognized-avatar, please register at Gravatar.

Related Posts from the Past: