suksit dot com

So you have seen some screenshots of FireTwitter in my last post, now I will show you the step-by-step guide on how to create FireTwitter.

Before we start, I'd like to mention the reason I write this guide (besides @goodlan's request, of course :P)

Quoted from Twhirl's blog

Twitter mainly is a website that is intended to be used via a web browser, an instant messaging client or SMS. Using these three access points, you are free to fetch information or interact with the service as often as you like, there is no limit imposed.

During this time, where IM interface is not really reliable, and 30 req/hr limit of Twitter's API renders most desktop clients to almost unusable, web interface seems to be the best way to use Twitter. More than that, I think web interface timeline is far more easier to read than in IM, while it can achieve near real-time updates like IM too.

So are you convinced that web interface is cool? :) Anyway, let's get started!

Read the rest of this entry »

As we all know that Twitter is reaching its capacity and has decided to disable IM notification, Pagination, and also reduced the Twitter API request limit to 30 req./hr.

(screenshot from Flickr)

For IM notification, that's fine for me because I rarely use Twitter via IM. The real problem is with the 30 req./hr. limit, which causes Twhirl and all other desktop clients to get the "limit exceeded" every half an hour or so and that's very annoying.

Read the rest of this entry »