IFTTT and RSS: enclosure anyone?

Plumbing from one website to a platform is not always so easy as it seems.

I’m using IFTTT, from time to time, because it’s the plumbing on the web that we liked about Yahoo Pipes and ol’plain RSS back in the days when the raging discussions were all about RSS or Atom, and also was it better to stick with RSS 1.0 or jump the bandwagom and do a crazy stunt like choosing RSS 2.0, remember?


With IFTTT, it’s reasonably easy to push information from one platform to another. For example, I can let my Twitter friends know I’ve published a new article on my website, I can store in diigo a link to a URL I liked in my offline reader, and so on.

The other day, I decided that I wanted to use Flickr again, because I miss the social quality when I publish pictures here. But I wanted to keep the control I have over the stuff I publish. In other words: publish here and push to the world automatically. And guess what, many people have already thought about that. There’s a grassroot movement called POSSE (for “Publish (on your) Own Site, Syndicate Elsewhere”) that proposes just that: put up methods so that your content is not published in the silos but published on your own site and then replicated into the silos.

So, I decided to push the RSS for my photos to Flickr.

IFTTT says no problem, and even provides an “automagic” element called {{EntryImageUrl}}. Yes but no, it failed to find the perfectly valid enclosure in my RSS feed: “Action skipped: No valid image URL provided.”

So far, I’m stranded, and have found nothing in the interwebs, and IFTTT did not respond to my tweet (I don’t blame them, I must not be the sole person calling for help).

Any ideas, people?


Who are you?
Your post

To create paragraphs, simply leave blank lines. All outgoing links will feature an attribute rel="nofollow". Please do not spam.