I just hope that flickr will adapt the API-policy as outlined by stewart butterfields (read http://www.flickr.com/groups/central/discuss/72157594165399644/#comment72157594167782546)…. i.e. giving anyone, even a direct competitor like zooomer (@kris tate: sorry, but that’s exactly what you are, imho), access to the API who is itself willing to give flickr access to its users data.

Just to clarify, we’ve never had any sort of “special treatment” from the Flickr guys. We just went like anyone else to their API page, applied for a key, and wrote our integration around it. I’ve written about it before but it’s worth mentioning again: I (and all of us at Tabblo) are really impressed with how open Flickr has been with respect to allowing its users to bring over their content to Tabblo.

I have a ton of respect for the Flickr folks when it comes to openness. In fact, as we try to evolve our own API, I often hear myself in meetings making comparisons to the Flickr one and asking: how can we make it more like Flickr’s.

http://digg.com/technology/Why_is_Flickr_Afraid_of_Zooomr_

Thanks,

-Kristopher

thx for your explanation, I wasn’t aware that the tabblo<>flickr-integration is based on an API which is blocked for zooomer (or other, more direct competitors) – which, of course, is a shame.

Trust me in that we would have Flickr integration if it were up to me. Tabblo is using Flickr’s API to download photos from Flickr, which is something that companies have to apply for.

While it seems that Tabblo isn’t ‘direct competitor’ enough to deem a API block, Zooomr is, and as such Flickr has refused to give us access to their API.

What this means though, on a broader scale, is that if you use services such as Flickr, you’re up to their discretion on if they want to move your already uploaded photos to other sites you would like to use — including tags.

Don’t let sites like Flickr lock you in.

Kristopher Tate
cto & founder — bluebridge tech / zooomr