on reclaiming my instagrams

I’ve loved Instagram since it was first released. Maybe that makes me a faux-retro-hipster. Whatever. It’s a fun app, and I like the aesthetic (how pretentious can this guy get? really?). Annyway… The one thing I didn’t like about Instagram is that it sucks my photos into its vortex of strangely-social-yet-antisocial-and-corporately-managed media hosting. I still posted a few, but kept the versions to also post here. But that’s a pain.

Then, I was reminded about the fantastic intarweb automation tool, ifttt (if this, then that). Like Yahoo! Pipes, with a simpler trigger-and-actions workflow. I used a recipe1 that creates blog posts here on my site every time I post something to Instagram. That’s simple enough, but the media is still stuck in Instagramland.

The other side of the equation is the really cool Add Linked Images to Gallery WordPress plugin. It sniffs around in the HTML of new posts and detects any images that are hosted elsewhere. It then copies the image onto my server, and transmorgrifies the post’s HTML to point to my copy of the image. For bonus marks, it adds an “instagram” tag to the posts, so it’s easy to see all of the photos that get automagically imported.

So, every time I take a photo with Instagram, it gets posted here on my blog, the media gets copied here for non-sharecropped-hosting, and the photos get merged into my ongoing ephemeral media stream. Easy peasy.

I don’t care that copies of the photos are left in Instagram’s quirky little silo. They’re there for anyone who is using it, but also here for my archive. Best of both worlds.

  1. the Instagram-to-WordPress Photo Post worked, but hardcodes an image width of 600px, which is strange. The Instagram-to-WordPress-Post recipe works just fine, though… []

5 thoughts on “on reclaiming my instagrams”

    1. bingo. then my stuff is just in another silo. I want to host it (or at least copies of it) here… I haven’t posted to Flickr in months, and don’t intend to renew my Pro account when it expires.

  1. Great use of ifttt. When Delicious was getting a bit iffy I set up a recipe to create a blog post from my bookmarks (just in case). I’ve left it churning away in the background ever since.

    1. yeah, it’s a pretty handy service, and more usable than Yahoo! Pipes. But, I have to wonder how they pay their bills. All of those scheduled jobs running in the background must eat up a LOT of CPU/bandwidth/etc… How do they pay for it? How will they pay for it? Or will the service either disappear or become absorbed into something else? I wonder if there’s a self-hosted analog to ifttt…

      1. Self-hosted or self-managed in a C-panel installation would be nice. I do worry about the service going under without notice (or without emailing me) but I think I’d hear fairly quickly through the eduInterPipes. I also worry about the password info I’ve had to entrust to ifttt.

        I tried out Yahoo Pipes for the first time a couple of weeks ago and so far my simple needs (aggregate feeds, create widget) have been accomplished in without undue stress.

Comments are closed.