<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Disqus - Friends of srod710</title><link>http://disqus.com/people/srod710/</link><description></description><language>en</language><lastBuildDate>Thu, 17 Sep 2009 21:27:00 -0000</lastBuildDate><item><title>Re: Google gets a patent on reading lists (Scripting News)</title><link>http://www.scripting.com/stories/2009/09/17/googleGetsAPatentOnReading.html#comment-16852091</link><description>Google Reader's bundles can, in fact, be subscribed to, by other Google Reader users and potentially by third-party readers that support OPML subscriptions. Two flaws: Their OPML was not validating when last you (Dave) checked, this is why I say the feeds may "potentially" be subscribed to -- if it doesn't validate it's not OPML so who knows where it will work. Second flaw, Google Reader's reader did not last I checked support the ability to subscribe to an arbitrary third-party OPML URL.&lt;br&gt;&lt;br&gt;Not sure any of this has bearing on the patent, though, given the extensive prior art outside of Google.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ryantate</dc:creator><pubDate>Thu, 17 Sep 2009 21:27:00 -0000</pubDate></item><item><title>Re: Chrome bookmark synch (Scripting News)</title><link>http://www.scripting.com/stories/2009/08/03/chromeBookmarkSynch.html#comment-13885748</link><description>Chrome for Mac isn't out yet, you're referring to the daily builds of Chromium, the open source foundation of Chrome. &lt;a href="http://build.chromium.org/buildbot/snapshots/chromium-rel-mac/" rel="nofollow"&gt;http://build.chromium.org/buildbot/snapshots/ch...&lt;/a&gt;&lt;br&gt;&lt;br&gt;PS Would love to use it, but am addicted to Firefox's Command-Shift-T -- "re-open that tab I just accidentally nuked." Maybe Chrome will have this when it's done but I'm not holding my breath. Of course, Undo should handle this but programmers seem to hate implementing Undo.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ryantate</dc:creator><pubDate>Tue, 04 Aug 2009 12:41:44 -0000</pubDate></item><item><title>Re: Following the people of the NYT and Twitter (Scripting News)</title><link>http://www.scripting.com/stories/2009/05/16/followingThePeopleOfTheNyt.html#comment-9480283</link><description>Thanks! Will make for a great feed</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ryantate</dc:creator><pubDate>Sun, 17 May 2009 17:54:08 -0000</pubDate></item><item><title>Re: Following the people of the NYT and Twitter (Scripting News)</title><link>http://www.scripting.com/stories/2009/05/16/followingThePeopleOfTheNyt.html#comment-9479981</link><description>I don't get it -- cluelessnewbie feed doesn't have any of the content of the streams. I was hoping for an RSS feed that contained the tweets (or, failing that, maybe an OPML pointing to the original tweet feeds)&lt;br&gt;&lt;br&gt;&lt;a href="http://twitter.com/statuses/user_timeline/37586939.rss" rel="nofollow"&gt;http://twitter.com/statuses/user_timeline/37586...&lt;/a&gt;&lt;br&gt;&lt;br&gt;It seems to me if the content of the page (eg &lt;a href="http://nyt.100twt.com/" rel="nofollow"&gt;http://nyt.100twt.com/&lt;/a&gt;) is the actual tweets, the RSS feed should be the same thing. If the content of the page were just pointers, it would make sense for the feed to be also just pointers.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ryantate</dc:creator><pubDate>Sun, 17 May 2009 17:37:48 -0000</pubDate></item><item><title>Re: Retweet is stupid (Scripting News)</title><link>http://www.scripting.com/stories/2009/04/26/retweetIsStupid.html#comment-8714113</link><description>Yes that would rock and solve the problem! As long as there is some sort of formatting explaining who favorited it. Favorites should look a touch different in the feed. (As I mentioned above before seeing your post &lt;a href="http://www.scripting.com/stories/2009/04/26/retweetIsStupid.html?disqus_reply=8714113#comment-8714015" rel="nofollow"&gt;http://www.scripting.com/stories/2009/04/26/ret...&lt;/a&gt;)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ryantate</dc:creator><pubDate>Sun, 26 Apr 2009 19:46:35 -0000</pubDate></item><item><title>Re: Retweet is stupid (Scripting News)</title><link>http://www.scripting.com/stories/2009/04/26/retweetIsStupid.html#comment-8714015</link><description>You nailed it -- favorites is key -- Twitter needs to make a tiny tweak to favorites and it would have a huge impact: just put Favorites in with the whole stream -- when you follow someone you get both their tweets and their favorites (with some kind of formatting for the favorite so it's clear who you got it via and why). Same for RSS -- default feed should have both faves and items.&lt;br&gt;&lt;br&gt;You'd want to be able to turn this off person by person or all at once, of course.&lt;br&gt;&lt;br&gt;(Update oh I see Jim Roepcke also said this below)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ryantate</dc:creator><pubDate>Sun, 26 Apr 2009 19:41:02 -0000</pubDate></item><item><title>Re: The Next Killer App is to Twitter as 1-2-3 was to Visicalc (Scripting News)</title><link>http://www.scripting.com/stories/2009/04/24/theNextKillerAppIsToTwitte.html#comment-8668768</link><description>Come on, this gets said  _every_ time there's a new Web publishing meme. The new thing is always called a trivial stupid variation on the old thing.&lt;br&gt;&lt;br&gt;"Web CMS just duplicates what you can already do with ssh/emacs and ftp. Except worse."&lt;br&gt;&lt;br&gt;"A blogging system is just a CMS with a particular template, what's the big deal?"&lt;br&gt;&lt;br&gt;And now "Twitter is just a type of blog."&lt;br&gt;&lt;br&gt;Slapping a Twitter template on WordPress is different in all kinds of ways from actual Twitter. You're glossing over all kinds of little differences -- presumably as "trivial" -- that are the crucial reason Twitter is where it is. &lt;br&gt;&lt;br&gt;It doesn't ask you to type a headline in your post. It doesn't allow you to edit a post, ever. These are just the tip of the iceberg. The little things make all the difference. Trivial isn't trivial.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ryantate</dc:creator><pubDate>Fri, 24 Apr 2009 18:20:38 -0000</pubDate></item><item><title>Re: Solving the TinyUrl centralization problem (Scripting News)</title><link>http://www.scripting.com/stories/2009/03/07/solvingTheTinyurlCentraliz.html#comment-7124712</link><description>PS According to Disqus you posted your reply _before_ the comment you're replying to. Odd.</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><item><title>Re: Solving the TinyUrl centralization problem (Scripting News)</title><link>http://www.scripting.com/stories/2009/03/07/solvingTheTinyurlCentraliz.html#comment-7124693</link><description>Interesting point! I hadn't thought if that way.</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>http://www.scripting.com/stories/2009/03/07/solvingTheTinyurlCentraliz.html#comment-6999874</link><description>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;br&gt;&lt;br&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.</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: Archiving your tweets in XML (Scripting News)</title><link>http://www.scripting.com/stories/2009/03/04/archivingYourTweetsInXml.html#comment-6887231</link><description>Oh I see, click on the "docs" link above:&lt;br&gt;&lt;br&gt;&lt;a href="http://editor.opml.org/twitterCalendarTool.html" rel="nofollow"&gt;http://editor.opml.org/twitterCalendarTool.html&lt;/a&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: Julie and Julia (Scripting News)</title><link>http://www.scripting.com/stories/2009/01/06/julieAndJulia.html#comment-4985416</link><description>Are you talking strictly about this controversial &lt;a href="http://nytimes.com" rel="nofollow"&gt;nytimes.com&lt;/a&gt; op-ed?&lt;br&gt;&lt;br&gt;&lt;a href="http://www.nytimes.com/2005/07/22/opinion/22powell_cm.html" rel="nofollow"&gt;http://www.nytimes.com/2005/07/22/opinion/22pow...&lt;/a&gt;&lt;br&gt;&lt;br&gt;Because that's a lot to extrapolate from one foofaraw!</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: CTO of the Year (Scripting News)</title><link>http://www.scripting.com/stories/2008/12/20/ctoOfTheYear.html#comment-4551771</link><description>I had not heard of SQS. It looks interesting, but messages can only be retained for a few days:&lt;br&gt;&lt;br&gt;&lt;a href="http://aws.amazon.com/sqs/" rel="nofollow"&gt;http://aws.amazon.com/sqs/&lt;/a&gt;&lt;br&gt;&lt;br&gt;So the model might be: Send message to every follower's "incoming" queue for every tweet.&lt;br&gt;&lt;br&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;br&gt;&lt;br&gt;OR:&lt;br&gt;&lt;br&gt;Send tweets to your own "outgoing queue." Followers must poll within four days or they miss the tweet.&lt;br&gt;&lt;br&gt;OR, SIMPLEST THING THAT COULD POSSIBLY WORK:&lt;br&gt;&lt;br&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;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&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;br&gt;&lt;br&gt;PS &lt;a href="http://Twitter.com" rel="nofollow"&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;br&gt;&lt;br&gt;A Twitter stream is just a tightly constrained RSS feed.&lt;br&gt;&lt;br&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?</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: What is a netbook? (Scripting News)</title><link>http://www.scripting.com/stories/2008/12/17/whatIsANetbook.html#comment-4473842</link><description>Thanks!</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: The space between Twitter and FriendFeed (Scripting News)</title><link>http://www.scripting.com/stories/2008/12/07/theSpaceBetweenTwitterAndF.html#comment-4242296</link><description>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.</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: Full text in RSS? (Scripting News)</title><link>http://www.scripting.com/stories/2008/10/24/fullTextInRss.html#comment-3291881</link><description>PS and the reader isn't clever enough. And doesn't care! Well, mine at least. Technical blogs, maybe not.</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: Full text in RSS? (Scripting News)</title><link>http://www.scripting.com/stories/2008/10/24/fullTextInRss.html#comment-3291879</link><description>Nah, I'm a fascist! ;-&amp;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>http://www.scripting.com/stories/2008/10/24/fullTextInRss.html#comment-3287476</link><description>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;br&gt;&lt;br&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.</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></channel></rss>