<?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: Monetizing Twitter</title>
	<atom:link href="http://www.blogschmog.net/2008/07/10/monetizing-twitter/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.blogschmog.net/2008/07/10/monetizing-twitter/</link>
	<description>We live as if the world were as it should be, to show it what it can be.</description>
	<lastBuildDate>Tue, 26 Jul 2011 13:57:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: 10 ways that Twitter could make money quickly &#171; Innovation 2.0 and&#8230;</title>
		<link>http://www.blogschmog.net/2008/07/10/monetizing-twitter/comment-page-1/#comment-33707</link>
		<dc:creator>10 ways that Twitter could make money quickly &#171; Innovation 2.0 and&#8230;</dc:creator>
		<pubDate>Tue, 15 Jul 2008 05:36:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogschmog.net/?p=1789#comment-33707</guid>
		<description>[...] of all earnings based on profits, there would be some immediate revenue. Another suggestion is to charge for API requests with request-rate [...]</description>
		<content:encoded><![CDATA[<p>[...] of all earnings based on profits, there would be some immediate revenue. Another suggestion is to charge for API requests with request-rate [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 10 ways that Twitter could make money quickly &#124; The Industry Standard</title>
		<link>http://www.blogschmog.net/2008/07/10/monetizing-twitter/comment-page-1/#comment-33704</link>
		<dc:creator>10 ways that Twitter could make money quickly &#124; The Industry Standard</dc:creator>
		<pubDate>Tue, 15 Jul 2008 00:41:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogschmog.net/?p=1789#comment-33704</guid>
		<description>&lt;!--%kramer-ref-pre%--&gt;[...] of all earnings based on profits, there would be some immediate revenue. Another suggestion is to charge for API requests with request-rate [...]&lt;!--%kramer-ref-post%--&gt;</description>
		<content:encoded><![CDATA[<p><a href="http://dev.wp-plugins.org/wiki/Kramer"><img src="http://www.blogschmog.net/wp-content/plugins/kramer.php?kramer=gif-icon" class="technorati-balloon" alt="Kramer auto Pingback" style="border:0;" /></a>[...] of all earnings based on profits, there would be some immediate revenue. Another suggestion is to charge for API requests with request-rate [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Makice</title>
		<link>http://www.blogschmog.net/2008/07/10/monetizing-twitter/comment-page-1/#comment-33687</link>
		<dc:creator>Kevin Makice</dc:creator>
		<pubDate>Fri, 11 Jul 2008 16:18:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogschmog.net/?p=1789#comment-33687</guid>
		<description>I think that&#039;s an excellent observation. Sort of what Tivo can do through their DVR service, only with a broader scope of domains. The service can then remain free for use and development as Twitter becomes a research center.

The big question, though, is whether they are tracking other bits of information not in the API. Obviously (pun), they can query in more efficient and broader ways than a third-party developer working through the API. But I look at something like Twitscope as a sign of the future. Lots of useful real-time information available there.</description>
		<content:encoded><![CDATA[<p>I think that&#8217;s an excellent observation. Sort of what Tivo can do through their DVR service, only with a broader scope of domains. The service can then remain free for use and development as Twitter becomes a research center.</p>
<p>The big question, though, is whether they are tracking other bits of information not in the API. Obviously (pun), they can query in more efficient and broader ways than a third-party developer working through the API. But I look at something like Twitscope as a sign of the future. Lots of useful real-time information available there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Drew</title>
		<link>http://www.blogschmog.net/2008/07/10/monetizing-twitter/comment-page-1/#comment-33684</link>
		<dc:creator>Drew</dc:creator>
		<pubDate>Thu, 10 Jul 2008 20:05:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogschmog.net/?p=1789#comment-33684</guid>
		<description>What about data trending? Twitter could effectively act as an instant means for trending. Being able to instantly trend users would be a marketer&#039;s dream.</description>
		<content:encoded><![CDATA[<p>What about data trending? Twitter could effectively act as an instant means for trending. Being able to instantly trend users would be a marketer&#8217;s dream.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

