<?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/"
	>

<channel>
	<title>bill.cava.us &#187; twitter</title>
	<atom:link href="http://bill.cava.us/index.php/category/twitter/feed/" rel="self" type="application/rss+xml" />
	<link>http://bill.cava.us</link>
	<description></description>
	<lastBuildDate>Thu, 08 Jul 2010 21:18:25 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Twitter Lists Lacking Community Curation</title>
		<link>http://bill.cava.us/index.php/2009/10/30/twitter-lists-lack-curation/</link>
		<comments>http://bill.cava.us/index.php/2009/10/30/twitter-lists-lack-curation/#comments</comments>
		<pubDate>Fri, 30 Oct 2009 15:55:36 +0000</pubDate>
		<dc:creator>bill</dc:creator>
				<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://bill.cava.us/?p=128</guid>
		<description><![CDATA[The term “Twitter List” is trending on Twitter today, looks like the feature has been opened up to everyone. I was included in an early release wave and have been playing with it for a bit now. Generally I like it and think it’s a very useful feature, but it’s more interesting to note what [...]]]></description>
			<content:encoded><![CDATA[<p>The term “<a href="http://twitter.com/#search?q=%22Twitter%20Lists%22%20OR%20Lists">Twitter List</a>” is trending on Twitter today, looks like the feature has been opened up to everyone. I was included in an early release wave and have been playing with it for a bit now. Generally I like it and think it’s a very useful feature, but it’s more interesting to note what was <em>not</em> included in it.</p>
<p>The ultimate value of Twitter Lists is for converting potential ties (people you don’t know yet) into weak or strong ties (see Granovetter&#8217;s <a href="http://www.analytictech.com/networks/weakties.htm">Theory of the Strength of Weak Ties</a>).</p>
<p>Delicious does this well. On Delicious, each person has their own local tagspace (all bookmarks tagged by that individual), but contributes to a global pool of bookmarks visible to everyone. For example, I can subscribe to the bookmarks tagged “openid” by <a href="http://blog.jonudell.net/2009/02/26/collaborative-curation-as-a-service/">Jon Udell</a> by visiting his stream here <a href="http://delicious.com/judell/openid">http://delicious.com/judell/openid</a>, and see the global pool of all bookmarks tagged “openid” here <a href="http://delicious.com/tag/openid">http://delicious.com/tag/openid</a>.</p>
<p>When I access Jon’s local tagspace, I do so knowing that there will be fewer but typically higher quality bookmarks. When I access the global tagspace, I recognize there will be more to sift through, but I can use it to discover new people interested in “openid”.</p>
<p>Translating this to Twitter, the Lists feature provides a “local tagspace” and there is no notion of a “global tagspace”. While the signal-to-noise ratio of the local list is greater, it decreases the opportunity for further discovering other users and other lists. This hole opens the door for a third part to step in to categorize and aggregate Lists across users (updated: <a href="http://listorious.com/">Listorious </a>launches attempting to do just this).</p>
<p>In a nutshell, I like the local List concept. I imagine the notion of a global List was left out because of the ability for spammers to abuse it. Ultimately, Bing and Google see the holy grail for Lists being a service that automatically pulls in the best tweets for a given category or term. I can see value in that. But I think Delicious style community curation is a powerful discovery mechanism relevant to Twitter and, I would argue, is lacking in the current implementation of Twitter Lists.</p>
]]></content:encoded>
			<wfw:commentRss>http://bill.cava.us/index.php/2009/10/30/twitter-lists-lack-curation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>uber extensible twitter client</title>
		<link>http://bill.cava.us/index.php/2009/09/04/uber-extensible-twitter-client/</link>
		<comments>http://bill.cava.us/index.php/2009/09/04/uber-extensible-twitter-client/#comments</comments>
		<pubDate>Fri, 04 Sep 2009 20:21:57 +0000</pubDate>
		<dc:creator>bill</dc:creator>
				<category><![CDATA[twitter]]></category>
		<category><![CDATA[lazyweb]]></category>

		<guid isPermaLink="false">http://bill.cava.us/?p=158</guid>
		<description><![CDATA[Dear lazyweb, i would like an extensible twitter client by christmas please. Think FireFox for Twitter. Seesmic and TweetDeck have an opportunity here to gain significant adoption by creating a developer ecosystem around its client, making it possible for developers to build niche plugins w/o burdening the core product with cruft. Not only that, but [...]]]></description>
			<content:encoded><![CDATA[<p>Dear lazyweb, i would like an extensible twitter client by christmas please. Think FireFox for Twitter. Seesmic and TweetDeck have an opportunity here to gain significant adoption by creating a developer ecosystem around its client, making it possible for developers to build niche plugins w/o burdening the core product with cruft. Not only that, but think of all the applications currently in development that will have some type of &#8220;activity stream&#8221; &#8212; without an open client, we&#8217;ll see a flood of new clients repeating the same functionality over and over. It&#8217;s only a matter of time before we see an open client, but lazyweb, it would make a nice present for christmas. </p>
]]></content:encoded>
			<wfw:commentRss>http://bill.cava.us/index.php/2009/09/04/uber-extensible-twitter-client/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>simplicity kills twitter?</title>
		<link>http://bill.cava.us/index.php/2008/12/19/simplicity-kills-twitter/</link>
		<comments>http://bill.cava.us/index.php/2008/12/19/simplicity-kills-twitter/#comments</comments>
		<pubDate>Fri, 19 Dec 2008 21:33:31 +0000</pubDate>
		<dc:creator>bill</dc:creator>
				<category><![CDATA[simplicity]]></category>
		<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://bill.cava.us/?p=72</guid>
		<description><![CDATA[As someone who fancies minimalism I dig Twitter’s concise feature set, tho I knew it was only a matter of time before an uber-twitter showed itself. @cmswire heralded it&#8217;s arrival in a post about a feature rich microblogging site called Yonkley. It let&#8217;s you:


* create a microblogging site around any subject area (a twitter vertical).
* [...]]]></description>
			<content:encoded><![CDATA[<p>As someone who fancies minimalism I dig Twitter’s concise feature set, tho I knew it was only a matter of time before an uber-twitter showed itself. <a href="http://twitter.com/cmswire/status/1065688191">@cmswire</a> heralded it&#8217;s arrival in a post about a feature rich microblogging site called Yonkley. It let&#8217;s you:</p>
<blockquote>
<ul>
<li>* create a microblogging site around any subject area (a twitter vertical).</li>
<li>* customize, brand, theme</li>
<li>* add adverts</li>
<li>* increase the character limit to above twitter&#8217;s 140 characters</li>
</ul>
</blockquote>
<p dir="ltr">Is the answer for twitter to bulk up on features? In some areas, YES! Hey Twitter, get <a href="http://www.google.com/search?q=site%3Atwitter.com+%22find+people%22+removed">people search</a> working! Beyond that, no. Twitter just needs to start better promoting the <a href="http://www.stumbleupon.com/tag/twitter/">many</a> sites out there built on their APIs. My favorite, <a href="http://qwitter.com/">qwitter</a>.</p>
<p dir="ltr"><em>discovered </em><a href="http://tinyurl.com/4qwoer"><em>via @cmswire</em></a><em> Yonkly: The Next Twitter Killer?</em></p>
<p dir="ltr">
]]></content:encoded>
			<wfw:commentRss>http://bill.cava.us/index.php/2008/12/19/simplicity-kills-twitter/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
