<?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>Tyler Butler &#187; twitter</title>
	<atom:link href="http://www.tylerbutler.com/tags/twitter/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.tylerbutler.com</link>
	<description></description>
	<lastBuildDate>Fri, 14 Aug 2009 22:09:27 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Twitter Experiment</title>
		<link>http://www.tylerbutler.com/2009/06/twitter-experiment/</link>
		<comments>http://www.tylerbutler.com/2009/06/twitter-experiment/#comments</comments>
		<pubDate>Thu, 18 Jun 2009 20:04:46 +0000</pubDate>
		<dc:creator>Tyler</dc:creator>
				<category><![CDATA[Projects]]></category>
		<category><![CDATA[twitter]]></category>
		<category><![CDATA[tylerbutler.com]]></category>

		<guid isPermaLink="false">http://www.tylerbutler.com/?p=489</guid>
		<description><![CDATA[I am experimenting a little with auto-tweeting from my blog to Twitter. In general, I dislike when people do this, for the following reasons:

I get double-exposure to their content. If I am interested enough in someone to follow them on Twitter, and they also have a blog, then 90% of the time I also subscribe [...]]]></description>
			<content:encoded><![CDATA[<p>I am experimenting a little with auto-tweeting from my blog to Twitter. In general, I dislike when people do this, for the following reasons:</p>
<ul>
<li>I get double-exposure to their content. If I am interested enough in someone to follow them on Twitter, and they also have a blog, then 90% of the time I also subscribe to their RSS feed. That means I see their posts in Twitter then also in my feed. That bugs me.</li>
<li>Tweets are limited to 140 characters, and typically blog posts are longer. That means I see 100 characters plus a link, possibly less in the tweet itself. That&#8217;s useless.</li>
</ul>
<p>At the same time, I find myself tweeting a lot of links, because Twitter is just a more vibrant community than my blog. I get a lot more comments and replies from people there than on my blog. Twitter is a decent place to broadcast stuff, but I don&#8217;t like the fact that I can&#8217;t easily find the stuff I&#8217;ve posted later. Have you tried using Twitter search to find a link you yourself posted in the past? It&#8217;s ridiculously bad. I figure if I can just keep it on my own site at least I have more control over the search experience. Another reason I want to do this is to have a centralized place to write stuff, then choose how it&#8217;s syndicated. This will let me do that.</p>
<p>In order to address the two issues I have with common auto-tweet solutions, I&#8217;ll only be tweeting some of my posts. I am doing this by feeding only posts tagged &#8220;<a href="/tags/tweet/">tweet</a>&#8221; to Twitter via <a href="http://twitterfeed.com/">TwitterFeed</a>. In addition, I grabbed a <a href="http://lepslair.com/wp/leprakhauns-character-count-wordpress-plugin/">WordPress plug-in</a> that does character counts of posts in the WordPress web UI. This will help me keep my posts that are auto-tweeted short and completely digestible as a complete tweet.</p>
<p>Hopefully this will all come together and work. Let me know what you think.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.tylerbutler.com/2009/06/twitter-experiment/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Twitter @replies Changes</title>
		<link>http://www.tylerbutler.com/2009/05/twitter-replies-changes/</link>
		<comments>http://www.tylerbutler.com/2009/05/twitter-replies-changes/#comments</comments>
		<pubDate>Wed, 13 May 2009 21:14:27 +0000</pubDate>
		<dc:creator>Tyler</dc:creator>
				<category><![CDATA[Rants]]></category>
		<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://www.tylerbutler.com/?p=405</guid>
		<description><![CDATA[There&#8217;s been some hoopla on Twitter today after a poorly handled announcement that the option to control whether replies from people you follow to people you don&#8217;t follow show up in your feed. This was an option in the Notices section of the Twitter settings that was off by default. The original post from @biz [...]]]></description>
			<content:encoded><![CDATA[<p>There&#8217;s been some hoopla on Twitter today after a <a href="http://blog.twitter.com/2009/05/small-settings-update.html">poorly handled announcement</a> that the option to control whether replies from people you follow to people you don&#8217;t follow show up in your feed. This was an option in the Notices section of the Twitter settings that was off by default. The original post from <a href="http://twitter.com/Biz">@biz</a> made it sound like they were trying to reduce confusion and that it was no big deal. That&#8217;s a bit naive &#8211; they should have seen the backlash coming a mile away&#8230; Dave Winer has <a href="http://www.scripting.com/stories/2009/05/13/lessonsFromTheChangesInTwi.html">a good summary</a> of problems with how they messaged things.</p>
<p>@biz later posted that they had heard the feedback, claiming it was a scalability problem with the implementation. I initially didn&#8217;t buy that argument, but the <a href="http://www.readwriteweb.com/archives/is_this_why_twitter_changed_its_replies_policy.php">description over at ReadWriteWeb</a> clarifies things somewhat. <a href="http://www.scripting.com/stories/2009/05/13/lessonsFromTheChangesInTwi.html#comment-9291130">This comment</a> over at Winer&#8217;s post clarifies it further. I think I understand now, given their architecture, why this would be a beneficial change for them to make.</p>
<p>But that&#8217;s not what I&#8217;m ultimately writing about. Much of the complaining from people opposed to the change has been that it makes it harder to meet new people on Twitter. If you see a reply to someone else from a person you follow then you might also be interested in following them. OK, fine, I buy that, but for me, I simply want to see <strong>everything</strong> people I follow say, regardless of who they say it to. With clients like <a href="http://www.atebits.com/tweetie-mac/">Tweetie</a> and <a href="http://phobos.apple.com/WebObjects/MZStore.woa/wa/viewSoftware?id=284540316&amp;mt=8">Twitterrific 2.0 (iTunes link)</a> able to browse through conversations effortlessly, I can use the tweets from my timeline as a jumping-off point to see the whole conversation which someone I <strong>am</strong> interested in is involved in. My goal is not to find new people to follow (though that does happen occasionally), but rather, just to see what interesting things people I follow are saying. I don&#8217;t care who they&#8217;re talking to. It&#8217;s not like everything <a href="http://twitter.com/Lincolnator">@Lincolnator</a> says to <a href="http://twitter.com/MajorLB">@MajorLB</a> is completely uninteresting to me just because I don&#8217;t follow her.</p>
<p><a href="http://blog.twitter.com/2009/05/we-learned-lot.html">The proposed changes</a> as they stand right now don&#8217;t solve my complaint. But it&#8217;s early; the smart people at Twitter will figure something out, and hopefully, it&#8217;ll solve my scenario and world hunger at the same time. One can hope and dream.</p>
<p>You can see the protests/commentary onTwitter itself by <a href="http://search.twitter.com/search?q=%23Fixreplies">searching for #fixreplies</a>. It&#8217;s still the top trending search term as of this writing.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.tylerbutler.com/2009/05/twitter-replies-changes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
