<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Friends of srod710</title><link>http://disqus.com/by/srod710/</link><description></description><atom:link href="http://disqus.com/srod710/friends.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Wed, 11 Mar 2009 23:00:46 -0000</lastBuildDate><item><title>Re: Could S3 be an end-user product? (Scripting News)</title><link>(u'http://www.scripting.com/stories/2007/12/20/couldS3BeAnEnduserProduct.html',%2042761L)#comment-42761</link><description>&lt;p&gt;I second JungleDisk. I use it to back up the more critical files on my home PC. I like that it encrypts the data before storing it on Amazon's servers.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ryantate</dc:creator><pubDate>Thu, 20 Dec 2007 15:11:06 -0000</pubDate></item><item><title>Re: Could S3 be an end-user product? (Scripting News)</title><link>(u'http://www.scripting.com/stories/2007/12/20/couldS3BeAnEnduserProduct.html',%2042762L)#comment-42762</link><description>&lt;p&gt;-&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ryantate</dc:creator><pubDate>Thu, 20 Dec 2007 15:11:24 -0000</pubDate></item><item><title>Re: The UGC limb, day 2 (Scripting News)</title><link>(u'http://www.scripting.com/stories/2008/01/22/theUgcLimbDay2.html',%2095291L)#comment-95291</link><description>&lt;p&gt;Yes and yes! Bing!&lt;/p&gt;&lt;p&gt;But what about ...&lt;/p&gt;&lt;p&gt;3. The next next step will be API clones of S3, EC2 and SimpleDB (from Google, MSFT, Yahoo, etc etc) so you can deploy your packaged app not just to Amazon but anywhere, and probably in multiple places at once, for sake of redundancy.&lt;/p&gt;&lt;p&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ryantate</dc:creator><pubDate>Wed, 23 Jan 2008 01:31:01 -0000</pubDate></item><item><title>Re: Interview with Scoble (Scripting News)</title><link>(u'http://www.scripting.com/stories/2008/03/11/interviewWithScoble.html',%20220071L)#comment-220071</link><description>&lt;p&gt;This was a great interview and you kept in on track well Dave. Well timed, good questions.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ryantate</dc:creator><pubDate>Tue, 11 Mar 2008 17:59:05 -0000</pubDate></item><item><title>Re: Embargoes: Thanks but no thanks</title><link>(u'http://www.mathewingram.com/work/2008/08/21/embargoes-thanks-but-no-thanks/',%201737180L)#comment-1737180</link><description>&lt;p&gt;The practice is, at heart, a gimmick, to add hype to "news" the press might otherwise ignore or underplay. Your IPO comparison is apt.&lt;/p&gt;&lt;p&gt;I have some inside information on why PR people do this, but I won't tell you unless you promise to keep it under your hat for a week.&lt;/p&gt;&lt;p&gt;(*Cough*)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ryantate</dc:creator><pubDate>Fri, 22 Aug 2008 18:25:51 -0000</pubDate></item><item><title>Re: Full text in RSS? (Scripting News)</title><link>(u'http://www.scripting.com/stories/2008/10/24/fullTextInRss.html',%203286933L)#comment-3286933</link><description>&lt;p&gt;Feed Readers can just truncate full text feeds if skimming is desired (which is orthogonal to river of news btw). That's how Google Reader works -- you can look at headlines and first few words of description in river of news headline mode. Then click an item to see the full included text. (Or you can switch to "extended" view, still river of news, and see full text of everything by default)&lt;/p&gt;&lt;p&gt; Seems best to encourage content publishers to do full feeds and leave the tools to trim it for the users.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ryantate</dc:creator><pubDate>Fri, 24 Oct 2008 19:48:44 -0000</pubDate></item><item><title>Re: Full text in RSS? (Scripting News)</title><link>(u'http://www.scripting.com/stories/2008/10/24/fullTextInRss.html',%203287476L)#comment-3287476</link><description>&lt;p&gt;99% of people don't care if they're reading an excerpt or a "hand-crafted" summation, imho. Granted they're not the same but you're just trying to decide whether to click through. And offering multiple feeds is just too confusing for an everyday non geek.&lt;/p&gt;&lt;p&gt; And if you really care, as a publisher, you could always do an atom feed, which can have a summary _and_ fulltext. But it's much better to have one feed. One less meaningless decision for people to make -- just click the autodiscovered RSS feed tag and you're off.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ryantate</dc:creator><pubDate>Fri, 24 Oct 2008 20:41:11 -0000</pubDate></item><item><title>Re: Full text in RSS? (Scripting News)</title><link>(u'http://www.scripting.com/stories/2008/10/24/fullTextInRss.html',%203291879L)#comment-3291879</link><description>&lt;p&gt;Nah, I'm a fascist! ;-&amp;gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ryantate</dc:creator><pubDate>Sat, 25 Oct 2008 02:45:06 -0000</pubDate></item><item><title>Re: Full text in RSS? (Scripting News)</title><link>(u'http://www.scripting.com/stories/2008/10/24/fullTextInRss.html',%203291881L)#comment-3291881</link><description>&lt;p&gt;PS and the reader isn't clever enough. And doesn't care! Well, mine at least. Technical blogs, maybe not.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ryantate</dc:creator><pubDate>Sat, 25 Oct 2008 02:46:05 -0000</pubDate></item><item><title>Re: I heart 30 Rock (Scripting News)</title><link>(u'http://www.scripting.com/stories/2008/11/16/iHeart30Rock.html',%203851857L)#comment-3851857</link><description>&lt;p&gt;Here's a downloadable link for the Fresh Air interview:&lt;/p&gt;&lt;p&gt;&lt;a href="http://podcastdownload.npr.org/anon.npr-podcasts/podcast/13/96553006/npr_96553006.mp3" rel="nofollow noopener" target="_blank" title="http://podcastdownload.npr.org/anon.npr-podcasts/podcast/13/96553006/npr_96553006.mp3"&gt;http://podcastdownload.npr....&lt;/a&gt;&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ryantate</dc:creator><pubDate>Sun, 16 Nov 2008 22:21:03 -0000</pubDate></item><item><title>Re: The space between Twitter and FriendFeed (Scripting News)</title><link>(u'http://www.scripting.com/stories/2008/12/07/theSpaceBetweenTwitterAndF.html',%204242296L)#comment-4242296</link><description>&lt;p&gt;My thought too. Most people use Tumblr exactly as DW is discussing. But it's not enforced -- unlike Twitter, you can use as many chars as you want. If Tumblr added "tiny post" or somesuch as one of its post types (along with pic, video, txt, etc), with a char count monitor and limit, and offered a truncated version of the feed (enforced to no longer than X chars), it would be a lot like DW describes.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ryantate</dc:creator><pubDate>Sun, 07 Dec 2008 22:57:33 -0000</pubDate></item><item><title>Re: What is a netbook? (Scripting News)</title><link>(u'http://www.scripting.com/stories/2008/12/17/whatIsANetbook.html',%204473495L)#comment-4473495</link><description>&lt;p&gt;Regarding your point on vendor lock-in, is there any, with OS X or XP or anything else? -- aren't all the key apps you use on one of these things Web apps? So as long as there's Firefox or whatever browser you like, you're good to go.&lt;/p&gt;&lt;p&gt;Or if not what are they key desktop apps you tend to use. I ask because I don't own a netbook and am curious about why the OS is important if I do buy one.&lt;/p&gt;&lt;p&gt; (On  my laptop I use the Web for my mail and rss apps, and would gladly switch for music (if I didnt have so many DRMed itunes tracks) and image editing (but I need blur) and video editing (not yet a Web thing, but who does that on a netbook). And Web post writing (ecto).)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ryantate</dc:creator><pubDate>Wed, 17 Dec 2008 22:04:13 -0000</pubDate></item><item><title>Re: What is a netbook? (Scripting News)</title><link>(u'http://www.scripting.com/stories/2008/12/17/whatIsANetbook.html',%204473842L)#comment-4473842</link><description>&lt;p&gt;Thanks!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ryantate</dc:creator><pubDate>Wed, 17 Dec 2008 22:27:50 -0000</pubDate></item><item><title>Re: CTO of the Year (Scripting News)</title><link>(u'http://www.scripting.com/stories/2008/12/20/ctoOfTheYear.html',%204551771L)#comment-4551771</link><description>&lt;p&gt;I had not heard of SQS. It looks interesting, but messages can only be retained for a few days:&lt;/p&gt;&lt;p&gt;&lt;a href="http://aws.amazon.com/sqs/" rel="nofollow noopener" target="_blank" title="http://aws.amazon.com/sqs/"&gt;http://aws.amazon.com/sqs/&lt;/a&gt;&lt;/p&gt;&lt;p&gt;So the model might be: Send message to every follower's "incoming" queue for every tweet.&lt;/p&gt;&lt;p&gt;On the other side: Poll your own "incoming" queue for messages, write to a DB or RSS file and/or send to a cell phone and/or ping IM depending on who it's from.&lt;/p&gt;&lt;p&gt;OR:&lt;/p&gt;&lt;p&gt;Send tweets to your own "outgoing queue." Followers must poll within four days or they miss the tweet.&lt;/p&gt;&lt;p&gt;OR, SIMPLEST THING THAT COULD POSSIBLY WORK:&lt;/p&gt;&lt;p&gt;Your tweets are just an RSS feed with a special flag (via namespace extension) indicating all items are Twitter compatible, ie 140 chars or less. You store them on S3 or any other Web accessible URL. Followers poll at will (respecting any limits within the RSS file as usual).&lt;/p&gt;&lt;p&gt;(Their own client software, probably open source, running on their cloud or desktop, handles the tweets -- writing to an HTML interface, or SMS or IM etc.)&lt;/p&gt;&lt;p&gt;PS &lt;a href="http://Twitter.com" rel="nofollow noopener" target="_blank" title="Twitter.com"&gt;Twitter.com&lt;/a&gt; is just a fancy RSS reader, with optional hookups to your cell phone, the ability to ferret out and display "replies," the ability to authenticate into restricted feeds and an IM bridge.&lt;/p&gt;&lt;p&gt;A Twitter stream is just a tightly constrained RSS feed.&lt;/p&gt;&lt;p&gt;PPS Caveat: Restricting readership is tricky. HTTP authentication would work but you'd need some kind of universal login database and common login technique. Would this matter to Twitter power users?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ryantate</dc:creator><pubDate>Sat, 20 Dec 2008 23:26:23 -0000</pubDate></item><item><title>Re: louisgray.com: The Christmas Story, As Told Through Twitter</title><link>(u'http://blog.louisgray.com/2008/12/christmas-story-as-told-through-twitter.html',%204625203L)#comment-4625203</link><description>&lt;p&gt;Wonderful.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ryantate</dc:creator><pubDate>Thu, 25 Dec 2008 06:53:01 -0000</pubDate></item><item><title>Re: Julie and Julia (Scripting News)</title><link>(u'http://www.scripting.com/stories/2009/01/06/julieAndJulia.html',%204985414L)#comment-4985414</link><description>&lt;p&gt;-moved-&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ryantate</dc:creator><pubDate>Thu, 08 Jan 2009 06:31:16 -0000</pubDate></item><item><title>Re: Julie and Julia (Scripting News)</title><link>(u'http://www.scripting.com/stories/2009/01/06/julieAndJulia.html',%204985416L)#comment-4985416</link><description>&lt;p&gt;Are you talking strictly about this controversial &lt;a href="http://nytimes.com" rel="nofollow noopener" target="_blank" title="nytimes.com"&gt;nytimes.com&lt;/a&gt; op-ed?&lt;/p&gt;&lt;p&gt;&lt;a href="http://www.nytimes.com/2005/07/22/opinion/22powell_cm.html" rel="nofollow noopener" target="_blank" title="http://www.nytimes.com/2005/07/22/opinion/22powell_cm.html"&gt;http://www.nytimes.com/2005...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Because that's a lot to extrapolate from one foofaraw!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ryantate</dc:creator><pubDate>Thu, 08 Jan 2009 06:33:17 -0000</pubDate></item><item><title>Re: How to avoid getting run down by drivers walking around town (Scripting News)</title><link>(u'http://www.scripting.com/stories/2009/02/15/howToAvoidGettingRunDownBy.html',%206319300L)#comment-6319300</link><description>&lt;p&gt;Perhaps this goes without saying, but with the wrong driver in the wrong part of Berkeley this could get a person in a dangerous confrontation. I'm very much in favor of taming drivers, but also very personally aware of the risks.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ryantate</dc:creator><pubDate>Mon, 16 Feb 2009 21:12:11 -0000</pubDate></item><item><title>Re: Archiving your tweets in XML (Scripting News)</title><link>(u'http://www.scripting.com/stories/2009/03/04/archivingYourTweetsInXml.html',%206887189L)#comment-6887189</link><description>&lt;p&gt;My question: Where do I get this app? :-&amp;gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ryantate</dc:creator><pubDate>Wed, 04 Mar 2009 21:07:20 -0000</pubDate></item><item><title>Re: Archiving your tweets in XML (Scripting News)</title><link>(u'http://www.scripting.com/stories/2009/03/04/archivingYourTweetsInXml.html',%206887231L)#comment-6887231</link><description>&lt;p&gt;Oh I see, click on the "docs" link above:&lt;/p&gt;&lt;p&gt;&lt;a href="http://editor.opml.org/twitterCalendarTool.html" rel="nofollow noopener" target="_blank" title="http://editor.opml.org/twitterCalendarTool.html"&gt;http://editor.opml.org/twit...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ryantate</dc:creator><pubDate>Wed, 04 Mar 2009 21:09:31 -0000</pubDate></item><item><title>Re: Maybe Schieffer should Face the nation? (Scripting News)</title><link>(u'http://www.scripting.com/stories/2009/03/04/maybeSchiefferShouldFaceTh.html',%206974188L)#comment-6974188</link><description>&lt;p&gt;MP3 for Terry Gross' Simon Johnson interview:&lt;/p&gt;&lt;p&gt;&lt;a href="http://public.npr.org/anon.npr-mp3/npr/fa/2009/03/20090303_fa_01.mp3?sc=16&amp;amp;orgId=" rel="nofollow noopener" target="_blank" title="http://public.npr.org/anon.npr-mp3/npr/fa/2009/03/20090303_fa_01.mp3?sc=16&amp;amp;orgId="&gt;http://public.npr.org/anon....&lt;/a&gt;|1|&amp;amp;topicId=1017&amp;amp;parentTopicId=1006&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ryantate</dc:creator><pubDate>Sat, 07 Mar 2009 02:59:35 -0000</pubDate></item><item><title>Re: Solving the TinyUrl centralization problem (Scripting News)</title><link>(u'http://www.scripting.com/stories/2009/03/07/solvingTheTinyurlCentraliz.html',%206999795L)#comment-6999795</link><description>&lt;p&gt;Reading this just once, my brain shortened what you wrote to "long URLs shouldn't really exist."&lt;/p&gt;&lt;p&gt;If the Web app itself contains the shortener, and the server it runs on can resolve the short URLs, there's not really a need for the long version of the URL at all, is there?&lt;/p&gt;&lt;p&gt;Anyway, maybe that's not a fair summary, but my conclusion is that since Web app authors created the need for URL shorteners in the first place it might be expecting too much to ask those same authors to obviate that same need.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ryantate</dc:creator><pubDate>Sun, 08 Mar 2009 17:52:51 -0000</pubDate></item><item><title>Re: Solving the TinyUrl centralization problem (Scripting News)</title><link>(u'http://www.scripting.com/stories/2009/03/07/solvingTheTinyurlCentraliz.html',%206999874L)#comment-6999874</link><description>&lt;p&gt;This is really an implementation problem -- Web app authors don't have the time/energy/knowledge to wire up apache in such a way as to shorten their app urls though they could theoretically do so without too much pain.&lt;/p&gt;&lt;p&gt;Maybe the solution is an Apache plugin/filter that would look for incoming requests for urls over a certain length Then it would generate a short url (using its own database/hashing code) and redirect the user to that url, which would become the canonical url for that link, Rinse/repeat for IIS. Dead simple for the app developer once implemented in the server.&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ryantate</dc:creator><pubDate>Sun, 08 Mar 2009 18:01:11 -0000</pubDate></item><item><title>Re: Solving the TinyUrl centralization problem (Scripting News)</title><link>(u'http://www.scripting.com/stories/2009/03/07/solvingTheTinyurlCentraliz.html',%207124693L)#comment-7124693</link><description>&lt;p&gt;Interesting point! I hadn't thought if that way.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ryantate</dc:creator><pubDate>Wed, 11 Mar 2009 23:00:06 -0000</pubDate></item><item><title>Re: Solving the TinyUrl centralization problem (Scripting News)</title><link>(u'http://www.scripting.com/stories/2009/03/07/solvingTheTinyurlCentraliz.html',%207124712L)#comment-7124712</link><description>&lt;p&gt;PS According to Disqus you posted your reply _before_ the comment you're replying to. Odd.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ryantate</dc:creator><pubDate>Wed, 11 Mar 2009 23:00:46 -0000</pubDate></item></channel></rss>