<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: A Twitter Experiment</title>
	<atom:link href="http://scholarlykitchen.sspnet.org/2008/05/10/a-twitter-experiment/feed/" rel="self" type="application/rss+xml" />
	<link>http://scholarlykitchen.sspnet.org/2008/05/10/a-twitter-experiment/</link>
	<description>What&#039;s Hot &#38; What&#039;s Cooking in Scholarly Publishing - from the Society for Scholarly Publishing</description>
	<lastBuildDate>Thu, 16 Feb 2012 03:31:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Twitter &#8212; One Month Later &#171; The Scholarly Kitchen</title>
		<link>http://scholarlykitchen.sspnet.org/2008/05/10/a-twitter-experiment/#comment-425</link>
		<dc:creator><![CDATA[Twitter &#8212; One Month Later &#171; The Scholarly Kitchen]]></dc:creator>
		<pubDate>Tue, 10 Jun 2008 11:01:44 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.wordpress.com/?p=87#comment-425</guid>
		<description><![CDATA[[...] Housekeeping, Research, Social Media, Technology, World of Tomorrow &#160;  One month ago, I wrote on this blog that I would begin using Twitter for a month, and see how it worked, both technically and practically. Now, one month later, here are some [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Housekeeping, Research, Social Media, Technology, World of Tomorrow &nbsp;  One month ago, I wrote on this blog that I would begin using Twitter for a month, and see how it worked, both technically and practically. Now, one month later, here are some [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

