I've been using Twitpic either via TwitterFon on my iPhone or Tweetie from my desktop for Twitter, but one thing struck me last night: Twitpic doesn't allow me to get my content back out.
So here's my fix: http://twitpicapi.appspot.com/
Book nowModern Universal React with Next.js
Stop worrying about configuration, and complex codebases: Next.js makes SSR with React easy. Book your masterclass today.
Twitpic JSON API
I've created an API that scrapes the data straight off the Twitpic site to get your images back out.
I've not gone so far as creating integration to Flickr (which actually where I want to put my images), mostly because that exists already.
The JSON API is easy to use, but I've had to limit it to one page at a time (because the backend processing takes too long).
Usage and examples are explained, but it's pretty self explanitary (and it supports JSONP too):
The service will resolve to the original url of your image too, but annoyingly, the title/description isn't always present, since it depends on your client sending it along at the same time (TwitterFon does this, but Tweetie doesn't).
With any hacking I play around with, I've made the project open source, and all the code is available on GitHub here: http://github.com/remy/twitpic-json
Feel free to log issues, fork it and make it better.
In addition to GitHub lovelyness, this is my first Google App Engine project written in Python (which I've not written before).
It wasn't too painful, though I definitely thought Python was more OO that my experience (though it's likely I screwed up!).
I'd like to move Twivatar across to App Engine at some point to reduce the load on my database, and I needed an excuse to play with Python, so this was an attempt to scratch an itch.