<?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: MicrostockRF Part 2: Getty&#8217;s Thinkstock</title>
	<atom:link href="http://gregceoblog.com/microstockrf-part-2-gettys-thinkstock/feed" rel="self" type="application/rss+xml" />
	<link>http://gregceoblog.com/microstockrf-part-2-gettys-thinkstock</link>
	<description>Greg&#039;s blog includes posts about the business of photography, features on new and established photographers, and Greg&#039;s own work.</description>
	<lastBuildDate>Mon, 19 Jul 2010 19:26:05 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Sylvia</title>
		<link>http://gregceoblog.com/microstockrf-part-2-gettys-thinkstock#comment-511</link>
		<dc:creator>Sylvia</dc:creator>
		<pubDate>Wed, 03 Feb 2010 15:40:19 +0000</pubDate>
		<guid isPermaLink="false">http://gregceoblog.com/?p=1027#comment-511</guid>
		<description>I used to work alongside the ADs for TS before the acquisition. There seemed to be such a conflict between making the TS RF images stand out as &quot;different&quot; than microstock while at the same time making them generic enough to compete with MS. It was such a strange balancing act that obviously did not succeed. Sad.</description>
		<content:encoded><![CDATA[<p>I used to work alongside the ADs for TS before the acquisition. There seemed to be such a conflict between making the TS RF images stand out as &#8220;different&#8221; than microstock while at the same time making them generic enough to compete with MS. It was such a strange balancing act that obviously did not succeed. Sad.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->