We’ve heard ISP’s limitting off bandwidth from paying users, effectively saying like, “Pay $2 for free flow of soft drink. Oh, btw, the paper cup is made of mahjong paper.” But how do you react when the service is initially free?
Twitter started to grow brains after realizing that they has just become the biggest ircop ever and like the their predecessors before, keeping fludderz at bay is really a PITA. API calls cap is reduced, and was done at the best of all times, the 2010 FIFA World Cup. Timeline flows as loud as the vuvuzelas. Truthfully, this is the best time to fine tune the transaction loads and determine the optimum upper limit count of the Twitter API call. See, fludderz are OK, and you can basicly /ignore them, but traffic is still traffic.
But its free, so why rant about it?
Exactly. You shouldn’t. Nor should I. Its when you become attached to it and start to have a false sense of belonging to the site, you will start to think that the site also owes you. But among these SNS’s, be aware. Facebook really OWNS you! LOL. No, seriously… Bwahahahahaha.
OK, let shut my mouth for a minute and put on my thinking cap. Actually its a good move by Twitter to actually implement a real floating limit (not a bogus limit where it is high enough where 95% of the users will never reach), since it enforces Twitter clients to be more remindful of their calls. This in turn reduces traffic and to an extent, battery life of your mobiles or yuiPhones. For desktop users, use Tweetdeck‘s sliders to balance the intervals between the different API calls (although I don’t use it due to the no Air/.NET policy on my PC). I wish Twit and Seesmic follows. One minute is up.
And so. In the spirit of Let this be a moment in cyberspace, where I name this twitter-api-limit-verb, “twottling”. Use it at your own discretion. And never on an excretion.
I’m a bit jolly tonight due to cough pills. On that bombshell, I wish you good night!!
Leave a Reply