<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0">
	<channel>
		<title>gdp's Comments</title>
		<language>en-us</language>
		<link>https://www.intensedebate.com/users/875705</link>
		<description>Comments by philbaumann</description>
<item>
<title>http://www.healthcarecommunication.com/ : 5 powerful health care Twitter hashtags to check out | Articles</title>
<link>http://www.healthcarecommunication.com/Main/Articles/6810.aspx#IDComment154162047</link>
<description>There&amp;#039;s also #MDchat, #RNchat and #FamMedChat  They&amp;#039;ve been around for a long time.   In fact #MDchat and #RNchat were the first clinical Twitter chats.  Big ones to miss ;) </description>
<pubDate>Thu, 19 May 2011 23:55:19 +0000</pubDate>
<guid>http://www.healthcarecommunication.com/Main/Articles/6810.aspx#IDComment154162047</guid>
</item><item>
<title>http://willfrancis.com/ : </title>
<link>http://willfrancis.com/post/888522221#IDComment90212926</link>
<description>Tried it myself and my All Friends column is wild (reminds me of Friendfeed&amp;#039;s stream before Facebook purchased it.  But I think we need to distinguish between Real-time and Instant.   In the true sense of the phrase, Real-time media are media that deliver the right information at the right time in the right context. Twitter, Facebook status updates, etc. aren&amp;#039;t true Real-time media. They&amp;#039;re actually Instant media (save for the appearance of the Fail Whale).  On one hand, I think there&amp;#039;s value in Instant streaming - as you described above. But on the other, I think we&amp;#039;ll get a point when we&amp;#039;ll more strongly demand true Real-time software.  When we use clients like Tweetdeck and set up columns, what we&amp;#039;re trying to do is to get closer to Real-time.   So I think Twitter isn&amp;#039;t totally the future yet. But it&amp;#039;s a pretty fun approximation.  @PhilBaumann </description>
<pubDate>Sun, 1 Aug 2010 22:36:17 +0000</pubDate>
<guid>http://willfrancis.com/post/888522221#IDComment90212926</guid>
</item>	</channel>
</rss>