<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Disqus - Latest Comments for crabasa</title><link>http://disqus.com/people/crabasa/</link><description></description><language>en</language><lastBuildDate>Sun, 25 Oct 2009 19:28:06 -0000</lastBuildDate><item><title>Re: I Haz NFL Gamepass!</title><link>http://cubanlinks.disqus.com/i_haz_nfl_gamepass/#comment-21000524</link><description>Yeah, I had to install Tor (&lt;a href="http://www.torproject.org" rel="nofollow"&gt;http://www.torproject.org&lt;/a&gt;) and play around with some things (&lt;a href="https://www.torproject.org/faq#ChooseEntryExit" rel="nofollow"&gt;https://www.torproject.org/faq#ChooseEntryExit&lt;/a&gt;) to make my PC to appear to be outside of the US.  I'm definitely having some problems (I get logged-out of my account frequently, since my IP tends to change) but it's worth it  :)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">crabasa</dc:creator><pubDate>Sun, 25 Oct 2009 19:28:06 -0000</pubDate></item><item><title>Re: All the angst over Atom (Scripting News)</title><link>http://scripting.disqus.com/all_the_angst_over_atom_scripting_news/#comment-16026330</link><description>I had forgotten all about ATOM!  Those flame wars were legendary.  Wow, what a blast from the past...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">crabasa</dc:creator><pubDate>Sat, 05 Sep 2009 13:07:56 -0000</pubDate></item><item><title>Re: My Thoughts on Posterous as a Lifestreaming Platform</title><link>http://lifestreamblog.disqus.com/my_thoughts_on_posterous_as_a_lifestreaming_platform/#comment-15446417</link><description>Oh, I dunno. Postereous could easily replace Friendfeed as it is currently used by most of the people I follow. That's as a discussion board -- not an aggregator. &lt;br&gt;&lt;br&gt;FF moved from emphasizing lifestreaming to "conversation" as soon as it went with realtime. Most links I see in my stream are shared directly or are topics original to FF. Postereous can certainly handle that, particularly if it improves the robustness of its comment system or allows users to move to Echo or DISQUS.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">chrisbaskind</dc:creator><pubDate>Wed, 26 Aug 2009 20:48:58 -0000</pubDate></item><item><title>Re: My Thoughts on Posterous as a Lifestreaming Platform</title><link>http://lifestreamblog.disqus.com/my_thoughts_on_posterous_as_a_lifestreaming_platform/#comment-15445995</link><description>I completely agree.  As much as I admire the product that the Postereous team has put together, I am totally baffled by the concept that it could act as a suitable replacement to FriendFeed.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">crabasa</dc:creator><pubDate>Wed, 26 Aug 2009 20:33:33 -0000</pubDate></item><item><title>Re: How to fix URL-shorteners, part II (Scripting News)</title><link>http://scripting.disqus.com/how_to_fix_url_shorteners_part_ii_scripting_news/#comment-15396250</link><description>i have cloned the core bit.ly (including tracking) without even using a database (uses flat static files). &lt;br&gt;and it's done in about 100 lines of code.&lt;br&gt;&lt;br&gt;and click tracking is click tracking.  date/time, ip, referrer url.  standard stuff.  i only spent a few moments on &lt;a href="http://adjix.com" rel="nofollow"&gt;adjix.com&lt;/a&gt; but i did not even see these basic click stats.  but maybe i missed where more detailed stars are or maybe their is a partner/api dashboard that is more thorough.  &lt;br&gt;&lt;br&gt;anyway, glad you are happy with a solution.  at the same time, it's good that your readers/commenters are engaging the conversation with other ideas. &lt;br&gt;&lt;br&gt;cheers!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">sull</dc:creator><pubDate>Tue, 25 Aug 2009 22:54:09 -0000</pubDate></item><item><title>Re: How to fix URL-shorteners, part II (Scripting News)</title><link>http://scripting.disqus.com/how_to_fix_url_shorteners_part_ii_scripting_news/#comment-15395440</link><description>But... isn't that something that a halfway decent web analytics tool could provide for retrieval of static files?&lt;br&gt;&lt;br&gt;I don't mean to be a trouble-maker, but I just wonder if the "middleware" of a URL shortener is really adding that much value, given the trouble.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">crabasa</dc:creator><pubDate>Tue, 25 Aug 2009 22:31:48 -0000</pubDate></item><item><title>Re: How to fix URL-shorteners, part II (Scripting News)</title><link>http://scripting.disqus.com/how_to_fix_url_shorteners_part_ii_scripting_news/#comment-15394842</link><description>Tracking. Tracking. Tracking.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">dave</dc:creator><pubDate>Tue, 25 Aug 2009 22:13:39 -0000</pubDate></item><item><title>Re: How to fix URL-shorteners, part II (Scripting News)</title><link>http://scripting.disqus.com/how_to_fix_url_shorteners_part_ii_scripting_news/#comment-15386393</link><description>Dave, for those of us who don't know, can you please explain precisely what you would lose if Adjix went away?  Or another way of putting it, what value do they delivery when they're up?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">crabasa</dc:creator><pubDate>Tue, 25 Aug 2009 19:59:27 -0000</pubDate></item><item><title>Re: Disqus V3 Is Live On This Blog</title><link>http://avc.disqus.com/disqus_v3_is_live_on_this_blog/#comment-15211914</link><description>This is a comment for the sake of usability and editing</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ShanaC</dc:creator><pubDate>Fri, 21 Aug 2009 17:55:47 -0000</pubDate></item><item><title>Re: Disqus V3 Is Live On This Blog</title><link>http://avc.disqus.com/disqus_v3_is_live_on_this_blog/#comment-15206216</link><description>I think that is an option but I've never used it</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">fredwilson</dc:creator><pubDate>Fri, 21 Aug 2009 15:33:04 -0000</pubDate></item><item><title>Re: Disqus V3 Is Live On This Blog</title><link>http://avc.disqus.com/disqus_v3_is_live_on_this_blog/#comment-15203521</link><description>Daniel, thanks for the reply!  I would say (speaking for myself, my website and my customers) that "you must register" is indeed scary but "you must authenticate via Twitter or Facebook" is not.  Now, my customers are 21-35 y/o, so maybe I'm a niche case.  But I really, really want to limit comments to "real" people with "real" avatars.  Just my $0.02.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">crabasa</dc:creator><pubDate>Fri, 21 Aug 2009 14:29:54 -0000</pubDate></item><item><title>Re: Disqus V3 Is Live On This Blog</title><link>http://avc.disqus.com/disqus_v3_is_live_on_this_blog/#comment-15203187</link><description>We did a lot of field testing with this, actually. As with everything on the web, nothing is ever set in stone and I'm constantly revisiting this. But now for the explanation...&lt;br&gt;&lt;br&gt;You can set the options so that Guest commenting is disabled, however the fields still do show up. Once the user submits his comment, he is required to finish registration before the post is completed. We've found that this increased the number of people willing to comment many, many times.&lt;br&gt;&lt;br&gt;Simply put, a comment form hidden behind a "You must register" wall is scary to everyone.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">danielha</dc:creator><pubDate>Fri, 21 Aug 2009 14:22:48 -0000</pubDate></item><item><title>Re: Disqus V3 Is Live On This Blog</title><link>http://avc.disqus.com/disqus_v3_is_live_on_this_blog/#comment-15199750</link><description>I had an email exchange with Daniel Ha, stating pretty much what you wrote (although I would give preference to Disqus with email over FB or OID). He has some reasons for the fields to remain. I don't think it makes sense and I don't think they will change that setting in the next version.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">benatlas</dc:creator><pubDate>Fri, 21 Aug 2009 13:00:25 -0000</pubDate></item><item><title>Re: Disqus V3 Is Live On This Blog</title><link>http://avc.disqus.com/disqus_v3_is_live_on_this_blog/#comment-15199238</link><description>Well, I see why it's confusing: it doesn't remove the name/email/website fields.  An ideal implementation should require authentication via the available sites (FB, OpenId, etc) first and then allow a comment to be entered.  Maybe we'll see this in v3?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">crabasa</dc:creator><pubDate>Fri, 21 Aug 2009 12:48:45 -0000</pubDate></item><item><title>Re: Disqus V3 Is Live On This Blog</title><link>http://avc.disqus.com/disqus_v3_is_live_on_this_blog/#comment-15198887</link><description>under settings - admin/permissions set it to "registered"</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">benatlas</dc:creator><pubDate>Fri, 21 Aug 2009 12:39:46 -0000</pubDate></item><item><title>Re: Disqus V3 Is Live On This Blog</title><link>http://avc.disqus.com/disqus_v3_is_live_on_this_blog/#comment-15198690</link><description>I just scanned my settings and didn't see anything like that.  Can you elaborate?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">crabasa</dc:creator><pubDate>Fri, 21 Aug 2009 12:35:30 -0000</pubDate></item><item><title>Re: Disqus V3 Is Live On This Blog</title><link>http://avc.disqus.com/disqus_v3_is_live_on_this_blog/#comment-15198510</link><description>there is already option like that, look at your settings, i tried and then disabled, too confusing for the readers</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">benatlas</dc:creator><pubDate>Fri, 21 Aug 2009 12:31:31 -0000</pubDate></item><item><title>Re: Disqus V3 Is Live On This Blog</title><link>http://avc.disqus.com/disqus_v3_is_live_on_this_blog/#comment-15192371</link><description>This might sound crazy, but how about an option to disable "guest" comments?  For certain sites, requiring a Facebook/Twitter/OpenId/etc log-in to comment isn't outrageous.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">crabasa</dc:creator><pubDate>Fri, 21 Aug 2009 10:17:18 -0000</pubDate></item><item><title>Re: Disqus V3 Is Live On This Blog</title><link>http://avc.disqus.com/disqus_v3_is_live_on_this_blog/#comment-15191910</link><description>i used typepad's comment system for about four years before moving to disqus. i get way less spam now and it is simple to delete the spam that i do get (maybe one or two a week). you can even delete the comment spam via email which is great for me.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">fredwilson</dc:creator><pubDate>Fri, 21 Aug 2009 10:08:02 -0000</pubDate></item><item><title>Re: Disqus V3 Is Live On This Blog</title><link>http://avc.disqus.com/disqus_v3_is_live_on_this_blog/#comment-15191768</link><description>I am VERY interested in this update.  I've had mixed feelings using Disqus on my personal blog due to spam getting through.  And this has kept me from launching it on my business' blog, despite my strong desire to give my customers a means of communicating freely via comments.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">crabasa</dc:creator><pubDate>Fri, 21 Aug 2009 10:04:42 -0000</pubDate></item><item><title>Re: Facebook acquires Friendfeed for $50 million according to the WSJ</title><link>http://loiclemeur.disqus.com/facebook_acquires_friendfeed_for_50_million_according_to_the_wsj/#comment-14604414</link><description>Doesn't that strike anyone as kind of low?  I guess the FriendFeed guys were a million miles away from a business plan and Facebook is essentially purchasing a codebase and some of the best talent in the Valley.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">crabasa</dc:creator><pubDate>Mon, 10 Aug 2009 19:19:23 -0000</pubDate></item><item><title>Re: How to get started with Facebook's new API? (Scripting News)</title><link>http://scripting.disqus.com/how_to_get_started_with_facebooks_new_api_scripting_news/#comment-8741576</link><description>&lt;blockquote&gt;The moral of the story is that developing on Facebook's platform is incredibly daunting...&lt;/blockquote&gt;&lt;br&gt;&lt;br&gt;This is true in my experience as well -- when I was actively developing for the Facebook platform, they actually had &lt;i&gt;showstopping bugs in their official PHP client&lt;/i&gt;, something I literally have never seen before. It was like it went out the door without anyone bothering to test it.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">sameasiteverwas</dc:creator><pubDate>Mon, 27 Apr 2009 14:28:42 -0000</pubDate></item><item><title>Re: How to get started with Facebook's new API? (Scripting News)</title><link>http://scripting.disqus.com/how_to_get_started_with_facebooks_new_api_scripting_news/#comment-8738370</link><description>I spent a weekend with a group of programmers trying to spin-up a proof of concept using Facebook Connect.  By the end of the weekend we had virtually nothing, and I ended up presenting a demo using a bunch of static images and JQuery magic.  &lt;br&gt;&lt;br&gt;The moral of the story is that developing on Facebook's platform is incredibly daunting, and I believe this has to do with their notion of "dynamic privacy".  So, instead of simply sending data along a wire based on a request (REST), you have to deal with an elaborate web of hooks and callbacks.  :(</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">crabasa</dc:creator><pubDate>Mon, 27 Apr 2009 12:57:44 -0000</pubDate></item><item><title>Re: Engagement Photos</title><link>http://cubanlinks.disqus.com/engagement_photos/#comment-8572117</link><description>Wow, that's a little embarrassing.  :)  I'm sure you're referring to Carrie.  I definitely married "up".</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">crabasa</dc:creator><pubDate>Wed, 22 Apr 2009 11:33:26 -0000</pubDate></item><item><title>Re: Twitter-to-FriendFeed</title><link>http://twitter-to-friendfeedcontactsync.disqus.com/twitter_to_friendfeed/#comment-8455641</link><description>Yeah, Twitter changed their API and now the app is broken.  I don't see this getting fixed anytime soon.  Sorry :(</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">crabasa</dc:creator><pubDate>Mon, 20 Apr 2009 13:35:12 -0000</pubDate></item></channel></rss>