<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Tweet Later - Latest Comments in Twitter Changes &amp;#8220;From&amp;#8221; Display</title><link>http://tweetlater.disqus.com/</link><description></description><atom:link href="https://tweetlater.disqus.com/twitter_changes_8220from8221_display/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Tue, 28 Jul 2009 15:30:04 -0000</lastBuildDate><item><title>Re: Twitter Changes &amp;#8220;From&amp;#8221; Display</title><link>http://www.tweetlaterblog.com/twitter-changes-from-display/#comment-13477871</link><description>&lt;p&gt;I appreciate the write up!  I was wondering what that meant.  Man!  You can find answers to anything online!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">JenChicago</dc:creator><pubDate>Tue, 28 Jul 2009 15:30:04 -0000</pubDate></item><item><title>Re: Twitter Changes &amp;#8220;From&amp;#8221; Display</title><link>http://www.tweetlaterblog.com/twitter-changes-from-display/#comment-12305602</link><description>&lt;p&gt;"From API" leave it, please. It's the best alternative.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kraucrow</dc:creator><pubDate>Wed, 08 Jul 2009 06:24:55 -0000</pubDate></item><item><title>Re: Twitter Changes &amp;#8220;From&amp;#8221; Display</title><link>http://www.tweetlaterblog.com/twitter-changes-from-display/#comment-12198287</link><description>&lt;p&gt;I truly trust tweetlater to do what is best and will continue to use it no matter what all this techno-babble means!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">klankford</dc:creator><pubDate>Mon, 06 Jul 2009 11:39:38 -0000</pubDate></item><item><title>Re: Twitter Changes &amp;#8220;From&amp;#8221; Display</title><link>http://www.tweetlaterblog.com/twitter-changes-from-display/#comment-12198234</link><description>&lt;p&gt;I love the Tweetlater concept and if you have to that "Tweetstream" idea really does sound like a good one. API or whatever else doesn't matter much to me as long as I an not considered a spammer. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Kevin Lankford</dc:creator><pubDate>Mon, 06 Jul 2009 11:37:27 -0000</pubDate></item><item><title>Re: Twitter Changes &amp;#8220;From&amp;#8221; Display</title><link>http://www.tweetlaterblog.com/twitter-changes-from-display/#comment-12158746</link><description>&lt;p&gt;So reading the update (very helpful, thanks), I'd suggest that you still maintain the "from API".... because that can sorta mask the posting source. i.e. it's impossible to know (in a reader's mind, at least) whether this tweet came from a desktop app in real time or a future post service like tweetlater.&lt;/p&gt;&lt;p&gt;Is it possible to toggle a preference for this by individual user?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jake</dc:creator><pubDate>Sat, 04 Jul 2009 15:23:39 -0000</pubDate></item><item><title>Re: Twitter Changes &amp;#8220;From&amp;#8221; Display</title><link>http://www.tweetlaterblog.com/twitter-changes-from-display/#comment-12138732</link><description>&lt;p&gt;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.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alan</dc:creator><pubDate>Sat, 04 Jul 2009 02:25:59 -0000</pubDate></item><item><title>Re: Twitter Changes &amp;#8220;From&amp;#8221; Display</title><link>http://www.tweetlaterblog.com/twitter-changes-from-display/#comment-12134617</link><description>&lt;p&gt;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'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 "gee thanks" when I RT or an answer when I @reply them. It's all good if the follow up is handled, in my opinion.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Pat</dc:creator><pubDate>Fri, 03 Jul 2009 21:02:57 -0000</pubDate></item><item><title>Re: Twitter Changes &amp;#8220;From&amp;#8221; Display</title><link>http://www.tweetlaterblog.com/twitter-changes-from-display/#comment-12134288</link><description>&lt;p&gt;I would have preferred "from web" 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.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Murff</dc:creator><pubDate>Fri, 03 Jul 2009 20:45:16 -0000</pubDate></item><item><title>Re: Twitter Changes &amp;#8220;From&amp;#8221; Display</title><link>http://www.tweetlaterblog.com/twitter-changes-from-display/#comment-12089949</link><description>&lt;p&gt;Because as we all know, everyone stopped using blogs and reading webcomics when we discovered that people could automate their posts, right?&lt;/p&gt;&lt;p&gt;I like the "Tweetstream" 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. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Raye Keslensky - Last Res0rt</dc:creator><pubDate>Fri, 03 Jul 2009 16:49:19 -0000</pubDate></item><item><title>Re: Twitter Changes &amp;#8220;From&amp;#8221; Display</title><link>http://www.tweetlaterblog.com/twitter-changes-from-display/#comment-12089747</link><description>&lt;p&gt;Unfortunately, "web" is not an option. That is now reserved for tweets submitted from the Twitter web interface.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dewald Pretorius</dc:creator><pubDate>Fri, 03 Jul 2009 16:39:54 -0000</pubDate></item><item><title>Re: Twitter Changes &amp;#8220;From&amp;#8221; Display</title><link>http://www.tweetlaterblog.com/twitter-changes-from-display/#comment-12088621</link><description>&lt;p&gt;To sum it up, users want:&lt;/p&gt;&lt;p&gt;80% Web&lt;br&gt;15% API&lt;br&gt;5% Tweetlater&lt;/p&gt;&lt;p&gt;I'd say give what the users really want. This is one of the reasons that made Tweetlater popular in the first place.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">John</dc:creator><pubDate>Fri, 03 Jul 2009 16:04:09 -0000</pubDate></item><item><title>Re: Twitter Changes &amp;#8220;From&amp;#8221; Display</title><link>http://www.tweetlaterblog.com/twitter-changes-from-display/#comment-12087203</link><description>&lt;p&gt;I dont think it should say from tweet later, because then people wont value the content as much... &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kristen</dc:creator><pubDate>Fri, 03 Jul 2009 15:20:01 -0000</pubDate></item><item><title>Re: Twitter Changes &amp;#8220;From&amp;#8221; Display</title><link>http://www.tweetlaterblog.com/twitter-changes-from-display/#comment-12078558</link><description>&lt;p&gt;This is good the "from web" was sort of vague and now the "API" is more targeted.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Len Hill</dc:creator><pubDate>Fri, 03 Jul 2009 15:01:33 -0000</pubDate></item><item><title>Re: Twitter Changes &amp;#8220;From&amp;#8221; Display</title><link>http://www.tweetlaterblog.com/twitter-changes-from-display/#comment-12075913</link><description>&lt;p&gt;API is fine - better than TLater.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">BearTrax3</dc:creator><pubDate>Fri, 03 Jul 2009 13:11:30 -0000</pubDate></item><item><title>Re: Twitter Changes &amp;#8220;From&amp;#8221; Display</title><link>http://www.tweetlaterblog.com/twitter-changes-from-display/#comment-12075051</link><description>&lt;p&gt;So, basically, people want to say "from web" to deceive readers. I can accept "from API" to be ambiguous/not turn people off, but the active deception is disheartening. This kind of attitude does not speak well of (at least segments of) the TweetLater user community. I don't care if you use TweetLater but still provide value; just don't try to lie to me about it.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Michael Ekstrand</dc:creator><pubDate>Fri, 03 Jul 2009 12:26:10 -0000</pubDate></item><item><title>Re: Twitter Changes &amp;#8220;From&amp;#8221; Display</title><link>http://www.tweetlaterblog.com/twitter-changes-from-display/#comment-12074170</link><description>&lt;p&gt;Having it from API is much better than from TweetLater. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Carl Watts</dc:creator><pubDate>Fri, 03 Jul 2009 11:40:02 -0000</pubDate></item><item><title>Re: Twitter Changes &amp;#8220;From&amp;#8221; Display</title><link>http://www.tweetlaterblog.com/twitter-changes-from-display/#comment-12073095</link><description>&lt;p&gt;It's a bummer that Twitter decided to change the source label. I personally don't mind which is used, but API is safer, as heck anyone can use the API to create something that uses Twitter, forget to give source data. My followers know that I send out  auto posts with tips, websites and such so, as I said, it doesn't matter. They follow me for the work I do to provide them tips, not just the conversation I give while I'm actually online.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Submissive Guide</dc:creator><pubDate>Fri, 03 Jul 2009 10:32:33 -0000</pubDate></item><item><title>Re: Twitter Changes &amp;#8220;From&amp;#8221; Display</title><link>http://www.tweetlaterblog.com/twitter-changes-from-display/#comment-12072526</link><description>&lt;p&gt;I agree with your comment, Charles.&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ray Beckerman</dc:creator><pubDate>Fri, 03 Jul 2009 10:03:56 -0000</pubDate></item><item><title>Re: Twitter Changes &amp;#8220;From&amp;#8221; Display</title><link>http://www.tweetlaterblog.com/twitter-changes-from-display/#comment-12072508</link><description>&lt;p&gt;I would rather it did not specify "from Tweetlater". I would rather it just said "from API".&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ray Beckerman</dc:creator><pubDate>Fri, 03 Jul 2009 10:02:58 -0000</pubDate></item><item><title>Re: Twitter Changes &amp;#8220;From&amp;#8221; Display</title><link>http://www.tweetlaterblog.com/twitter-changes-from-display/#comment-12072277</link><description>&lt;p&gt;Pretty much a draw for me... perhaps slight preference for "from API" but that's very slight.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">threew</dc:creator><pubDate>Fri, 03 Jul 2009 09:51:20 -0000</pubDate></item><item><title>Re: Twitter Changes &amp;#8220;From&amp;#8221; Display</title><link>http://www.tweetlaterblog.com/twitter-changes-from-display/#comment-12071537</link><description>&lt;p&gt;I am amazed at the number of comments that suggests this is all the brain child of TWEETLATER. IT IS NOT, read the entire post, they in the corner on this one. TWITTER is changing the API so it is either identified as "from API" or from the name of the API accessing it. TWITTER is making the call on this one guys. Anyway if you are providing your followers with something valuable they won't care where the tweets are coming from!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ryan</dc:creator><pubDate>Fri, 03 Jul 2009 09:40:54 -0000</pubDate></item><item><title>Re: Twitter Changes &amp;#8220;From&amp;#8221; Display</title><link>http://www.tweetlaterblog.com/twitter-changes-from-display/#comment-12069449</link><description>&lt;p&gt;You want to leave this as from API. Though you might quickly think about yourself and your own advertising by saying it's from TweetLater, WE don't want it identified as coming from TweetLater... why do we want to tell people we have programmed tweets? It does us NO good and may do us quite a bit of harm.&lt;/p&gt;&lt;p&gt;So you are right to leave it as From API - the alternative may kill your service.&lt;/p&gt;&lt;p&gt;Charles Seymour Jr&lt;br&gt;&lt;a href="http://twitter.com/UltimateWAHDads" rel="nofollow noopener" target="_blank" title="http://twitter.com/UltimateWAHDads"&gt;http://twitter.com/Ultimate...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">CharlieSeymourJr</dc:creator><pubDate>Fri, 03 Jul 2009 09:28:02 -0000</pubDate></item><item><title>Re: Twitter Changes &amp;#8220;From&amp;#8221; Display</title><link>http://www.tweetlaterblog.com/twitter-changes-from-display/#comment-12069431</link><description>&lt;p&gt;For those of you that object to "From API" or potentially future "From Tweetlater" you can always set up a dedicated &lt;a href="http://Ping.fm" rel="nofollow noopener" target="_blank" title="Ping.fm"&gt;Ping.fm&lt;/a&gt; account in your TweetLater profile to forward your scheduled tweets which may be a bit more benign to the average follower.&lt;/p&gt;&lt;p&gt;If I were to ever be "called to task" for using Tweetlater or accused of using a spammer tool I would highlight the TweetCockpit management aspects and anti-spam filter/follow features.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">pfmonaco</dc:creator><pubDate>Fri, 03 Jul 2009 09:26:59 -0000</pubDate></item><item><title>Re: Twitter Changes &amp;#8220;From&amp;#8221; Display</title><link>http://www.tweetlaterblog.com/twitter-changes-from-display/#comment-12068859</link><description>&lt;p&gt;Much prefer that it remain as API&lt;/p&gt;&lt;p&gt;Somehow "from Tweetlater" creates an aura of impersonality - which is counter to the whole point of Social marketing - AARRGGH - Not unlike having the government make rules for how much air we can exhale!&lt;/p&gt;&lt;p&gt;Thanks for asking for out opinion.&lt;/p&gt;&lt;p&gt;Janetedin&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">janetedin</dc:creator><pubDate>Fri, 03 Jul 2009 08:49:42 -0000</pubDate></item><item><title>Re: Twitter Changes &amp;#8220;From&amp;#8221; Display</title><link>http://www.tweetlaterblog.com/twitter-changes-from-display/#comment-12068741</link><description>&lt;p&gt;I'm much happier with the reference to API than TweetLater, which just emphasizes the fact that I'm not present when the Tweet comes through. API is more innocuous, I think.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Kate Arnold</dc:creator><pubDate>Fri, 03 Jul 2009 08:42:29 -0000</pubDate></item></channel></rss>