Wednesday, June 22, 2011 Kung Fooz Itself

You know Bit Ly? Bruce Lee's distant cousin.

I love Twitter, but it's not for everybody and I can understand why some people don't get it or don't like it. One of the things I like is how the 140 char limit forces you to compose your tweet more carefully than you would in email or a blog. Tweeted URL links are counted as chars, so they can become a problem. Whether you use Twitter or not, there are occasions when you would like to replace some cosmologically long URL, like this,-70.423737&spn=0.330804,0.558929&sll=37.0625,-95.677068&sspn=37.819897,72.158203&t=h&z=11 with this That's where URL shorteners come in and there are many shortening services out there.

Until very recently, I had settled on using exclusively for Twitter because it was the first service I became aware of that produced the shortest URLs without going to unicode. is owned by With the recent advent of Twitter auto-shortening, seems to be scrambling to keep users and in that process I suddenly noticed was now being redirected to, which is not as short.

Moreover, was taking much more time to process a URL due to the growing JS eye-candy on their web page, not to mention "processing" your data. I can really see this with my web client bloat-detector: a 1 GHz Power Mac G4.

Finally, I decided to give the chop in favor of Here's why:
  • Not as short as but generally shorter than Tweeter's auto-shortner
  • Tweeter auto-shortner can leave fairly explicit URL fragments
  • Sometimes I don't want to divert attention with the longer Twitter URL string
  • It has much lower JS overhead (Goog KISSes it) which makes for faster translation
  • Goog doesn't need to riffle my wallet for this service
  • Goog was tracking my data anyway :/
So, 再见 (zàijiàn) ... fast as lightning.

No comments: