I can understand the Firefox extension as being something laudable, sure. But an HTTP API? That seems kind of random, given that the URL shorteners work with 30x HTTP responses. I mean, you just need to request the short URL and read out the Location header of the 30x response. It seems... convoluted to go via an additional server.
Good point - what I've done is allow you to piggyback more than one lookup onto a single request. so the plugin will batch them in groups of 4. does that make sense?
Well, on the server you're still starting N requests based on my batch request. I guess combined with caching that can make sense, yes. Even so, I'd probably want to implement my own [1] when setting up my own web app for reliability/trust reasons, and because of same-origin restrictions on client-side scripting. (XHR does support not following redirects, but it's kind of pointless with same-origin policy)
Yeah, it's only possible on the same hostname as the page you're on, which limits the usefulness and makes the server-side lookup necessary. The JSON solution will only work via a foreign host with a <script> tag as far as I know, which again is something of a trust issue.
I've been using Twitter as part of my blog and have started replacing the href of links with the expanded link. So if you go to my blog or follow me on twitter the links look the same but if you hover on a link the status bar shows the end link.
The Firefox plugin at addons.mozilla.org is messed up (I looked at the contents and found it's an html document). However, the "Benefit right away by installing the firefox plugin" link has a working xpi. Just a heads-up for anyone wondering why they can't install the plugin. :-)
EDIT: Oh, and the statusbar icon is utterly pointless.
sort of related, I wrote a Greasemonkey script to automatically create bit.ly urls as you type a Twitter Tweet. Does it on the fly. Uses the bit.ly API. Check it out at http://userscripts.org/scripts/show/39042
yah.. I wrote it partly to take that ambiguity away.. also seemed a shame to take up some of your 140 characters with a long url, then only to see that Twitter compressed it for you in the saved Tweet, reminding you that you could have typed more :)
on the typing more front words - have you seen tweetshrink? http://tweetshrink.com/ - it'll shorten words like later to l8r to save characters - http://tweetdeck.com have integrated it's api into their twitter client
Yep - looks very similar to what I've done, I hadn't seen it until a few days ago. We could do with even more similar services - to balance out the hundreds of url shrinking services.
http://decenturl.com/
e.g., http://news.ycombinator.decenturl.com/long-urls-please
And a tidbit for the sadistic: http://hugeurl.com/