<?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: Read/Unread on Twitter</title>
	<atom:link href="http://alexking.org/blog/2009/11/04/twitter-read-unread-state/feed" rel="self" type="application/rss+xml" />
	<link>http://alexking.org/blog/2009/11/04/twitter-read-unread-state</link>
	<description>Alex King, Denver Web Developer</description>
	<lastBuildDate>Thu, 24 May 2012 16:30:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Jason Berman</title>
		<link>http://alexking.org/blog/2009/11/04/twitter-read-unread-state#comment-112731</link>
		<dc:creator>Jason Berman</dc:creator>
		<pubDate>Tue, 10 Nov 2009 17:05:33 +0000</pubDate>
		<guid isPermaLink="false">http://alexking.org/?p=3753#comment-112731</guid>
		<description>Been taking a look at CoTweet today. They have an option to archive tweets. As a gMail user, this resonated with me. Interesting interface. Probably looks awesome as an SSB. JB</description>
		<content:encoded><![CDATA[<p>Been taking a look at CoTweet today. They have an option to archive tweets. As a gMail user, this resonated with me. Interesting interface. Probably looks awesome as an SSB. JB</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://alexking.org/blog/2009/11/04/twitter-read-unread-state#comment-110305</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Wed, 04 Nov 2009 18:20:22 +0000</pubDate>
		<guid isPermaLink="false">http://alexking.org/?p=3753#comment-110305</guid>
		<description>Sorry I wasn&#039;t more clear. Tweetie (Mac) lets you turn off the notification in the dock and menu bar, but the little blue dots persist in the application window.</description>
		<content:encoded><![CDATA[<p>Sorry I wasn&#8217;t more clear. Tweetie (Mac) lets you turn off the notification in the dock and menu bar, but the little blue dots persist in the application window.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://alexking.org/blog/2009/11/04/twitter-read-unread-state#comment-110284</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Wed, 04 Nov 2009 17:14:27 +0000</pubDate>
		<guid isPermaLink="false">http://alexking.org/?p=3753#comment-110284</guid>
		<description>Tweetie has an option to turn off the blue light. Just go to preferences/account/notification options.</description>
		<content:encoded><![CDATA[<p>Tweetie has an option to turn off the blue light. Just go to preferences/account/notification options.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Devin Reams</title>
		<link>http://alexking.org/blog/2009/11/04/twitter-read-unread-state#comment-110266</link>
		<dc:creator>Devin Reams</dc:creator>
		<pubDate>Wed, 04 Nov 2009 15:15:29 +0000</pubDate>
		<guid isPermaLink="false">http://alexking.org/?p=3753#comment-110266</guid>
		<description>I can&#039;t remember if I read it on Loren&#039;s blog, TechCrunch or elsewhere, but he&#039;s suggesting that when the next version of Tweetie for Mac comes out he&#039;ll be able to sync your current position (like when you close the app on the iPhone, it remembers how far you&#039;ve scrolled). That&#039;ll be a big win for me..</description>
		<content:encoded><![CDATA[<p>I can&#8217;t remember if I read it on Loren&#8217;s blog, TechCrunch or elsewhere, but he&#8217;s suggesting that when the next version of Tweetie for Mac comes out he&#8217;ll be able to sync your current position (like when you close the app on the iPhone, it remembers how far you&#8217;ve scrolled). That&#8217;ll be a big win for me..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://alexking.org/blog/2009/11/04/twitter-read-unread-state#comment-110265</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Wed, 04 Nov 2009 14:40:58 +0000</pubDate>
		<guid isPermaLink="false">http://alexking.org/?p=3753#comment-110265</guid>
		<description>I don&#039;t think client to client sync is a solution - ultimately there needs to be a central data source/API. Perhaps an opportunity for someone to build one and try to get the clients to integrate with it (think: equivalent of what Summize did for search).</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think client to client sync is a solution &#8211; ultimately there needs to be a central data source/API. Perhaps an opportunity for someone to build one and try to get the clients to integrate with it (think: equivalent of what Summize did for search).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Arnold</title>
		<link>http://alexking.org/blog/2009/11/04/twitter-read-unread-state#comment-110264</link>
		<dc:creator>Brian Arnold</dc:creator>
		<pubDate>Wed, 04 Nov 2009 14:37:28 +0000</pubDate>
		<guid isPermaLink="false">http://alexking.org/?p=3753#comment-110264</guid>
		<description>That&#039;s the one thing TweetDeck tries to do that seems solid - you sign up for an account there, and then the clients sync up read/unread state.

That being said, Tweetie is just too nice to not use, so I wind up doing a manual sync, in that I try to stick to just one client at a time, and when I make a move that changes what client I&#039;ll be using (sitting down at a computer for long periods, leaving said computer for long periods), I fire up the other client and do a fast mark all as read.

I&#039;m hoping that when the Tweetie 2 iPhone changes propagate out into the desktop client, that something like TD&#039;s syncing happens, though I doubt it actually will.</description>
		<content:encoded><![CDATA[<p>That&#8217;s the one thing TweetDeck tries to do that seems solid &#8211; you sign up for an account there, and then the clients sync up read/unread state.</p>
<p>That being said, Tweetie is just too nice to not use, so I wind up doing a manual sync, in that I try to stick to just one client at a time, and when I make a move that changes what client I&#8217;ll be using (sitting down at a computer for long periods, leaving said computer for long periods), I fire up the other client and do a fast mark all as read.</p>
<p>I&#8217;m hoping that when the Tweetie 2 iPhone changes propagate out into the desktop client, that something like TD&#8217;s syncing happens, though I doubt it actually will.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://alexking.org/blog/2009/11/04/twitter-read-unread-state#comment-110263</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Wed, 04 Nov 2009 14:36:57 +0000</pubDate>
		<guid isPermaLink="false">http://alexking.org/?p=3753#comment-110263</guid>
		<description>I just want it for @replies and DMs - you know, the stuff Twitter clients are already tracking read/unread status for individually.</description>
		<content:encoded><![CDATA[<p>I just want it for @replies and DMs &#8211; you know, the stuff Twitter clients are already tracking read/unread status for individually.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Derek Gathright</title>
		<link>http://alexking.org/blog/2009/11/04/twitter-read-unread-state#comment-110262</link>
		<dc:creator>Derek Gathright</dc:creator>
		<pubDate>Wed, 04 Nov 2009 14:35:17 +0000</pubDate>
		<guid isPermaLink="false">http://alexking.org/?p=3753#comment-110262</guid>
		<description>I&#039;ve integrated read/unread into my client (Tweenky) a few times using various methods, and always remove it because, in my opinion, read/unread with the status updates medium is a bad idea.  There&#039;s just too much data there.  The day I realized &quot;Hey, I -don&#039;t- have to read everything on Twitter&quot;, I felt very liberated.

I&#039;d be shocked if Twitter ever implemented read/unread at the API level.  Just think about the storage aspects of 1,000,000 people viewing 1,000,000 tweets and Twitter having to keep track of who has looked at what.  And that doesn&#039;t even scratch the surface of what flows through that network on a daily bases.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve integrated read/unread into my client (Tweenky) a few times using various methods, and always remove it because, in my opinion, read/unread with the status updates medium is a bad idea.  There&#8217;s just too much data there.  The day I realized &#8220;Hey, I -don&#8217;t- have to read everything on Twitter&#8221;, I felt very liberated.</p>
<p>I&#8217;d be shocked if Twitter ever implemented read/unread at the API level.  Just think about the storage aspects of 1,000,000 people viewing 1,000,000 tweets and Twitter having to keep track of who has looked at what.  And that doesn&#8217;t even scratch the surface of what flows through that network on a daily bases.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

