<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Disqus - Latest Comments for crabasa</title><link xmlns="http://www.w3.org/2005/Atom" rel="http://api.friendfeed.com/2008/03#sup" href="http://disqus.com/sup/all.sup#usercomments-7efd254c" type="application/json"/><link>http://disqus.com/people/crabasa/</link><description></description><language>en</language><lastBuildDate>Wed, 19 Nov 2008 18:52:49 -0000</lastBuildDate><item><title>Re: Boxee</title><link>http://www.avc.com/a_vc/2008/11/boxee.html#comment-3898684</link><description>Thanks, Fred!&lt;br&gt;&lt;br&gt;Unlike people who are trying these tools out for fun, I am a graduate student who has chosen (for cost and time-killing reasons) not to own a TV or subscribe to cable.  I just have an Internet connection and a handful of home computers, so I'm really excited about Boxee.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">crabasa</dc:creator><pubDate>Wed, 19 Nov 2008 18:52:49 -0000</pubDate></item><item><title>Re: Boxee</title><link>http://www.avc.com/a_vc/2008/11/boxee.html#comment-3897246</link><description>I left a comment on FF, but should have commented here (as I pray for integration). I would love to give Boxee a spin.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">crabasa</dc:creator><pubDate>Wed, 19 Nov 2008 17:36:52 -0000</pubDate></item><item><title>Re: Why The iTouch Is Inevitable</title><link>http://www.avc.com/a_vc/2008/11/why-the-itouch.html#comment-3645003</link><description>I think that you're probably overstating the cost savings of removing the iPod components.  The main cost of the device are the components you're likely to keep (touch screen, battery, Wi-fi, etc).&lt;br&gt;&lt;br&gt;More to the point, I think the benefits of creating niche extensions of the iPhone/iTouch are outweighed by the costs.  Developers don't want different targets to code against. Apple wants to evolve the concept of mobile computing, not slide backwards into creating super remotes.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">crabasa</dc:creator><pubDate>Sun, 09 Nov 2008 16:57:07 -0000</pubDate></item><item><title>Re: cubanlinks 
  
  
    - Time to Buy?</title><link>http://cubanlinks.org/articles/2008/10/7/time-to-buy#comment-2928517</link><description>Wow, that's such a great idea.  Anyone with a rock-solid job (government employees, etc) should be doing this.  Pre-tax money buying assets at rock-bottom prices.  Ka-ching!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">crabasa</dc:creator><pubDate>Wed, 08 Oct 2008 01:54:25 -0000</pubDate></item><item><title>Re: cubanlinks 
  
  
    - Styling Your FriendFeed Badge</title><link>http://cubanlinks.org/articles/2008/5/5/styling-your-friendfeed-badge#comment-765990</link><description>I did a "view source" on Scoble's page.  Also, you can always use Firefox to view the DOM that gets created by Javascript after the page has fully loaded.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">crabasa</dc:creator><pubDate>Fri, 27 Jun 2008 22:44:47 -0000</pubDate></item><item><title>Re: Photos From Austin | iSeanReiser</title><link>http://seanreiser.com/node/1557#comment-501141</link><description>I can't begin to guess what you might be looking for, so here are some highlights:&lt;br&gt;&lt;br&gt;Amazing burgers: Counter Cafe (N Lamar Blvd, Tues-Sun)&lt;br&gt;Relax, drinks and Wii: Tiniest Bar in Texas (W 5th St)&lt;br&gt;Sushi: Uchi (S Lamar Blvd)&lt;br&gt;&lt;br&gt;None of this includes simply walking up and down S. Congress.  Enjoy!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">crabasa</dc:creator><pubDate>Wed, 21 May 2008 04:43:54 -0000</pubDate></item><item><title>Re: Photos From Austin | iSeanReiser</title><link>http://seanreiser.com/node/1557#comment-501071</link><description>Hope you enjoyed Austin. I've been living there for the past year and, having spent time on both coasts, really feel like it has a lot to offer.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">crabasa</dc:creator><pubDate>Wed, 21 May 2008 04:22:32 -0000</pubDate></item><item><title>Re: cubanlinks 
  
  
    - Pretty Embarassing...</title><link>http://cubanlinks.org/articles/2008/5/13/pretty-embarassing#comment-461791</link><description>You know what, this might have been a blessing in disguise.  I am now implementing a temporary switch to Feedburner, so we'll see if that solves the problem.  While I'm fixing bugs, I'll get to see what the fuss with Feedburner is all about.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">crabasa</dc:creator><pubDate>Wed, 14 May 2008 13:41:18 -0000</pubDate></item><item><title>Re: cubanlinks 
  
  
    - Pretty Embarassing...</title><link>http://cubanlinks.org/articles/2008/5/13/pretty-embarassing#comment-461654</link><description>Wow, this is a much harder nut to crack than I thought.  Thanks for letting me know!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">crabasa</dc:creator><pubDate>Wed, 14 May 2008 13:15:24 -0000</pubDate></item><item><title>Re: A Venezuelan Moment: The Gillmor Gang considers nationalizing Twitter</title><link>http://blog.echovar.com/?p=385#comment-446206</link><description>I agree with Blaine.  I'm constantly surprised at how over-stated the functionality of Twitter is.  When you boil it down to its essentials, I think it's clear that a distributed replica is quite viable.&lt;br&gt;&lt;br&gt;I've suggested a few times that tracking could be implemented much the way SixApart implemented TrackBack back in the early days of blogging.  All micro-blogging tools/sites would implement a commmon API for receiving "follow" pings from their readership.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">crabasa</dc:creator><pubDate>Sun, 11 May 2008 17:46:14 -0000</pubDate></item><item><title>Re: cubanlinks 
  
  
    - I've Added Disqus</title><link>http://cubanlinks.org/articles/2008/5/10/i-ve-added-disqus#comment-443793</link><description>Testing!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">crabasa</dc:creator><pubDate>Sat, 10 May 2008 20:36:11 -0000</pubDate></item><item><title>Re: If the Dems didn't have Superdelegates... (Scripting News)</title><link>http://www.scripting.com/stories/2008/05/05/ifTheDemsDidntHaveSuperdel.html#comment-418345</link><description>I think your point about Clinton needing 70% of the remaining delegates illustrated why it IS over.  It's the same statistical principle that is used when calling elections, despite only a fraction of the votes having been counted.  It is impossible (statistically, very close to zero probability) for Clinton to regain the lead.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">crabasa</dc:creator><pubDate>Mon, 05 May 2008 22:06:32 -0000</pubDate></item><item><title>Re: Why decentralizing Twitter is so important (Scripting News)</title><link>http://www.scripting.com/stories/2008/05/04/whyDecentralizingTwitterIs.html#comment-414375</link><description>I just had a conversation with a buddy in the Bay Area about Twitter.  He had some interesting insights into the sweet deal they got on SMS integration from the wireless carries (it's capped at a reasonable figure per month).  This, of course, is one of the differentiators that Twitter has that can't simply be replicated by decentralizing.&lt;br&gt;&lt;br&gt;But SMS notifications aside, caching feeds requires a much smarter client.  Right now Twitter clients can call a single method (friends_timeline) to get updates for a user and those she or he follows.  The caching solution means that a Twitter client will have to know who you are following, so that it can get the proper feeds and splice them together into a coherent time line.&lt;br&gt;&lt;br&gt;Which kind of bring me back around to my feeling that Twitter is kind of a walled-garden of blogging and blog-reading, where you "follow" instead of subscribe, etc.  I feel like the better long-term solution is for bloggers to create RSS feeds for their micro-blogging and provide an open API that blogging tools can implement (remember Trackback?) to notify blogger that people are "following" them.&lt;br&gt;&lt;br&gt;More: &lt;a href="http://cubanlinks.org/articles/2008/4/22/twitter-is-proprietary-rss" rel="nofollow"&gt;http://cubanlinks.org/articles/2008/4/22/twitte...&lt;/a&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">crabasa</dc:creator><pubDate>Sun, 04 May 2008 22:29:05 -0000</pubDate></item><item><title>Re: How to decouple from Twitter, now (Scripting News)</title><link>http://www.scripting.com/stories/2008/04/22/howToDecoupleFromTwitterNo.html#comment-365316</link><description>Dave, as much as I like FriendFeed, I think it is vulnerable in the same way Twitter is.  And cloning the API, while a good idea, just creates a small number of failure points rather than one.  That's an improvement, but has high switching costs in the event of outages (assuming you can even reliably detect an outage).&lt;br&gt;&lt;br&gt;I think an interesting and distributed solution would be to clone part of Twitter's API not for centralized services (Pownce, FriendFeed, etc) but for ALL blogging software.  If blogger A subscribes to blogger B, let the subscription tool for A notify the blogging tool for B.  It requires (or is at least expedited) by the idea of mashing reading and writing blogs.&lt;br&gt;&lt;br&gt;&lt;a href="http://cubanlinks.org/articles/2008/4/22/twitter-is-proprietary-rss" rel="nofollow"&gt;http://cubanlinks.org/articles/2008/4/22/twitte...&lt;/a&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">crabasa</dc:creator><pubDate>Tue, 22 Apr 2008 16:56:21 -0000</pubDate></item></channel></rss>