<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Flickr, Zooomr and API Parity</title>
	<atom:link href="http://www.sitepoint.com/blogs/2006/06/21/flickr-zooomr-and-api-parity/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sitepoint.com/blogs/2006/06/21/flickr-zooomr-and-api-parity/</link>
	<description>News, opinion, and fresh thinking for web developers and designers. The official podcast of sitepoint.com.</description>
	<pubDate>Thu, 04 Dec 2008 01:09:23 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Nate Kirby</title>
		<link>http://www.sitepoint.com/blogs/2006/06/21/flickr-zooomr-and-api-parity/#comment-51989</link>
		<dc:creator>Nate Kirby</dc:creator>
		<pubDate>Tue, 05 Sep 2006 20:09:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2006/06/21/flickr-zooomr-and-api-parity/#comment-51989</guid>
		<description>I think the point about "burning CPU cycles" is misunderstood.  It takes time for engineers to build thsi import/export facility. Those engineers could be adding user requested features instead of building the import export.</description>
		<content:encoded><![CDATA[<p>I think the point about &#8220;burning CPU cycles&#8221; is misunderstood.  It takes time for engineers to build thsi import/export facility. Those engineers could be adding user requested features instead of building the import export.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: chrisb</title>
		<link>http://www.sitepoint.com/blogs/2006/06/21/flickr-zooomr-and-api-parity/#comment-31940</link>
		<dc:creator>chrisb</dc:creator>
		<pubDate>Thu, 22 Jun 2006 09:19:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2006/06/21/flickr-zooomr-and-api-parity/#comment-31940</guid>
		<description>Agreed.. if you start insisting all sites must share data with competitors will just end up with patent issues rising up again - if they can't stiffle competition by making it a little bit more difficult to move, they'll just find ways to stop the competition getting off the ground in the first place and suddenly we're back where we started and the user is worse off!</description>
		<content:encoded><![CDATA[<p>Agreed.. if you start insisting all sites must share data with competitors will just end up with patent issues rising up again - if they can&#8217;t stiffle competition by making it a little bit more difficult to move, they&#8217;ll just find ways to stop the competition getting off the ground in the first place and suddenly we&#8217;re back where we started and the user is worse off!</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Stewart Butterfield</title>
		<link>http://www.sitepoint.com/blogs/2006/06/21/flickr-zooomr-and-api-parity/#comment-31749</link>
		<dc:creator>Stewart Butterfield</dc:creator>
		<pubDate>Wed, 21 Jun 2006 17:17:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2006/06/21/flickr-zooomr-and-api-parity/#comment-31749</guid>
		<description>You're missing the point. The path to true data portability does not start with the implementation of vendor-specific APIs.

That may introduce a small amount of openness into the market, depending how many services implement each other's APIs, but the only way to ensure broad interoperability is have an open *standard* (as opposed to API) for import/export. 

Most users organize their photos on their local computer and neither Microsfot nor Apple is ever going to implement the Flickr APIs so the metadata makes it back to the file system. Neither are the dozens of desktop photo management applications going start coming bundled with web servers to online services can hook up to them. It's just not a realistic approach.

On the other hand, ITPC is doing fairly well, and with some extensions to match the functionality of modern online services, it could be just the ticket. 

Finally, there are all kinds of reasons *not* to use the API for this: it opens the provider of the API to all kinds of risks and requires more monitoring, oversight and protection of users' data and privacy. A malicious third party can't do any damage when importing exported data, but they can through the API.</description>
		<content:encoded><![CDATA[<p>You&#8217;re missing the point. The path to true data portability does not start with the implementation of vendor-specific APIs.</p>
<p>That may introduce a small amount of openness into the market, depending how many services implement each other&#8217;s APIs, but the only way to ensure broad interoperability is have an open *standard* (as opposed to API) for import/export. </p>
<p>Most users organize their photos on their local computer and neither Microsfot nor Apple is ever going to implement the Flickr APIs so the metadata makes it back to the file system. Neither are the dozens of desktop photo management applications going start coming bundled with web servers to online services can hook up to them. It&#8217;s just not a realistic approach.</p>
<p>On the other hand, ITPC is doing fairly well, and with some extensions to match the functionality of modern online services, it could be just the ticket. </p>
<p>Finally, there are all kinds of reasons *not* to use the API for this: it opens the provider of the API to all kinds of risks and requires more monitoring, oversight and protection of users&#8217; data and privacy. A malicious third party can&#8217;t do any damage when importing exported data, but they can through the API.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Madmac</title>
		<link>http://www.sitepoint.com/blogs/2006/06/21/flickr-zooomr-and-api-parity/#comment-31734</link>
		<dc:creator>Madmac</dc:creator>
		<pubDate>Wed, 21 Jun 2006 16:23:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2006/06/21/flickr-zooomr-and-api-parity/#comment-31734</guid>
		<description>Web 2.0 is driven by generosity. Video and photo hosting services are all suddenly free-of-charge. Digg just sends people *away* as quickly as possible. Etc, etc.

However, this generosity is rightly directed at the end user. 

I've read much about this Flickr / Zooomr debacle and have concluded that, in my humble opinion, it's nothing but exploitation of this wave of generosity. 

Giving away everything an end user could possibly desire in exchange for market penetration is one thing. Assisting rip-off ideas (come on, stop ignoring the fact that we can all see Zooomr is just that, even in name) is another bag of chips entirely.</description>
		<content:encoded><![CDATA[<p>Web 2.0 is driven by generosity. Video and photo hosting services are all suddenly free-of-charge. Digg just sends people *away* as quickly as possible. Etc, etc.</p>
<p>However, this generosity is rightly directed at the end user. </p>
<p>I&#8217;ve read much about this Flickr / Zooomr debacle and have concluded that, in my humble opinion, it&#8217;s nothing but exploitation of this wave of generosity. </p>
<p>Giving away everything an end user could possibly desire in exchange for market penetration is one thing. Assisting rip-off ideas (come on, stop ignoring the fact that we can all see Zooomr is just that, even in name) is another bag of chips entirely.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: bigalreturns</title>
		<link>http://www.sitepoint.com/blogs/2006/06/21/flickr-zooomr-and-api-parity/#comment-31710</link>
		<dc:creator>bigalreturns</dc:creator>
		<pubDate>Wed, 21 Jun 2006 14:40:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2006/06/21/flickr-zooomr-and-api-parity/#comment-31710</guid>
		<description>I agree with Dr L here. Flickr are a company, who's objective must only be to be a financial success.  To release an API to a direct rival that allowed them to compete more effectively is business suicide, and I say well done to them for standing up and saying no!
If I came up with a great idea and made a success of it then you can bet that I wouldn't be do anything to make life easier for someone ripping off my idea.</description>
		<content:encoded><![CDATA[<p>I agree with Dr L here. Flickr are a company, who&#8217;s objective must only be to be a financial success.  To release an API to a direct rival that allowed them to compete more effectively is business suicide, and I say well done to them for standing up and saying no!<br />
If I came up with a great idea and made a success of it then you can bet that I wouldn&#8217;t be do anything to make life easier for someone ripping off my idea.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Dr Livingston</title>
		<link>http://www.sitepoint.com/blogs/2006/06/21/flickr-zooomr-and-api-parity/#comment-31707</link>
		<dc:creator>Dr Livingston</dc:creator>
		<pubDate>Wed, 21 Jun 2006 14:28:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2006/06/21/flickr-zooomr-and-api-parity/#comment-31707</guid>
		<description>well i know im proberly going to be shot down but i think flickr are fair enough to stand up and protect not only their own interests but those of their users as well.

so if they want to prevent their competition from access to their software, they have that god damn right just to do so. that is commericialism for you. its nothing personal - its just business :)

and just because there is that prevention in place in no way does that say that there is going to be an impact on the users and how they use the service in relation to other services available either.

if you ask me if flickr actually do give the go ahead for this then this in its self actually restricts and prohibits not only competition but innovation as well.

anyways, my message to flickr is to stand by your convictions and dont give any ground. you are right and just in this case and to give zooomr (crap name btw) access would be selling yourself short...

all that hard work and for what?</description>
		<content:encoded><![CDATA[<p>well i know im proberly going to be shot down but i think flickr are fair enough to stand up and protect not only their own interests but those of their users as well.</p>
<p>so if they want to prevent their competition from access to their software, they have that god damn right just to do so. that is commericialism for you. its nothing personal - its just business :)</p>
<p>and just because there is that prevention in place in no way does that say that there is going to be an impact on the users and how they use the service in relation to other services available either.</p>
<p>if you ask me if flickr actually do give the go ahead for this then this in its self actually restricts and prohibits not only competition but innovation as well.</p>
<p>anyways, my message to flickr is to stand by your convictions and dont give any ground. you are right and just in this case and to give zooomr (crap name btw) access would be selling yourself short&#8230;</p>
<p>all that hard work and for what?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: chris ward</title>
		<link>http://www.sitepoint.com/blogs/2006/06/21/flickr-zooomr-and-api-parity/#comment-31642</link>
		<dc:creator>chris ward</dc:creator>
		<pubDate>Wed, 21 Jun 2006 08:38:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2006/06/21/flickr-zooomr-and-api-parity/#comment-31642</guid>
		<description>This is just crazy, Flickr's nothing special, just an idea that someone reached before anyone else.

But now that people are catching up, they're going to find it difficult to keep innovating to stay ahead, to keep their users... who now have no real reason to stay loyal to the brand as long as they can up-and-leave.

The logic here is all wrong.

Users should have their own APIs, a set of microformats for their data, and then use flickr/zoomr/whatevr to analyse and structure it.

Obviously, this isn't going to happen anytime soon, as nobody can use their desktop as a webserver... but eventually when machines are turned on all the time, and we have massive pipes to push data down, this will become less of an issue.

But still, an interesting topic to follow, thanks for the post!</description>
		<content:encoded><![CDATA[<p>This is just crazy, Flickr&#8217;s nothing special, just an idea that someone reached before anyone else.</p>
<p>But now that people are catching up, they&#8217;re going to find it difficult to keep innovating to stay ahead, to keep their users&#8230; who now have no real reason to stay loyal to the brand as long as they can up-and-leave.</p>
<p>The logic here is all wrong.</p>
<p>Users should have their own APIs, a set of microformats for their data, and then use flickr/zoomr/whatevr to analyse and structure it.</p>
<p>Obviously, this isn&#8217;t going to happen anytime soon, as nobody can use their desktop as a webserver&#8230; but eventually when machines are turned on all the time, and we have massive pipes to push data down, this will become less of an issue.</p>
<p>But still, an interesting topic to follow, thanks for the post!</p>]]></content:encoded>
	</item>
</channel>
</rss>
