<?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:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Other Ways to Participate in #lrnchat</title>
	<atom:link href="http://www.aaronsilvers.com/2010/02/other-ways-to-participate-in-lrnchat/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.aaronsilvers.com/2010/02/other-ways-to-participate-in-lrnchat/</link>
	<description>Learning Nerd. Husband. Dad. Rocker. Cobbler. Coder. Strategist. Visionary. Hugger. Dude.</description>
	<lastBuildDate>Sun, 06 Jun 2010 02:25:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Aaron</title>
		<link>http://www.aaronsilvers.com/2010/02/other-ways-to-participate-in-lrnchat/comment-page-1/#comment-1897</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Thu, 11 Feb 2010 16:18:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.aaronsilvers.com/?p=1456#comment-1897</guid>
		<description>I really like Wave for this kind of activity - co-authoring but I don&#039;t see a lot of people building their comfort with Wave.  That&#039;s kind of how Paul and I got into that conversation -- talking about structure in Google Wave.

Buzz is interesting in some ways for this kind of activity, but I&#039;m afraid it starts to get unmanageable when you have so many comments responding at the same time -- the interface becomes a constraint to how much you can follow, where Twitter (more like Tweetdeck or TweetChat) accomodates that rapidfire activity well.

Still... Marcia turned me onto what #journchat does for a summary.  Someone acts as moderator, favorite-ing what they feel are the big points that emerge and then they simply cull those favorites in an organized way, based on the structure of the chat.  That ultimately might be the easiest and straight-forward way of doing it.

Doesn&#039;t make it the best way -- doesn&#039;t mean you can&#039;t have a community that&#039;s interested in pouring through the tweets to derive the juice from the fruit, either.</description>
		<content:encoded><![CDATA[<p>I really like Wave for this kind of activity &#8211; co-authoring but I don&#8217;t see a lot of people building their comfort with Wave.  That&#8217;s kind of how Paul and I got into that conversation &#8212; talking about structure in Google Wave.</p>
<p>Buzz is interesting in some ways for this kind of activity, but I&#8217;m afraid it starts to get unmanageable when you have so many comments responding at the same time &#8212; the interface becomes a constraint to how much you can follow, where Twitter (more like Tweetdeck or TweetChat) accomodates that rapidfire activity well.</p>
<p>Still&#8230; Marcia turned me onto what #journchat does for a summary.  Someone acts as moderator, favorite-ing what they feel are the big points that emerge and then they simply cull those favorites in an organized way, based on the structure of the chat.  That ultimately might be the easiest and straight-forward way of doing it.</p>
<p>Doesn&#8217;t make it the best way &#8212; doesn&#8217;t mean you can&#8217;t have a community that&#8217;s interested in pouring through the tweets to derive the juice from the fruit, either.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Dusablon</title>
		<link>http://www.aaronsilvers.com/2010/02/other-ways-to-participate-in-lrnchat/comment-page-1/#comment-1895</link>
		<dc:creator>Brian Dusablon</dc:creator>
		<pubDate>Thu, 11 Feb 2010 15:59:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.aaronsilvers.com/?p=1456#comment-1895</guid>
		<description>Buzz + Twitter + Wave...could be interesting.</description>
		<content:encoded><![CDATA[<p>Buzz + Twitter + Wave&#8230;could be interesting.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
