<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for sethlong.com</title>
	<atom:link href="http://sethlong.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://sethlong.com</link>
	<description>&#34;If everything is under control, you’re not going fast enough.&#34; -Mario Andretti</description>
	<lastBuildDate>Thu, 01 Apr 2010 21:11:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>Comment on What&#8217;s wrong with the Nexus One? by paulbalcerak</title>
		<link>http://sethlong.com/2010/03/31/whats-wrong-with-the-nexus-one/#comment-116</link>
		<dc:creator><![CDATA[paulbalcerak]]></dc:creator>
		<pubDate>Thu, 01 Apr 2010 21:11:15 +0000</pubDate>
		<guid isPermaLink="false">http://sethlong.com/?p=244#comment-116</guid>
		<description><![CDATA[I think I said this before, but I feel like if I&#039;d never used an iPhone, the Nexus One would be pretty awesome. I didn&#039;t get a thorough testing of it (couldn&#039;t access the wireless network I was near over the weekend) but I was also mainly hamstrung by the awkward typing. Even after using it for a while, it took me a good 5-7 minutes to type a two-paragraph e-mail—&lt;em&gt;way&lt;/em&gt; too long, in my opinion. (Tangent: Touch-screen keyboards should be standardized with regard to character/punctuation placement, the way QWERTY standardized where the letters go. The way the comma and period flank the N1&#039;s spacebar make for too many mis-clicks and beg for the phone to be thrown.)

Pros: Screen is &lt;em&gt;super&lt;/em&gt; crisp; it was nerd nirvana having a phone with a Google logo on it.

Cons: I can&#039;t see the screen in the sunlight; there aren&#039;t enough apps; keyboard is frustrating; there&#039;s a delay in the UI a little too often.]]></description>
		<content:encoded><![CDATA[<p>I think I said this before, but I feel like if I&#8217;d never used an iPhone, the Nexus One would be pretty awesome. I didn&#8217;t get a thorough testing of it (couldn&#8217;t access the wireless network I was near over the weekend) but I was also mainly hamstrung by the awkward typing. Even after using it for a while, it took me a good 5-7 minutes to type a two-paragraph e-mail—<em>way</em> too long, in my opinion. (Tangent: Touch-screen keyboards should be standardized with regard to character/punctuation placement, the way QWERTY standardized where the letters go. The way the comma and period flank the N1&#8242;s spacebar make for too many mis-clicks and beg for the phone to be thrown.)</p>
<p>Pros: Screen is <em>super</em> crisp; it was nerd nirvana having a phone with a Google logo on it.</p>
<p>Cons: I can&#8217;t see the screen in the sunlight; there aren&#8217;t enough apps; keyboard is frustrating; there&#8217;s a delay in the UI a little too often.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What can news orgs learn from content farms? by paulbalcerak</title>
		<link>http://sethlong.com/2010/03/31/what-can-news-orgs-learn-from-content-farms/#comment-115</link>
		<dc:creator><![CDATA[paulbalcerak]]></dc:creator>
		<pubDate>Thu, 01 Apr 2010 16:23:20 +0000</pubDate>
		<guid isPermaLink="false">http://sethlong.com/?p=238#comment-115</guid>
		<description><![CDATA[You should syndicate this on the company blog :)]]></description>
		<content:encoded><![CDATA[<p>You should syndicate this on the company blog <img src='http://s0.wp.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on My personal backup strategy by David Friend</title>
		<link>http://sethlong.com/2009/10/23/personal-backup-strategy/#comment-111</link>
		<dc:creator><![CDATA[David Friend]]></dc:creator>
		<pubDate>Thu, 03 Dec 2009 19:34:44 +0000</pubDate>
		<guid isPermaLink="false">http://sethlong.com/?p=204#comment-111</guid>
		<description><![CDATA[Seth:  Thanks for mentioning Carbonite.  I&#039;m the CEO and I&#039;d love to be able to correspond with you.   Could you shoot me an email?   THanks. 

Dave Friend]]></description>
		<content:encoded><![CDATA[<p>Seth:  Thanks for mentioning Carbonite.  I&#8217;m the CEO and I&#8217;d love to be able to correspond with you.   Could you shoot me an email?   THanks. </p>
<p>Dave Friend</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Twitter is not just for headlines by Paul Balcerak</title>
		<link>http://sethlong.com/2009/10/27/twitter-not-just-for-newspaper-headlines/#comment-102</link>
		<dc:creator><![CDATA[Paul Balcerak]]></dc:creator>
		<pubDate>Thu, 29 Oct 2009 17:23:57 +0000</pubDate>
		<guid isPermaLink="false">http://sethlong.com/?p=201#comment-102</guid>
		<description><![CDATA[Well yeah, that&#039;s the &quot;if you had the manpower&quot; part. One person at a news org can easily get 1,000 followers built up in a relatively short amount of time. If each niche reporter were doing that, you could maybe get something going (like selling specified ads on section fronts).]]></description>
		<content:encoded><![CDATA[<p>Well yeah, that&#8217;s the &#8220;if you had the manpower&#8221; part. One person at a news org can easily get 1,000 followers built up in a relatively short amount of time. If each niche reporter were doing that, you could maybe get something going (like selling specified ads on section fronts).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Twitter is not just for headlines by Seth</title>
		<link>http://sethlong.com/2009/10/27/twitter-not-just-for-newspaper-headlines/#comment-101</link>
		<dc:creator><![CDATA[Seth]]></dc:creator>
		<pubDate>Thu, 29 Oct 2009 07:27:58 +0000</pubDate>
		<guid isPermaLink="false">http://sethlong.com/?p=201#comment-101</guid>
		<description><![CDATA[I agree about tagging sponsor Tweets with AD or [AD]. I&#039;m not sure, though, that I would want ads in channel-specific feeds. Unless you&#039;re a large news org, it seems like getting enough followers to those niche feeds to make them attractive to advertisers would be a challenge.]]></description>
		<content:encoded><![CDATA[<p>I agree about tagging sponsor Tweets with AD or [AD]. I&#8217;m not sure, though, that I would want ads in channel-specific feeds. Unless you&#8217;re a large news org, it seems like getting enough followers to those niche feeds to make them attractive to advertisers would be a challenge.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Twitter is not just for headlines by Paul Balcerak</title>
		<link>http://sethlong.com/2009/10/27/twitter-not-just-for-newspaper-headlines/#comment-100</link>
		<dc:creator><![CDATA[Paul Balcerak]]></dc:creator>
		<pubDate>Wed, 28 Oct 2009 23:38:10 +0000</pubDate>
		<guid isPermaLink="false">http://sethlong.com/?p=201#comment-100</guid>
		<description><![CDATA[I like the idea of timed Tweets. Another great idea, if you had the manpower, would be to split up your Web site/newspaper sections into their own Twitter feeds—sports, entertainment, etc. That way, you&#039;d be able to target advertisers with more of a niche market. Sure, you can&#039;t be positive that everyone following you likes sports (God knows there&#039;s spam on Twitter), but you can reasonably assume that X percentage of your followers are legit.

My only thing from an editorial standpoint is that I&#039;d want some kind of common label to denote the fact that each Tweet was an ad. For example, I loop my blog posts into Twitterfeed and I have it set up so that when a headline goes out, it&#039;s preceded by &quot;paulbalcerak.com:.&quot; Similarly, I&#039;d put something like &quot;Ad:&quot; in front of every sponsored Tweet.]]></description>
		<content:encoded><![CDATA[<p>I like the idea of timed Tweets. Another great idea, if you had the manpower, would be to split up your Web site/newspaper sections into their own Twitter feeds—sports, entertainment, etc. That way, you&#8217;d be able to target advertisers with more of a niche market. Sure, you can&#8217;t be positive that everyone following you likes sports (God knows there&#8217;s spam on Twitter), but you can reasonably assume that X percentage of your followers are legit.</p>
<p>My only thing from an editorial standpoint is that I&#8217;d want some kind of common label to denote the fact that each Tweet was an ad. For example, I loop my blog posts into Twitterfeed and I have it set up so that when a headline goes out, it&#8217;s preceded by &#8220;paulbalcerak.com:.&#8221; Similarly, I&#8217;d put something like &#8220;Ad:&#8221; in front of every sponsored Tweet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A short URL service of our own by Twitter is not just for headlines &#171; sethlong.com</title>
		<link>http://sethlong.com/2009/08/26/a-short-url-service-of-our-own/#comment-97</link>
		<dc:creator><![CDATA[Twitter is not just for headlines &#171; sethlong.com]]></dc:creator>
		<pubDate>Tue, 27 Oct 2009 17:44:11 +0000</pubDate>
		<guid isPermaLink="false">http://sethlong.com/?p=193#comment-97</guid>
		<description><![CDATA[[...] Oh yeah, don&#8217;t forget to use your own short URL service! [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Oh yeah, don&#8217;t forget to use your own short URL service! [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on My personal backup strategy by Extending the cloud with backup services &#171; sethlong.com</title>
		<link>http://sethlong.com/2009/10/23/personal-backup-strategy/#comment-96</link>
		<dc:creator><![CDATA[Extending the cloud with backup services &#171; sethlong.com]]></dc:creator>
		<pubDate>Sat, 24 Oct 2009 07:45:32 +0000</pubDate>
		<guid isPermaLink="false">http://sethlong.com/?p=204#comment-96</guid>
		<description><![CDATA[[...] Older &#187; [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Older &raquo; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Short URL integration idea by A short URL service of our own &#171; sethlong.com</title>
		<link>http://sethlong.com/2009/07/14/short-url-integration-idea/#comment-90</link>
		<dc:creator><![CDATA[A short URL service of our own &#171; sethlong.com]]></dc:creator>
		<pubDate>Thu, 27 Aug 2009 03:57:38 +0000</pubDate>
		<guid isPermaLink="false">http://sethlong.com/?p=185#comment-90</guid>
		<description><![CDATA[[...] from the same author. The plugin comes dangerously close to giving me the workflow I described in an earlier post. The plugin can be configured to automatically generate a short URL for each published post and/or [...]]]></description>
		<content:encoded><![CDATA[<p>[...] from the same author. The plugin comes dangerously close to giving me the workflow I described in an earlier post. The plugin can be configured to automatically generate a short URL for each published post and/or [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on New job by andy</title>
		<link>http://sethlong.com/2007/12/06/new-job/#comment-85</link>
		<dc:creator><![CDATA[andy]]></dc:creator>
		<pubDate>Tue, 08 Jan 2008 07:32:05 +0000</pubDate>
		<guid isPermaLink="false">http://skip.wordpress.com/2007/12/06/new-job/#comment-85</guid>
		<description><![CDATA[Congratulations on the new gig. Sounds very neat. Started one of my own just today.
]]></description>
		<content:encoded><![CDATA[<p>Congratulations on the new gig. Sounds very neat. Started one of my own just today.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

