and YFrog team up. What does this mean for Twitpic?

Filed as News on August 26, 2009 3:55 pm

bitlylogo2.pngURL Shortening service 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 In partnership with yfrog, we’ll be rolling out a shortcut to let you upload and share photos from the homepage. links will also be available for all yfrog images.

After Twitter’s decision to integrate as standard URL sthortener and now the Google (Reader) collaboration it seems that 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.

Tags: , , , ,

This post was written by

You can visit the for a short bio, more posts, and other information about the author.

Submissions & Subscriptions

Submit the post to Reddit, StumbleUpon, Digg or

Did you like it? Then subscribe to our RSS feed!

  1. By Jeffro posted on August 26, 2009 at 4:20 pm
    Want an avatar? Get a gravatar! • You can link to this comment

    Whenever I take photos with my iPhone, I generally always use TwitPic first and if it doesn’t work, I then use Yfrog. I’ll continue to use TwitPic until it disappears or i can’t access it from my phone any longer.


  2. By Franky Branckaute posted on August 26, 2009 at 4:35 pm
    Want an avatar? Get a gravatar! • You can link to this comment

    I’m in the same boat, Jeffro. All Twitter apps I have are set to use Twitpic and I will continue to do so. I also think that Bit’ly’s popularity is overblown. I would love to know how many people actually use from the site itself.


    Your words are your own, so be nice and helpful if you can. If this is the first time you're posting a comment, it might go into moderation. Don't worry, it's not lost, so there's no need to repost it! We accept clean XHTML in comments, but don't overdo it please.