<?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: Twitter Changes &#8220;From&#8221; Display</title>
	<atom:link href="http://www.socialoomphblog.com/twitter-changes-from-display/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.socialoomphblog.com/twitter-changes-from-display/</link>
	<description></description>
	<lastBuildDate>Mon, 09 Aug 2010 00:41:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: JenChicago</title>
		<link>http://www.socialoomphblog.com/twitter-changes-from-display/#comment-347</link>
		<dc:creator>JenChicago</dc:creator>
		<pubDate>Tue, 28 Jul 2009 19:30:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.socialoomphblog.com/?p=284#comment-347</guid>
		<description>I appreciate the write up!  I was wondering what that meant.  Man!  You can find answers to anything online!</description>
		<content:encoded><![CDATA[<p>I appreciate the write up!  I was wondering what that meant.  Man!  You can find answers to anything online!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: krau</title>
		<link>http://www.socialoomphblog.com/twitter-changes-from-display/#comment-333</link>
		<dc:creator>krau</dc:creator>
		<pubDate>Wed, 08 Jul 2009 10:24:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.socialoomphblog.com/?p=284#comment-333</guid>
		<description>&quot;From API&quot; leave it, please. It&#039;s the best alternative.</description>
		<content:encoded><![CDATA[<p>&#8220;From API&#8221; leave it, please. It&#39;s the best alternative.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: klankford</title>
		<link>http://www.socialoomphblog.com/twitter-changes-from-display/#comment-320</link>
		<dc:creator>klankford</dc:creator>
		<pubDate>Mon, 06 Jul 2009 15:39:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.socialoomphblog.com/?p=284#comment-320</guid>
		<description>I truly trust tweetlater to do what is best and will continue to use it no matter what all this techno-babble means!</description>
		<content:encoded><![CDATA[<p>I truly trust tweetlater to do what is best and will continue to use it no matter what all this techno-babble means!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Lankford</title>
		<link>http://www.socialoomphblog.com/twitter-changes-from-display/#comment-319</link>
		<dc:creator>Kevin Lankford</dc:creator>
		<pubDate>Mon, 06 Jul 2009 15:37:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.socialoomphblog.com/?p=284#comment-319</guid>
		<description>I love the Tweetlater concept and if you have to that &quot;Tweetstream&quot; idea really does sound like a good one. API or whatever else doesn&#039;t matter much to me as long as I an not considered a spammer.</description>
		<content:encoded><![CDATA[<p>I love the Tweetlater concept and if you have to that &#8220;Tweetstream&#8221; idea really does sound like a good one. API or whatever else doesn&#39;t matter much to me as long as I an not considered a spammer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jake McKee</title>
		<link>http://www.socialoomphblog.com/twitter-changes-from-display/#comment-257</link>
		<dc:creator>Jake McKee</dc:creator>
		<pubDate>Sat, 04 Jul 2009 19:23:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.socialoomphblog.com/?p=284#comment-257</guid>
		<description>So reading the update (very helpful, thanks), I&#039;d suggest that you still maintain the &quot;from API&quot;.... because that can sorta mask the posting source. i.e. it&#039;s impossible to know (in a reader&#039;s mind, at least) whether this tweet came from a desktop app in real time or a future post service like tweetlater. &lt;br&gt;&lt;br&gt;Is it possible to toggle a preference for this by individual user?</description>
		<content:encoded><![CDATA[<p>So reading the update (very helpful, thanks), I&#39;d suggest that you still maintain the &#8220;from API&#8221;&#8230;. because that can sorta mask the posting source. i.e. it&#39;s impossible to know (in a reader&#39;s mind, at least) whether this tweet came from a desktop app in real time or a future post service like tweetlater. </p>
<p>Is it possible to toggle a preference for this by individual user?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan</title>
		<link>http://www.socialoomphblog.com/twitter-changes-from-display/#comment-256</link>
		<dc:creator>Alan</dc:creator>
		<pubDate>Sat, 04 Jul 2009 06:25:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.socialoomphblog.com/?p=284#comment-256</guid>
		<description>I am cool with API, but if you use Tweetlater, it will identify that we are using this great tool, and not actually tweeting at real time. This tool, is great for my business tweets, but would be less effective if it said tweet later. I agree the word of mouth is good for your service, I speak about it all the time with other business owners.</description>
		<content:encoded><![CDATA[<p>I am cool with API, but if you use Tweetlater, it will identify that we are using this great tool, and not actually tweeting at real time. This tool, is great for my business tweets, but would be less effective if it said tweet later. I agree the word of mouth is good for your service, I speak about it all the time with other business owners.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pat</title>
		<link>http://www.socialoomphblog.com/twitter-changes-from-display/#comment-255</link>
		<dc:creator>Pat</dc:creator>
		<pubDate>Sat, 04 Jul 2009 01:02:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.socialoomphblog.com/?p=284#comment-255</guid>
		<description>The Twitter world is getting very used to receiving communications from multiple sources. I have received a wealth of fantastic information on all subjects imaginable from third party sources. What matters is getting a response when a comment or feedback is offered.  So it is the @replies and DM&#039;s that make it or break it. I would RATHER have tweets with great links and content coming from Tweetlater to get me the info, let me read it, and then get a &quot;gee thanks&quot; when I RT or an answer when I @reply them. It&#039;s all good if the follow up is handled, in my opinion.</description>
		<content:encoded><![CDATA[<p>The Twitter world is getting very used to receiving communications from multiple sources. I have received a wealth of fantastic information on all subjects imaginable from third party sources. What matters is getting a response when a comment or feedback is offered.  So it is the @replies and DM&#39;s that make it or break it. I would RATHER have tweets with great links and content coming from Tweetlater to get me the info, let me read it, and then get a &#8220;gee thanks&#8221; when I RT or an answer when I @reply them. It&#39;s all good if the follow up is handled, in my opinion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Murff</title>
		<link>http://www.socialoomphblog.com/twitter-changes-from-display/#comment-254</link>
		<dc:creator>Murff</dc:creator>
		<pubDate>Sat, 04 Jul 2009 00:45:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.socialoomphblog.com/?p=284#comment-254</guid>
		<description>I would have preferred &quot;from web&quot; as it disguises the fact that it is coming from a bot. Now everyone will know what is going on and our secret is lost for ever. What a nuisance.</description>
		<content:encoded><![CDATA[<p>I would have preferred &#8220;from web&#8221; as it disguises the fact that it is coming from a bot. Now everyone will know what is going on and our secret is lost for ever. What a nuisance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rachel Keslensky - Last Res0rt</title>
		<link>http://www.socialoomphblog.com/twitter-changes-from-display/#comment-253</link>
		<dc:creator>Rachel Keslensky - Last Res0rt</dc:creator>
		<pubDate>Fri, 03 Jul 2009 20:49:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.socialoomphblog.com/?p=284#comment-253</guid>
		<description>Because as we all know, everyone stopped using blogs and reading webcomics when we discovered that people could automate their posts, right?&lt;br&gt;&lt;br&gt;I like the &quot;Tweetstream&quot; idea someone else suggested, but anyone who cares will find out one way or another, really. If disguising the source is the only way this service can survive, something is fundamentally wrong with it.</description>
		<content:encoded><![CDATA[<p>Because as we all know, everyone stopped using blogs and reading webcomics when we discovered that people could automate their posts, right?</p>
<p>I like the &#8220;Tweetstream&#8221; idea someone else suggested, but anyone who cares will find out one way or another, really. If disguising the source is the only way this service can survive, something is fundamentally wrong with it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dewald Pretorius</title>
		<link>http://www.socialoomphblog.com/twitter-changes-from-display/#comment-252</link>
		<dc:creator>Dewald Pretorius</dc:creator>
		<pubDate>Fri, 03 Jul 2009 20:39:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.socialoomphblog.com/?p=284#comment-252</guid>
		<description>Unfortunately, &quot;web&quot; is not an option. That is now reserved for tweets submitted from the Twitter web interface.</description>
		<content:encoded><![CDATA[<p>Unfortunately, &#8220;web&#8221; is not an option. That is now reserved for tweets submitted from the Twitter web interface.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
