URL Shortening service Bit.ly announced new partnerships with Google (Reader) and Typepad together with a new API yesterday. Most interesting news though was the future integration of ‘upload-images-to-twitter’ service yfrog, the ImageShack service.
As for the upcoming features that we’re working on… we’re pleased to announce that one is them is a new way to use bit.ly. In partnership with yfrog, we’ll be rolling out a shortcut to let you upload and share photos from the bit.ly homepage. Bit.ly links will also be available for all yfrog images.
After Twitter’s decision to integrate bit.ly as standard URL sthortener and now the Google (Reader) collaboration it seems that bit.ly has won the ‘Battle of the URL Shorteners’ for good. The question to ask now is: where does this leave Twitpic, the first ‘image-to-Twitter’ service and still leader in the race.
Picking the right URL shortener for your links is obviously important, especially now that the fact that they might not be around for as long as you might like has dawned on people. Naturally you should roll your own, but failing that, it might be interesting to know that Bit.ly and Ow.ly are the most reliable ones. At least according to a reliability report from Pingdom. I must say, I was a bit surprised to see Ow.ly up on top, it has had some downtime in the past but have obviously got its act together. In fact, it was the only one with 100% uptime.
Be sure to read the whole thing. It is pretty interesting after all.
Do we really need yet another URL shortener service? I guess we do, if nothing else but to get even shorter URLs for our slightly compulsive microblog link pushing. The most recent one is to.ly, created by Jonas Lejon, who also did the Twitter backup service. So why did he venture into URL shortening? Aren’t the competition good enough?
I’ve got so many crazy ideas about what is possible to do with an URL shortening service and I needed to use one for my projects. Also, I couldn’t find any PHP code examples on any of the popular services.