<?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: eMetrics Twitter Backchannel Analysis</title>
	<atom:link href="http://blog.instantcognition.com/twitter/2008/05/10/emetrics-twitter-backchannel-analysis/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.instantcognition.com/twitter/2008/05/10/emetrics-twitter-backchannel-analysis/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=emetrics-twitter-backchannel-analysis</link>
	<description>a discussion of visual report design &#038; web analytics</description>
	<lastBuildDate>Sat, 04 Jun 2011 07:27:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: cidade (cidade.usp.br)</title>
		<link>http://blog.instantcognition.com/twitter/2008/05/10/emetrics-twitter-backchannel-analysis/comment-page-1/#comment-23960</link>
		<dc:creator>cidade (cidade.usp.br)</dc:creator>
		<pubDate>Fri, 28 Nov 2008 11:23:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.instantcognition.com/?p=239#comment-23960</guid>
		<description>[delicious] [from fjcapeletto] eMetrics Twitter Backchannel Analysis &quot; Instant Cognition http://tinyurl.com/5f4fbm</description>
		<content:encoded><![CDATA[<p>[delicious] [from fjcapeletto] eMetrics Twitter Backchannel Analysis &#8221; Instant Cognition <a href="http://tinyurl.com/5f4fbm" rel="nofollow">http://tinyurl.com/5f4fbm</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fjcapeletto (Fernando J Capeletto)</title>
		<link>http://blog.instantcognition.com/twitter/2008/05/10/emetrics-twitter-backchannel-analysis/comment-page-1/#comment-23961</link>
		<dc:creator>fjcapeletto (Fernando J Capeletto)</dc:creator>
		<pubDate>Fri, 28 Nov 2008 11:23:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.instantcognition.com/?p=239#comment-23961</guid>
		<description>[delicious] eMetrics Twitter Backchannel Analysis » Instant Cognition http://tinyurl.com/5f4fbm</description>
		<content:encoded><![CDATA[<p>[delicious] eMetrics Twitter Backchannel Analysis » Instant Cognition <a href="http://tinyurl.com/5f4fbm" rel="nofollow">http://tinyurl.com/5f4fbm</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Powerful feedback loops, and why should you care &#171;</title>
		<link>http://blog.instantcognition.com/twitter/2008/05/10/emetrics-twitter-backchannel-analysis/comment-page-1/#comment-23828</link>
		<dc:creator>Powerful feedback loops, and why should you care &#171;</dc:creator>
		<pubDate>Mon, 17 Nov 2008 15:01:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.instantcognition.com/?p=239#comment-23828</guid>
		<description>[...] back-channel is always at work. In grade school it was a piece of paper that was surreptitiously circulated [...]</description>
		<content:encoded><![CDATA[<p>[...] back-channel is always at work. In grade school it was a piece of paper that was surreptitiously circulated [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ignore feedback loops at your own peril &#187; Hoipolloi Report</title>
		<link>http://blog.instantcognition.com/twitter/2008/05/10/emetrics-twitter-backchannel-analysis/comment-page-1/#comment-23827</link>
		<dc:creator>Ignore feedback loops at your own peril &#187; Hoipolloi Report</dc:creator>
		<pubDate>Mon, 17 Nov 2008 10:08:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.instantcognition.com/?p=239#comment-23827</guid>
		<description>[...] back-channel is always at work. In grade school it was a piece of paper that was surreptitiously circulated [...]</description>
		<content:encoded><![CDATA[<p>[...] back-channel is always at work. In grade school it was a piece of paper that was surreptitiously circulated [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clint</title>
		<link>http://blog.instantcognition.com/twitter/2008/05/10/emetrics-twitter-backchannel-analysis/comment-page-1/#comment-21364</link>
		<dc:creator>Clint</dc:creator>
		<pubDate>Fri, 23 May 2008 23:16:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.instantcognition.com/?p=239#comment-21364</guid>
		<description>To my visitor from Hawaii who has looked at this post 15 times since I posted it:

If there&#039;s something I can help you with please leave a comment, email me (civy &quot;at&quot; instantcognition.com) or send me a message on twitter (&lt;a href=&quot;http://twitter.com/omomyid&quot; rel=&quot;nofollow&quot;&gt;@omomyid&lt;/a&gt;). 
&lt;b&gt;I&#039;m happy to help -- if I can.&lt;/b&gt;</description>
		<content:encoded><![CDATA[<p>To my visitor from Hawaii who has looked at this post 15 times since I posted it:</p>
<p>If there&#8217;s something I can help you with please leave a comment, email me (civy &#8220;at&#8221; instantcognition.com) or send me a message on twitter (<a href="http://twitter.com/omomyid" rel="nofollow">@omomyid</a>).<br />
<b>I&#8217;m happy to help &#8212; if I can.</b></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clint</title>
		<link>http://blog.instantcognition.com/twitter/2008/05/10/emetrics-twitter-backchannel-analysis/comment-page-1/#comment-21148</link>
		<dc:creator>Clint</dc:creator>
		<pubDate>Tue, 13 May 2008 17:13:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.instantcognition.com/?p=239#comment-21148</guid>
		<description>@June Dershewitz: Rock on! I&#039;ll beat the horse again - @jimsterne needs to provide better connectivity in the conference rooms.

It&#039;ll be nice to let someone who is actually there the whole time host.

Here&#039;s a tip, if you plan to do analysis, use Excel to grab the RSS on a daily basis. I missed a lot of opportunities because I didn&#039;t. Most importantly, time of day analysis and qualitative assessment. If I had been dumping the feed into excel on a daily basis I could have easily analyzed the content of the tweets - oh well!

I think the XChange format doesn&#039;t really support this kind of communication, but what do you think?</description>
		<content:encoded><![CDATA[<p>@June Dershewitz: Rock on! I&#8217;ll beat the horse again &#8211; @jimsterne needs to provide better connectivity in the conference rooms.</p>
<p>It&#8217;ll be nice to let someone who is actually there the whole time host.</p>
<p>Here&#8217;s a tip, if you plan to do analysis, use Excel to grab the RSS on a daily basis. I missed a lot of opportunities because I didn&#8217;t. Most importantly, time of day analysis and qualitative assessment. If I had been dumping the feed into excel on a daily basis I could have easily analyzed the content of the tweets &#8211; oh well!</p>
<p>I think the XChange format doesn&#8217;t really support this kind of communication, but what do you think?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: June Dershewitz</title>
		<link>http://blog.instantcognition.com/twitter/2008/05/10/emetrics-twitter-backchannel-analysis/comment-page-1/#comment-21147</link>
		<dc:creator>June Dershewitz</dc:creator>
		<pubDate>Tue, 13 May 2008 16:54:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.instantcognition.com/?p=239#comment-21147</guid>
		<description>Bob brings up a good point - our ability to contribute was limited by the crappy network/cell reception at the hotel.  This probably explains the &quot;I&#039;m at the lobby bar&quot; reports - our phones actually worked there.

Anyhow, this was a fun experiment and I look forward to doing it again, hopefully with more of our web analytics comrades.  I volunteer to host the backchannel at eMetrics DC this fall.

June &quot;#2 Twit&quot; Dershewitz</description>
		<content:encoded><![CDATA[<p>Bob brings up a good point &#8211; our ability to contribute was limited by the crappy network/cell reception at the hotel.  This probably explains the &#8220;I&#8217;m at the lobby bar&#8221; reports &#8211; our phones actually worked there.</p>
<p>Anyhow, this was a fun experiment and I look forward to doing it again, hopefully with more of our web analytics comrades.  I volunteer to host the backchannel at eMetrics DC this fall.</p>
<p>June &#8220;#2 Twit&#8221; Dershewitz</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clint</title>
		<link>http://blog.instantcognition.com/twitter/2008/05/10/emetrics-twitter-backchannel-analysis/comment-page-1/#comment-21140</link>
		<dc:creator>Clint</dc:creator>
		<pubDate>Tue, 13 May 2008 06:36:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.instantcognition.com/?p=239#comment-21140</guid>
		<description>@bobpage: Bob, while your twittering definitely spiked on a couple of days, it was more distributed than you think. Because I wasn&#039;t capturing the RSS in realtime it&#039;s difficult to do the daypart analysis now.

One of my top recommendations to @jimsterne is better connectivity in the rooms.

As far as &#039;idea space&#039; goes, check out &lt;a href=&quot;http://tweetscan.com/index.php?s=mrforum&amp;u=&amp;p=0&amp;d=&quot; rel=&quot;nofollow&quot;&gt;Media Republic Tweetscan&lt;/a&gt; Basically, this idea space was lots of people tweeting what they heard during presos that they found interesting - e.g. note taking. It was a great way to see audience response to the sessions. I could have wished for more discussion (as was reportedly the case at SXSW) but still the many perspectives shared in Twitter were pretty darn cool.
I&#039;ve never seen a more plugged in crowd which was pretty interesting since they were all journalists.

What&#039;s interesting is if you go ahead and assume that Twitter is currently for early adopters and &#039;influentials&#039; then the web analytics crowd must appear to be a very normal distribution of demographics. We had 26 (including me) contribute to the backchannel and even if there were double that actually tweeting about #emetrics that&#039;s still somewhere south of the total population at #emetrics.

Just riffin&#039; here.</description>
		<content:encoded><![CDATA[<p>@bobpage: Bob, while your twittering definitely spiked on a couple of days, it was more distributed than you think. Because I wasn&#8217;t capturing the RSS in realtime it&#8217;s difficult to do the daypart analysis now.</p>
<p>One of my top recommendations to @jimsterne is better connectivity in the rooms.</p>
<p>As far as &#8216;idea space&#8217; goes, check out <a href="http://tweetscan.com/index.php?s=mrforum&#038;u=&#038;p=0&#038;d=" rel="nofollow">Media Republic Tweetscan</a> Basically, this idea space was lots of people tweeting what they heard during presos that they found interesting &#8211; e.g. note taking. It was a great way to see audience response to the sessions. I could have wished for more discussion (as was reportedly the case at SXSW) but still the many perspectives shared in Twitter were pretty darn cool.<br />
I&#8217;ve never seen a more plugged in crowd which was pretty interesting since they were all journalists.</p>
<p>What&#8217;s interesting is if you go ahead and assume that Twitter is currently for early adopters and &#8216;influentials&#8217; then the web analytics crowd must appear to be a very normal distribution of demographics. We had 26 (including me) contribute to the backchannel and even if there were double that actually tweeting about #emetrics that&#8217;s still somewhere south of the total population at #emetrics.</p>
<p>Just riffin&#8217; here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Page</title>
		<link>http://blog.instantcognition.com/twitter/2008/05/10/emetrics-twitter-backchannel-analysis/comment-page-1/#comment-21139</link>
		<dc:creator>Bob Page</dc:creator>
		<pubDate>Tue, 13 May 2008 06:18:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.instantcognition.com/?p=239#comment-21139</guid>
		<description>Wow, analysis of anything!  Seriously, thanks for setting up the backchannel.  I noticed a lot of folks forgot (or chose not to) use it, especially when replying to tweets.  But it was useful for me to get a sense of what was going on outside the realm of my own experience.

I had the advantage of spending Sunday attending the Industry Insights Day - where my cell phone had a reasonable network connection, and there was beaucoup twitter-worthiness.  Most of my fellow Twitterers were only on duty Monday through Wednesday, many without a decent network/cell connection... a daypart analysis may bear out that hypothesis...

Can you talk more about the &quot;idea space&quot; you saw at Media Re:Public?</description>
		<content:encoded><![CDATA[<p>Wow, analysis of anything!  Seriously, thanks for setting up the backchannel.  I noticed a lot of folks forgot (or chose not to) use it, especially when replying to tweets.  But it was useful for me to get a sense of what was going on outside the realm of my own experience.</p>
<p>I had the advantage of spending Sunday attending the Industry Insights Day &#8211; where my cell phone had a reasonable network connection, and there was beaucoup twitter-worthiness.  Most of my fellow Twitterers were only on duty Monday through Wednesday, many without a decent network/cell connection&#8230; a daypart analysis may bear out that hypothesis&#8230;</p>
<p>Can you talk more about the &#8220;idea space&#8221; you saw at Media Re:Public?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clint</title>
		<link>http://blog.instantcognition.com/twitter/2008/05/10/emetrics-twitter-backchannel-analysis/comment-page-1/#comment-21109</link>
		<dc:creator>Clint</dc:creator>
		<pubDate>Sun, 11 May 2008 18:16:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.instantcognition.com/?p=239#comment-21109</guid>
		<description>@Jon Peltier: Thanks John! I&#039;ve added your chart to the body of the post.</description>
		<content:encoded><![CDATA[<p>@Jon Peltier: Thanks John! I&#8217;ve added your chart to the body of the post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Peltier</title>
		<link>http://blog.instantcognition.com/twitter/2008/05/10/emetrics-twitter-backchannel-analysis/comment-page-1/#comment-21108</link>
		<dc:creator>Jon Peltier</dc:creator>
		<pubDate>Sun, 11 May 2008 18:03:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.instantcognition.com/?p=239#comment-21108</guid>
		<description>Hmmm, no image tags accepted in comments. The chart is at http://peltiertech.com/Sample/zipf_instantcognition.png</description>
		<content:encoded><![CDATA[<p>Hmmm, no image tags accepted in comments. The chart is at <a href="http://peltiertech.com/Sample/zipf_instantcognition.png" rel="nofollow">http://peltiertech.com/Sample/zipf_instantcognition.png</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Peltier</title>
		<link>http://blog.instantcognition.com/twitter/2008/05/10/emetrics-twitter-backchannel-analysis/comment-page-1/#comment-21103</link>
		<dc:creator>Jon Peltier</dc:creator>
		<pubDate>Sun, 11 May 2008 14:50:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.instantcognition.com/?p=239#comment-21103</guid>
		<description>&quot;So what’s all this telling us?&quot;

Your distribution of contributions vs. rank is described by Zipf&#039;s Law (&lt;a href=&quot;http://www.nslij-genetics.org/wli/zipf/index.html&quot; rel=&quot;nofollow&quot;&gt;http://www.nslij-genetics.org/wli/zipf/index.html&lt;/a&gt;), which has been applied to web site traffic by Jakob Nielsen in &lt;a href=&quot;http://www.useit.com/alertbox/zipf.html&quot; rel=&quot;nofollow&quot;&gt;Zipf Curves and Website Popularity&lt;/a&gt;. I&#039;ve made a simple plot of this for you:
</description>
		<content:encoded><![CDATA[<p>&#8220;So what’s all this telling us?&#8221;</p>
<p>Your distribution of contributions vs. rank is described by Zipf&#8217;s Law (<a href="http://www.nslij-genetics.org/wli/zipf/index.html" rel="nofollow">http://www.nslij-genetics.org/wli/zipf/index.html</a>), which has been applied to web site traffic by Jakob Nielsen in <a href="http://www.useit.com/alertbox/zipf.html" rel="nofollow">Zipf Curves and Website Popularity</a>. I&#8217;ve made a simple plot of this for you:</p>
]]></content:encoded>
	</item>
</channel>
</rss>

