<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	
	xmlns:media="http://search.yahoo.com/mrss/"
	>

<channel>
	<title>Bwana.org &#187; quotably</title>
	<atom:link href="http://www.bwana.org/tag/quotably/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bwana.org</link>
	<description>Gaming, Technology, Social Media, and Fun</description>
	<lastBuildDate>Mon, 05 Sep 2011 11:48:38 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<cloud domain='www.bwana.org' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
<link rel="http://api.friendfeed.com/2008/03#sup" xmlns="http://www.w3.org/2005/Atom" type="application/json" href="http://friendfeed.com/api/public-sup.json#3ffaf93dae"/>		<item>
		<title>Quotably Adds User Powered Context</title>
		<link>http://www.bwana.org/2008/03/28/quotably-adds-user-powered-context/</link>
		<comments>http://www.bwana.org/2008/03/28/quotably-adds-user-powered-context/#comments</comments>
		<pubDate>Fri, 28 Mar 2008 20:40:11 +0000</pubDate>
		<dc:creator>Bwana</dc:creator>
				<category><![CDATA[web2.0]]></category>
		<category><![CDATA[quotably]]></category>
		<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://www.bwana.org/2008/03/28/quotably-adds-user-powered-context/</guid>
		<description><![CDATA[A while ago, I blogged about Quotably&#8217;s lack of conversation context. Quotably was designed to solve the problem of sparse Twitter conversations. It did its best to generate a threaded view of the twitter conversation. As I stated before, it failed in many cases and added frustration to a seemingly unfixable problem. Today I found [...]
Related posts:<ul>
<li><a href='http://www.bwana.org/2008/03/24/quotably-needs-conversation-context/' rel='bookmark' title='Quotably Needs Conversation Context'>Quotably Needs Conversation Context</a></li>
<li><a href='http://www.bwana.org/2010/04/14/twitter-user-streams-real-time-is-back/' rel='bookmark' title='Twitter User Streams:  Real-Time Is Back?'>Twitter User Streams:  Real-Time Is Back?</a></li>
<li><a href='http://www.bwana.org/2008/12/28/tweetrees-value-is-embedded-media/' rel='bookmark' title='Tweetree&#8217;s Value Is Embedded Media'>Tweetree&#8217;s Value Is Embedded Media</a></li>
</ul>]]></description>
			<content:encoded><![CDATA[<div align="right" style="float: right; padding: 10px 0px 5px 5px;"><a name="fb_share" type="button_count" share_url="http://www.bwana.org/2008/03/28/quotably-adds-user-powered-context/"></a></div><p>A while ago, I <a href="http://www.bwana.org/2008/03/24/quotably-needs-conversation-context/">blogged</a> about <a href="http://www.quotably.com">Quotably&#8217;s</a> lack of conversation context.  Quotably was designed to solve the problem of sparse Twitter conversations.  It did its best to generate a threaded view of the twitter conversation.  As I stated before, it failed in many cases and added frustration to a seemingly unfixable problem.  Today I found a new feature on Quotably that I want to share:</p>
<div class="thumbnail"><a href="http://skitch.com/bwana/exhf/twitter-quotably.com-new-quotably.com-feature-"><img src="http://img.skitch.com/20080328-ddi9w6k6mpkytesaw52h5mgu1r.preview.jpg" alt="Twitter / Quotably.com: New Quotably.com Feature: ..." /></a></div>
<div class="thumbnail"><a href="http://skitch.com/bwana/ex5i/bwanas-twitter-conversations-quotably.com"><img src="http://img.skitch.com/20080328-8mn8p3415gjeasiss5rm2iu4i5.preview.jpg" alt="Bwana's twitter conversations - Quotably.com" /></a></p>
</div>
<p>Now you are able to (manually) fix threads that Quotably gets wrong.  The context returns!  Even though it&#8217;s a manual process which may not jive for some users, at least you have the option of fixing the conversation.  I like this.  While it&#8217;s not the most elegant solution, it does provide a realistic approach to fixing a design issue with Twitter.  Quotably gets a nod of respect from yours truly for this improvement.  Here&#8217;s a video I made which depicts the process (and also a perfect example of a broken thread):</p>
<p><embed src="http://blip.tv/play/AbCNQwA" type="application/x-shockwave-flash" width="400" height="255" allowscriptaccess="always" allowfullscreen="true"></embed></p>
<p>See room for improvement?  So do I.  The CAPTCHA process needs tweaking.  The system leads you to believe you are inputting a correct CAPTCHA when you are apparently not.  It is kind of frustrating, but workable.  We&#8217;ll see if it gets addressed in a later iteration.</p>
<p>Related posts:<ul>
<li><a href='http://www.bwana.org/2008/03/24/quotably-needs-conversation-context/' rel='bookmark' title='Quotably Needs Conversation Context'>Quotably Needs Conversation Context</a></li>
<li><a href='http://www.bwana.org/2010/04/14/twitter-user-streams-real-time-is-back/' rel='bookmark' title='Twitter User Streams:  Real-Time Is Back?'>Twitter User Streams:  Real-Time Is Back?</a></li>
<li><a href='http://www.bwana.org/2008/12/28/tweetrees-value-is-embedded-media/' rel='bookmark' title='Tweetree&#8217;s Value Is Embedded Media'>Tweetree&#8217;s Value Is Embedded Media</a></li>
</ul></p>]]></content:encoded>
			<wfw:commentRss>http://www.bwana.org/2008/03/28/quotably-adds-user-powered-context/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:thumbnail url="http://img.skitch.com/20080328-ddi9w6k6mpkytesaw52h5mgu1r.preview.jpg" />
		<media:content url="http://img.skitch.com/20080328-ddi9w6k6mpkytesaw52h5mgu1r.preview.jpg" medium="image">
			<media:title type="html">Twitter / Quotably.com: New Quotably.com Feature: ...</media:title>
		</media:content>
		<media:content url="http://img.skitch.com/20080328-8mn8p3415gjeasiss5rm2iu4i5.preview.jpg" medium="image">
			<media:title type="html">Bwana's twitter conversations - Quotably.com</media:title>
		</media:content>
	</item>
		<item>
		<title>Quotably Needs Conversation Context</title>
		<link>http://www.bwana.org/2008/03/24/quotably-needs-conversation-context/</link>
		<comments>http://www.bwana.org/2008/03/24/quotably-needs-conversation-context/#comments</comments>
		<pubDate>Mon, 24 Mar 2008 18:58:09 +0000</pubDate>
		<dc:creator>Bwana</dc:creator>
				<category><![CDATA[geek]]></category>
		<category><![CDATA[conversation]]></category>
		<category><![CDATA[friendfeed]]></category>
		<category><![CDATA[quotably]]></category>
		<category><![CDATA[social aggregators]]></category>
		<category><![CDATA[social web]]></category>
		<category><![CDATA[socialthing]]></category>
		<category><![CDATA[twitter]]></category>
		<category><![CDATA[web2.0]]></category>

		<guid isPermaLink="false">http://www.bwana.org/2008/03/24/quotably-needs-conversation-context/</guid>
		<description><![CDATA[Yesterday, a new service launched which aims to solve a &#8220;problem&#8221; with Twitter. If you&#8217;re not familiar with Twitter, its purpose is to answer the question, &#8220;What are you doing?&#8221;, so it&#8217;s easy to wonder why you would even expect a response. At any rate, Twitter has evolved into something that no one predicted: The [...]
Related posts:<ul>
<li><a href='http://www.bwana.org/2008/03/28/quotably-adds-user-powered-context/' rel='bookmark' title='Quotably Adds User Powered Context'>Quotably Adds User Powered Context</a></li>
<li><a href='http://www.bwana.org/2009/06/14/friendfeed-still-reigns-as-conversation-king/' rel='bookmark' title='FriendFeed Still Reigns As Conversation King'>FriendFeed Still Reigns As Conversation King</a></li>
<li><a href='http://www.bwana.org/2008/12/28/tweetrees-value-is-embedded-media/' rel='bookmark' title='Tweetree&#8217;s Value Is Embedded Media'>Tweetree&#8217;s Value Is Embedded Media</a></li>
</ul>]]></description>
			<content:encoded><![CDATA[<div align="right" style="float: right; padding: 10px 0px 5px 5px;"><a name="fb_share" type="button_count" share_url="http://www.bwana.org/2008/03/24/quotably-needs-conversation-context/"></a></div><p>Yesterday, a new service launched which aims to solve a &#8220;problem&#8221; with <a href="http://www.twitter.com">Twitter</a>.   If you&#8217;re not familiar with Twitter, its purpose is to answer the question, &#8220;What are you doing?&#8221;, so it&#8217;s easy to wonder why you would even expect a response.  At any rate, Twitter has evolved into something that no one predicted:  <strong>The stock trading floor of tech</strong>.  Except in this case, it&#8217;s not stock that&#8217;s being traded, it&#8217;s tidbits of information.</p>
<p><a href="http://www.flickr.com/photos/bwana/2358913000/" title="Quotably Needs Conversation Context by bwana, on Flickr"><img src="http://farm4.static.flickr.com/3076/2358913000_99c3cdff8c.jpg" width="500" height="327" alt="Quotably Needs Conversation Context" /></a></p>
<p>One of the issues of this phenomenon, is tracking conversations.  If <a href="http://www.twitter.com/scobleizer">Robert Scoble</a> responds a question from someone on Twitter that I&#8217;m not following, I lose the context of the conversation.  It&#8217;s a frustrating task to keep track of what&#8217;s going on.  Enter <a href="http://www.quotably.com">Quotably</a> which aims to solve the &#8220;problem&#8221; of conversation tracking in Twitter.  </p>
<p><a href="http://www.quotably.com" target="new"><img src="http://www.bwana.org/images/quotably_logo_large.png" border="0" /></a></p>
<p>On paper, it sounds like a great idea and will make all of our lives easier.  You simply go to the website, input your Twitter username, and out pops your Twitter conversations.  When I first heard about it, I was instantly skeptical, because I knew the initial design of Twitter did not consider conversations, but only blast messages to the world on what you were doing.  I took a quick look at Quotably, and my assumptions were correct, <strong>conversation context is guessing game</strong>.  It&#8217;s almost impossible to determine the context of any conversation.  If user A responds to user B&#8217;s tweet from yesterday, quotably does its best to fit the conversation in the right thread and most times it gets it wrong.  It&#8217;s inevitable, but I commend Quotably on their efforts.  </p>
<p>Don&#8217;t get me wrong, I believe Quotably has <strong>dramatically</strong> improved the way we look at Twitter, but it doesn&#8217;t fix the underlining problem:  <strong>Twitter needs a re-design</strong>.  <a href="http://friendfeed.com/e/fc4d55e9-4e33-57da-6981-b5dbf7ed93a29">Eric Rice agrees</a>.  There is no way to accomplish this functionality accurately without going to the root of the issue.  To try to aid the issue, I sent this suggestion to the quotably author for consideration:</p>
<p><a href="http://www.flickr.com/photos/bwana/2358838134/" title="Quotably Needs Conversation Context by bwana, on Flickr"><img src="http://farm3.static.flickr.com/2026/2358838134_133c384e51.jpg" width="500" height="201" alt="Quotably Needs Conversation Context" /></a></p>
<p>I believe this will aid the issue, but it will not fix it.  Only Twitter can fix it.  If you think I&#8217;m full of hot air, I took a screenshot of a conversation of Eric Rice and the Twitterverse about this very topic.  <a href="http://farm4.static.flickr.com/3086/2358831338_a50050ff86_o.jpg" title="Eric Rice's twitter conversations - Quotably.com by bwana, on Flickr">Quotably tries, but fails</a>.  While you can make out some of the conversation, it tends to go way off topic.</p>
<p>Is this is a blog post to try to promote FriendFeed over Twitter?  Absolutely not.  As with <a href="http://www.socialthing.com">SocialThing</a>, <a href="http://www.bwana.org/2008/03/15/friendfeed-and-socialthing-are-totally-different/">they can&#8217;t be compared</a>.  As a matter of fact, I would <strong>love</strong> to have richer conversations on Twitter, but it&#8217;s a lost cause.  Twitter needs work.  It&#8217;s not completely their fault either.  We have transformed it into something it wasn&#8217;t meant for, so now Twitter has to adjust.  As for Quotably, I offer this:</p>
<p><a href="http://www.flickr.com/photos/bwana/2358125587/" title="Quotably Needs Conversation Context by bwana, on Flickr"><img src="http://farm3.static.flickr.com/2318/2358125587_a42fdb1f8f.jpg" width="500" height="173" alt="Quotably Needs Conversation Context" /></a></p>
<p>And you can &#8220;quote&#8221; me <img src='http://www.bwana.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Related posts:<ul>
<li><a href='http://www.bwana.org/2008/03/28/quotably-adds-user-powered-context/' rel='bookmark' title='Quotably Adds User Powered Context'>Quotably Adds User Powered Context</a></li>
<li><a href='http://www.bwana.org/2009/06/14/friendfeed-still-reigns-as-conversation-king/' rel='bookmark' title='FriendFeed Still Reigns As Conversation King'>FriendFeed Still Reigns As Conversation King</a></li>
<li><a href='http://www.bwana.org/2008/12/28/tweetrees-value-is-embedded-media/' rel='bookmark' title='Tweetree&#8217;s Value Is Embedded Media'>Tweetree&#8217;s Value Is Embedded Media</a></li>
</ul></p>]]></content:encoded>
			<wfw:commentRss>http://www.bwana.org/2008/03/24/quotably-needs-conversation-context/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
	
		<media:thumbnail url="http://farm4.static.flickr.com/3076/2358913000_99c3cdff8c.jpg" />
		<media:content url="http://farm4.static.flickr.com/3076/2358913000_99c3cdff8c.jpg" medium="image">
			<media:title type="html">Quotably Needs Conversation Context</media:title>
		</media:content>
		<media:content url="http://www.bwana.org/images/quotably_logo_large.png" medium="image" />
		<media:content url="http://farm3.static.flickr.com/2026/2358838134_133c384e51.jpg" medium="image">
			<media:title type="html">Quotably Needs Conversation Context</media:title>
		</media:content>
		<media:content url="http://farm3.static.flickr.com/2318/2358125587_a42fdb1f8f.jpg" medium="image">
			<media:title type="html">Quotably Needs Conversation Context</media:title>
		</media:content>
	</item>
	</channel>
</rss>

