<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: CrowdFlower</title>
	<atom:link href="http://blog.crowdflower.com/2009/09/crowdflower/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.crowdflower.com/2009/09/crowdflower/</link>
	<description></description>
	<lastBuildDate>Wed, 07 Dec 2011 22:49:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: David Orban</title>
		<link>http://blog.crowdflower.com/2009/09/crowdflower/#comment-1494</link>
		<dc:creator>David Orban</dc:creator>
		<pubDate>Wed, 16 Sep 2009 08:50:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.doloreslabs.com/2009/09/crowdflower/#comment-1494</guid>
		<description>Congratulations. This is a fantastic move! 

When applications move from a few enterprises using them to a large number of small companies or individuals, they always bloom. Invariably the original uses turn out to be a very small subset of what large numbers of creative, and passionate people come up with. 

I also commend you for the simultaneous launch of the APIs, which make it possible for CrowdFlower to become part of the online apps ecosystem, and not only a streamlined interactive web interface.

It will be important to make sure that the various uses are automatically documented, and made visible through a default setting to share. Just like oDesk generates realtime data of the economy, CrowdFlower users will get great benefit from seeing what is going on, what kind of results are being obtained, and who uses the system in which innovative ways.</description>
		<content:encoded><![CDATA[<p>Congratulations. This is a fantastic move! </p>
<p>When applications move from a few enterprises using them to a large number of small companies or individuals, they always bloom. Invariably the original uses turn out to be a very small subset of what large numbers of creative, and passionate people come up with. </p>
<p>I also commend you for the simultaneous launch of the APIs, which make it possible for CrowdFlower to become part of the online apps ecosystem, and not only a streamlined interactive web interface.</p>
<p>It will be important to make sure that the various uses are automatically documented, and made visible through a default setting to share. Just like oDesk generates realtime data of the economy, CrowdFlower users will get great benefit from seeing what is going on, what kind of results are being obtained, and who uses the system in which innovative ways.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

