(2009-05-13) Making Url Shortener Unnecessary For Twitter

Had an idea for making Url Shortener-s like BitLy unnecessary for Twitter.

Is it fair to say that people receiving a tweet via SMS aren't going to be in a position to click on a link in that "client"? Therefore the "users" of a URI are in a richer/fatter environment? Plus, given various constraints, isn't it OK to force/assume a max of 1 URI per tweet? And even force that to be the last thing in the tweet?

So why not carry that URI as a second payload, and keep the "main" payload at 140chars. And even take a couple chars to use for a special flag to include in the main message signifying the association of a URI?