<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Disqus - Latest Comments for cwalcott</title><link>http://disqus.com/people/cwalcott/</link><description></description><language>en</language><lastBuildDate>Thu, 11 Jun 2009 11:40:09 -0000</lastBuildDate><item><title>Re: New Features! Remember Me, Following, Retweets and More</title><link>http://tweetree.disqus.com/new_features_remember_me_following_retweets_and_more/#comment-10740466</link><description>Everything mentioned in this post is still in Tweetree.  Or did you mean some other work?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">cwalcott</dc:creator><pubDate>Thu, 11 Jun 2009 11:40:09 -0000</pubDate></item><item><title>Re: Read your blogs inside Tweetree</title><link>http://tweetree.disqus.com/read_your_blogs_inside_tweetree/#comment-10558310</link><description>No "account" has been created.  Putting any public Twitter username in  &lt;br&gt;the URL, like &lt;a href="http://tweetree.com/%3Cusername" rel="nofollow"&gt;http://tweetree.com/&amp;lt;username&lt;/a&gt;&amp;gt;, will display that user's  &lt;br&gt;tweets, formatted and with links back to &lt;a href="http://Twitter.com" rel="nofollow"&gt;Twitter.com&lt;/a&gt;.  This comes  &lt;br&gt;directly from the Twitter API and is not hosted or changed by us in  &lt;br&gt;any way.  Twitter's TOS, at &lt;a href="http://twitter.com/tos" rel="nofollow"&gt;http://twitter.com/tos&lt;/a&gt;, not only allows  &lt;br&gt;but encourages (their words) what we do, as long as there are links  &lt;br&gt;back to twitter (which we have).  Here is the exact text from their TOS:&lt;br&gt;&lt;br&gt;"The Twitter service makes it possible to post images and text hosted  &lt;br&gt;on Twitter to outside websites. This use is accepted (and even  &lt;br&gt;encouraged!). However, pages on other websites which display data  &lt;br&gt;hosted on &lt;a href="http://Twitter.com" rel="nofollow"&gt;Twitter.com&lt;/a&gt; must provide a link back to Twitter."&lt;br&gt;&lt;br&gt;With that said, if you'd like, as a courtesy, we can prevent tweets  &lt;br&gt;from being displayed specifically on your page.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">cwalcott</dc:creator><pubDate>Sat, 06 Jun 2009 02:19:09 -0000</pubDate></item><item><title>Re: Read your blogs inside Tweetree</title><link>http://tweetree.disqus.com/read_your_blogs_inside_tweetree/#comment-10557547</link><description>I'm not talking about opting out of the RSS integration ... I never asked you to create &lt;a href="http://tweetree.com/lunchinsuva" rel="nofollow"&gt;http://tweetree.com/lunchinsuva&lt;/a&gt;&lt;br&gt;&lt;br&gt;I want to opt out of that ... actually, wait ... you should have waited for me to opt in.&lt;br&gt;&lt;br&gt;You're not like Google Reader at all ... that's account and opt-in dependent. It's private, I can add and remove feeds, I can close my account. Any my stream is not exposed unless I publish it deliberately.&lt;br&gt;&lt;br&gt;So, how about letting me close this unauthorised 'account' with you guys.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">lunchinsuva</dc:creator><pubDate>Sat, 06 Jun 2009 01:02:49 -0000</pubDate></item><item><title>Re: Read your blogs inside Tweetree</title><link>http://tweetree.disqus.com/read_your_blogs_inside_tweetree/#comment-10554563</link><description>Hi,&lt;br&gt;&lt;br&gt;We don't strip ads out of the feeds. The only way we alter the content  &lt;br&gt;is disabling Javascript, which is only done to prevent malicious code  &lt;br&gt;from being run.&lt;br&gt;&lt;br&gt;We specifically use RSS so that website owners have control over what  &lt;br&gt;we show. What users see on Tweetree should be no different than what  &lt;br&gt;they would see in any other feedreader. Is it possible the ads depend  &lt;br&gt;on Javascript?  If there's a bug on our side, we'd be happy to help  &lt;br&gt;fix it.&lt;br&gt;&lt;br&gt;In terms of opting out, that's kind of like asking to opt out of  &lt;br&gt;Google Reader. The best way would be to simply remove or alter your  &lt;br&gt;RSS feed.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">cwalcott</dc:creator><pubDate>Fri, 05 Jun 2009 21:39:07 -0000</pubDate></item><item><title>Re: Performance Updates</title><link>http://tweetree.disqus.com/performance_updates/#comment-9328574</link><description>It worked the first time I tried, but then I went to my replies and was getting the original error.  Then went back to the main page, and it then didn't work either.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Azlen</dc:creator><pubDate>Thu, 14 May 2009 12:46:49 -0000</pubDate></item><item><title>Re: Performance Updates</title><link>http://tweetree.disqus.com/performance_updates/#comment-9312004</link><description>It was my work computer that I was having issues with, so I'll give it a try tomorrow.  Thanks</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Azlen</dc:creator><pubDate>Wed, 13 May 2009 23:43:29 -0000</pubDate></item><item><title>Re: Performance Updates</title><link>http://tweetree.disqus.com/performance_updates/#comment-9309433</link><description>Do you mind trying again? We just pushed out a fix.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">cwalcott</dc:creator><pubDate>Wed, 13 May 2009 22:07:11 -0000</pubDate></item><item><title>Re: Tweetree Now Checks for New Tweets</title><link>http://tweetree.disqus.com/tweetree_now_checks_for_new_tweets/#comment-9012559</link><description>Hi, &lt;br&gt;&lt;br&gt;The refresh notices were down for a while last night, but they should be back now.  Sorry about that!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">cwalcott</dc:creator><pubDate>Tue, 05 May 2009 10:05:19 -0000</pubDate></item><item><title>Re: New Features! Remember Me, Following, Retweets and More</title><link>http://tweetree.disqus.com/new_features_remember_me_following_retweets_and_more/#comment-5166857</link><description>Thanks! We're actually working on adding DM support right now :).</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">cwalcott</dc:creator><pubDate>Fri, 16 Jan 2009 12:50:50 -0000</pubDate></item><item><title>Re: How You Can Add Thumbnails to Tweetree</title><link>http://tweetree.disqus.com/how_you_can_add_thumbnails_to_tweetree/#comment-5118955</link><description>I don't think more options is always such a good thing.  In this case,  I would prefer using the FB method because it's already been done (circa 2006) and it's proven.  Options aren't bad inherently, however, when you have too many they cease to be helpful.&lt;br&gt;&lt;br&gt;There's a saying in Texas, "If it ain't broke, don't fix it."</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">tim</dc:creator><pubDate>Wed, 14 Jan 2009 15:45:27 -0000</pubDate></item><item><title>Re: How You Can Add Thumbnails to Tweetree</title><link>http://tweetree.disqus.com/how_you_can_add_thumbnails_to_tweetree/#comment-5106131</link><description>We should have more types of embedding coming very soon.  Are there any particular sites or services that you'd like to see?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">cwalcott</dc:creator><pubDate>Tue, 13 Jan 2009 23:16:52 -0000</pubDate></item><item><title>Re: How You Can Add Thumbnails to Tweetree</title><link>http://tweetree.disqus.com/how_you_can_add_thumbnails_to_tweetree/#comment-4789584</link><description>Thanks!  This looks promising too.  I'd love for Tweetree (and other sites) to be able to support multiple standards, such as oEmbed, this Facebook sharing standard, as well as the kind of mechanism Dave Winer has described.  This gives site owners more options, which is always a good thing.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">cwalcott</dc:creator><pubDate>Tue, 30 Dec 2008 19:22:31 -0000</pubDate></item><item><title>Re: Item-level permalinks, and FriendFeed account</title><link>http://tweetree.disqus.com/item_level_permalinks_and_friendfeed_account/#comment-4789525</link><description>Hmm, links that go to other sites should be opening in new windows.  If you don't mind, could you let me know what kind of links aren't opening in new windows, and which browser you're using?&lt;br&gt;&lt;br&gt;Thanks for using Tweetree!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">cwalcott</dc:creator><pubDate>Tue, 30 Dec 2008 19:17:31 -0000</pubDate></item><item><title>Re: How You Can Add Thumbnails to Tweetree</title><link>http://tweetree.disqus.com/how_you_can_add_thumbnails_to_tweetree/#comment-4705381</link><description>Neat! Thanks for pointing me to oEmbed, I'm going to check it out.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">cwalcott</dc:creator><pubDate>Mon, 29 Dec 2008 00:06:24 -0000</pubDate></item><item><title>Re: The space between Twitter and FriendFeed (Scripting News)</title><link>http://scripting.disqus.com/the_space_between_twitter_and_friendfeed_scripting_news/#comment-4575637</link><description>This post got me thinking that you could do a lot of what you're describing with a Twitter client.  You could follow any links that come through Twitter, and for things like images, videos and music embed the content directly in the client, similar to Friendfeed.  Other links could at least show the page's title and URL (after redirects).&lt;br&gt;&lt;br&gt;Another important bit to Friendfeed is the way it nests conversations.  I know with Twitter I always feel like I'm missing context when it comes to replies, and the only solution is to keep clicking those "in reply to" links.  So another important part would be to show "in reply to" messages right above replies.&lt;br&gt;&lt;br&gt;I've actually started working on this as a project called Tweetree, and an initial working release is up at &lt;a href="http://tweetree.com" rel="nofollow"&gt;tweetree.com&lt;/a&gt;.  I think there's a lot of potential to create a rich, graphical interface to the Twitter backend, using the FF model you've described here.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">cwalcott</dc:creator><pubDate>Mon, 22 Dec 2008 15:07:13 -0000</pubDate></item><item><title>Re: Boxee Invites</title><link>http://avc.disqus.com/boxee_invites/#comment-4007032</link><description>Great feedback&lt;br&gt;&lt;br&gt;We are going to talk about this with the company in 15 minutes!&lt;br&gt;&lt;br&gt;I love the web</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">fredwilson</dc:creator><pubDate>Tue, 25 Nov 2008 11:52:34 -0000</pubDate></item><item><title>Re: Boxee Invites</title><link>http://avc.disqus.com/boxee_invites/#comment-4006886</link><description>I understand the need to keep the user base controlled at the beginning, and a closed alpha/beta lets the company have more control over scaling.  I think creating a Boxee signup page for AVC readers was a great solution, since it lets Boxee know which of the users are the early adopters that come from your blog.&lt;br&gt;&lt;br&gt;I also get the sense that a big part of closed betas is the scarcity creating a marketing tool, which I find interesting.  I remember with Seesmic, there was a time when it was still nominally "closed", but Loic would give an account to anyone who asked for one, and would even post invite codes in blog comments and Twitter.  As a user it doesn't bother me, but I don't know if other people find it annoying.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">cwalcott</dc:creator><pubDate>Tue, 25 Nov 2008 11:44:25 -0000</pubDate></item><item><title>Re: Boxee Invites</title><link>http://avc.disqus.com/boxee_invites/#comment-4006489</link><description>Good question. I've been asking the same thing. The software is not yet where we want it and where we can get it soon. So the company wants to keep the user base small and sophiticated right now&lt;br&gt;&lt;br&gt;But I am starting to think that's not the right call&lt;br&gt;&lt;br&gt;Thoughts?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">fredwilson</dc:creator><pubDate>Tue, 25 Nov 2008 11:22:42 -0000</pubDate></item><item><title>Re: Boxee Invites</title><link>http://avc.disqus.com/boxee_invites/#comment-4004737</link><description>I'm loving Boxee so far, but I'm wondering why not make it an open beta if all the invite requests are being filled?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">cwalcott</dc:creator><pubDate>Tue, 25 Nov 2008 09:36:35 -0000</pubDate></item><item><title>Re: 5 Simple Ways To Keep Up With The Rails Community</title><link>http://dracoware.disqus.com/5_simple_ways_to_keep_up_with_the_rails_community_59/#comment-4004642</link><description>Thanks, glad you found it useful!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">cwalcott</dc:creator><pubDate>Tue, 25 Nov 2008 09:27:34 -0000</pubDate></item><item><title>Re: How Apple Can Support True Background Applications on the iPhone</title><link>http://dracoware.disqus.com/how_apple_can_support_true_background_applications_on_the_iphone_60/#comment-3330419</link><description>Yeah, I was thinking of a way to have only one application run in the background at once, since as you said users probably don't actually need too many simultaneously.  But for multiple background processes I like your method a lot.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">cwalcott</dc:creator><pubDate>Mon, 27 Oct 2008 16:19:11 -0000</pubDate></item><item><title>Re: Backups in Solaris using rsync</title><link>http://dracoware.disqus.com/backups_in_solaris_using_rsync/#comment-2893720</link><description>Sorry about that! Must have been a problem with our redesign.  The code should be visible now.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">cwalcott</dc:creator><pubDate>Mon, 06 Oct 2008 11:32:16 -0000</pubDate></item><item><title>Re: Ryan Twomey</title><link>http://ryantwomey.disqus.com/ryan_twomey_050/#comment-1088161</link><description>Really cool app, unfortunately it sounds like people are saying it's been removed from the App Store :-/.  Apparently it goes against the AT&amp;T TOS.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Costa</dc:creator><pubDate>Sun, 03 Aug 2008 20:38:00 -0000</pubDate></item><item><title>Re: Ryan Twomey</title><link>http://ryantwomey.disqus.com/ryan_twomey_332/#comment-486240</link><description>haha, thanks.  I'm using it too, and I'm impressed.  It's a nice eye-candy way of viewing feeds, though it's not really meant for hardcore RSS addicts.&lt;br&gt;&lt;br&gt;What I'm doing, actually, is pulling together lots of feeds that aren't in my regular newsreader and using snackr to display them.  That way, whenever I glance over at it, I'm guaranteed to see something I haven't already read, and can pick out things I may not have seen otherwise.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">rtwomey</dc:creator><pubDate>Sun, 18 May 2008 10:51:29 -0000</pubDate></item><item><title>Re: Ryan Twomey - A busy day...</title><link>http://ryantwomey.disqus.com/ryan_twomey_a_busy_day/#comment-486217</link><description>Thanks.  Luckily, the rain has been holding off.  Hopefully it stays that way, otherwise it will be a miserable day.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">rtwomey</dc:creator><pubDate>Sun, 18 May 2008 10:41:38 -0000</pubDate></item></channel></rss>