<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Disqus - Friends of gishdog</title><link>http://disqus.com/people/gishdog/</link><description></description><language>en</language><lastBuildDate>Mon, 20 Jul 2009 16:39:41 -0000</lastBuildDate><item><title>Re: Server Side Javascript Continued &amp;#8211; Node.js (plus example)</title><link>http://britg.com/2009/07/01/server-side-javascript-continued-node-js-plus-example/#comment-12970950</link><description>Hey John - from your console output, it looks like you are making requests to the wrong script.&lt;br&gt;&lt;br&gt;"example.js:28 ..."&lt;br&gt;&lt;br&gt;The name of the script, if you used the same copy from the github repo, should be 'gamelobby.js'&lt;br&gt;&lt;br&gt;Let me know if that helps!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Mon, 20 Jul 2009 16:39:41 -0000</pubDate></item><item><title>Re: Server Side Javascript Continued &amp;#8211; Node.js (plus example)</title><link>http://britg.com/2009/07/01/server-side-javascript-continued-node-js-plus-example/#comment-11986345</link><description>Very cool, will watch its progress on github :)  I like the Sinatra-esque lightweight approach.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Wed, 01 Jul 2009 13:47:44 -0000</pubDate></item><item><title>Re: Server Side Javascript Continued &amp;#8211; Node.js (plus example)</title><link>http://britg.com/2009/07/01/server-side-javascript-continued-node-js-plus-example/#comment-11978023</link><description>True, I plan to make some updates, the first of which is to use POST on the /join URL and enforce it.  Also, I will implement a reaper process to clear stale joins.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Wed, 01 Jul 2009 10:34:49 -0000</pubDate></item><item><title>Re: Nginx Proxies with FirePHP</title><link>http://britg.com/2009/06/16/nginx-proxies-with-firephp/#comment-11499027</link><description>And yes, I think Jack support is a great move for the project -- I think it'll find more adoption on Jack than Jaxer.  Nothing wrong with Jaxer, but I have a feeling that Jack will be widely adopted going forward just because of it's WSGI/Rack approach.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Sat, 20 Jun 2009 09:30:22 -0000</pubDate></item><item><title>Re: Nginx Proxies with FirePHP</title><link>http://britg.com/2009/06/16/nginx-proxies-with-firephp/#comment-11498943</link><description>Very cool project you put together!  I will definitely give it a try -- I'm finding that I can't live without FirePHP now.  I'm sure that will carry over to my server-side JS projects and this sounds like the perfect solution.  Cheers!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Sat, 20 Jun 2009 09:25:23 -0000</pubDate></item><item><title>Re: Three Cheers for CakePHP Backwards Compatibility</title><link>http://britg.com/2009/01/27/three-cheers-for-cakephp-backwards-compatibility/#comment-5583502</link><description>Yeah, I agree about ActionScript camel casing.  Some languages just _feel_ like they should be camelcased and other _feel_ like they are underscored -- usually correlated to whether they are OO or not.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Tue, 27 Jan 2009 12:01:49 -0000</pubDate></item><item><title>Re: Integrating CakePHP with bbPress - Part 1</title><link>http://britg.com/2008/08/23/integrating-cakephp-with-bbpress-part-1/#comment-5011635</link><description>Well, my first approach when I get time to revisit would be to use the same&lt;br&gt;cookie mechanism i'm already using in my cake app - namely the cookie&lt;br&gt;handler.  I usually dont rely just on Sessions for my user login, but set a&lt;br&gt;cookie also.&lt;br&gt;&lt;br&gt;I would extend the Cookie handler built into cake to tap into the same&lt;br&gt;libraries that BBPress is using (either by duplication or inclusion), and&lt;br&gt;when I set my cake cookie I also set a BBPress cookie, and a session&lt;br&gt;variable if BBPress requires one.&lt;br&gt;&lt;br&gt;Hope that helps - and yes, I apologize that I have not finished part 3 - it&lt;br&gt;kills me as well!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Fri, 09 Jan 2009 09:19:21 -0000</pubDate></item><item><title>Re: It&amp;#8217;s hard to like the PHP &amp;#8216;Elite&amp;#8217;</title><link>http://britg.com/2009/01/08/its-hard-to-like-the-php-elite/#comment-4994848</link><description>Ouch, that's unfortunate that it got posted before you could finish your train of thought.  I've redacted my "this guy doesn't get it" statement - the rest of your argument is a lot more thought out.  Are you going to pub it on your blog?  Won't get heard here.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Thu, 08 Jan 2009 15:25:28 -0000</pubDate></item><item><title>Re: Integrating CakePHP with bbPress - Part 1</title><link>http://britg.com/2008/08/23/integrating-cakephp-with-bbpress-part-1/#comment-4990265</link><description>No, unfortunately I haven't taken the time to finish this out or the project&lt;br&gt;that this was for!  I really hope to revisit soon.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Thu, 08 Jan 2009 11:18:20 -0000</pubDate></item><item><title>Re: The Winter Beer of 2008 - Michelob Winter&amp;#8217;s Bourbon Cask Ale</title><link>http://britg.com/2008/12/25/the-winter-beer-of-2008-michelob-winters-bourbon-cask-ale/#comment-4788267</link><description>God yeah it's damn smooth and the hint of Vanilla is the kicker.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Tue, 30 Dec 2008 16:52:15 -0000</pubDate></item><item><title>Re: Integrating CakePHP with bbPress - Part 2</title><link>http://britg.com/2008/08/25/integrating-cakephp-with-bbpress-part-2/#comment-3273453</link><description>Thanks, yes I really intend to write part 3 - but unfortunately the project&lt;br&gt;I was doing this for has been put on hold for the moment!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Fri, 24 Oct 2008 09:10:11 -0000</pubDate></item><item><title>Re: Who Google Chrome Affects the Most</title><link>http://britg.com/2008/09/02/who-google-chrome-affects-the-most/#comment-2996971</link><description>Haha, yes good points all around.  I do agree that this is a good thing for&lt;br&gt;web developers in general because it does force Adobe to keep up with speed&lt;br&gt;and accessibility of ajax in flash.&lt;br&gt;&lt;br&gt;In response to your Microsoft point - they don't necessarily have to adopt&lt;br&gt;Google's technology for V8 to have an affect on Adobe.  Since MS and Google&lt;br&gt;are so competitive, I can see a scenario where Microsoft comes out with&lt;br&gt;their own new-fangled js engine that touts more and better features than V8&lt;br&gt;etc, etc.  This will lead to the web tech conversation switching tone from&lt;br&gt;"ajax vs flash" to "google's js tech vs MS's js tech".  This is bad for&lt;br&gt;Adobe.&lt;br&gt;&lt;br&gt;I do agree with you that flash isn't going anywhere even in this scenario.&lt;br&gt;It's all up to Adobe and where they take the platform.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Sat, 11 Oct 2008 07:57:06 -0000</pubDate></item><item><title>Re: Why Aptana is Quickly Becoming the Killer Stack</title><link>http://britg.com/2008/08/26/why-aptana-is-quickly-becoming-the-killer-stack/#comment-2935026</link><description>Check out the response to the word wrap issue report here:&lt;br&gt;&lt;a href="http://support.aptana.com/asap/browse/STU-534?focusedCommentId=18301#action_18301" rel="nofollow"&gt;http://support.aptana.com/asap/browse/STU-534?f...&lt;/a&gt;&lt;br&gt;&lt;br&gt;He explains how to turn on wordwrap.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Wed, 08 Oct 2008 08:55:11 -0000</pubDate></item><item><title>Re: Using the Zend Framework in CakePHP</title><link>http://britg.com/2008/07/07/using-the-zend-framework-in-cakephp/#comment-2406367</link><description>Interesting - i guess the most extensible solution would be to check if&lt;br&gt;there is a semicolon and add it if there is not - like your case.&lt;br&gt;Thanks for sharing</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Wed, 17 Sep 2008 15:43:26 -0000</pubDate></item><item><title>Re: The Answer To Gaming Piracy Was Perfected Over a Decade Ago</title><link>http://britg.com/2008/09/14/the-answer-to-gaming-piracy-was-perfected-over-a-decade-ago/#comment-2383202</link><description>Online is the only answer to prevent piracy without compromising customer's computers/privacy/gameplay.  It's fine that you don't like playing games online, but my point is that publishers should publish single player games with NO DRM and understand that there will be piracy.   If they care about piracy, the only method to prevent it is to create a valuable online component to a game that only legitimatly purchased copies can connect to!  Hobble the pirates, not the payers.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Tue, 16 Sep 2008 08:12:21 -0000</pubDate></item><item><title>Re: Integrating CakePHP with bbPress - Part 2</title><link>http://britg.com/2008/08/25/integrating-cakephp-with-bbpress-part-2/#comment-2347983</link><description>No problem!  glad to help.  Been slammed with other stuff and haven't been able to work on this project, but I'll definitely get around to writing part 3.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Sun, 14 Sep 2008 13:46:29 -0000</pubDate></item><item><title>Re: Ok, Apple Not Stupid - The Have Just Turned Into &amp;#8220;The Man&amp;#8221;</title><link>http://britg.com/2008/09/09/ok-apple-not-stupid-the-have-just-turned-into-the-man/#comment-2248100</link><description>Interesting argument, and yes I agree the iphone platform is still in its&lt;br&gt;infancy.  But, I see no reason why we can't take a look at now-mature&lt;br&gt;platforms (like the internet) and apply the some critical thinking.  Namely,&lt;br&gt;walled gardens don't work (AOL, etc).  Also, no matter how secure you think&lt;br&gt;you are - someone is always out there smarter and more determined than you&lt;br&gt;to break your security (DRM, etc).&lt;br&gt;So, Apple needs to allow applications like Big5 to roam free.  If it's an&lt;br&gt;issue where they KNOW about security risks and just haven't fixed them yet,&lt;br&gt;then be upfront damnit - Dirk spent quite a lot of time on Big5 and got&lt;br&gt;absolutely nothing in return.  There are other phonegap developers like&lt;br&gt;myself that are frustrated for him.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Tue, 09 Sep 2008 13:35:15 -0000</pubDate></item><item><title>Re: Ok, Apple Not Stupid - The Have Just Turned Into &amp;#8220;The Man&amp;#8221;</title><link>http://britg.com/2008/09/09/ok-apple-not-stupid-the-have-just-turned-into-the-man/#comment-2246332</link><description>Haha, you're right - I probably will love the wild west of Android.  &lt;br&gt;&lt;br&gt;I agree that IE itself wasn't that important - but the concept behind it was - release an application that spawns innovation and fix the security holes when they arise.  Windows is a nest for malicious software because they chose innovation over caution.  But without that, the computer industry wouldn't be where it's at today, and Apple would have never been able to establish itself as the 'safe alternative' and the 'cool kid on the block.'&lt;br&gt;&lt;br&gt;The funny thing is, I'm writing this from a macbook pro :)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Tue, 09 Sep 2008 11:26:53 -0000</pubDate></item><item><title>Re: Apple Too Stupid to Understand Utility of Outside-The-Box Apps</title><link>http://britg.com/2008/09/08/apple-too-stupid-to-understand-utility-of-outside-the-box-apps/#comment-2245672</link><description>Thanks Dirk for shedding some light.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Tue, 09 Sep 2008 10:42:31 -0000</pubDate></item><item><title>Re: Apple Too Stupid to Understand Utility of Outside-The-Box Apps</title><link>http://britg.com/2008/09/08/apple-too-stupid-to-understand-utility-of-outside-the-box-apps/#comment-2238176</link><description>Yeah, good points about the impact of 'limited utility'.  Your last question&lt;br&gt;has scary implications, and if the answer is 'yes' I see the application&lt;br&gt;pool stagnating after a certain number of iPint's and 'Pull my thumb' apps&lt;br&gt;being released.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Mon, 08 Sep 2008 18:12:40 -0000</pubDate></item><item><title>Re: Apple Too Stupid to Understand Utility of Outside-The-Box Apps</title><link>http://britg.com/2008/09/08/apple-too-stupid-to-understand-utility-of-outside-the-box-apps/#comment-2235151</link><description>If that is the case, Apple owes it to their developers to give us that type of explanation.  I think there is a chance here the reviewer or team of reviewers just didn't think outside of the box, and decided that we don't need another web browser app.&lt;br&gt;&lt;br&gt;If they really did understand the full implications of the app and denied it with a boilerplate response then it's not worth the time and effort to make a remotely innovative iphone application in my opinion.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Mon, 08 Sep 2008 15:56:43 -0000</pubDate></item><item><title>Re: Apple Too Stupid to Understand Utility of Outside-The-Box Apps</title><link>http://britg.com/2008/09/08/apple-too-stupid-to-understand-utility-of-outside-the-box-apps/#comment-2233584</link><description>Saying Big5 is useless is similar to saying Firefox was stupid when it came out.  Or, that any browser but Internet Explorer and Safari are stupid.&lt;br&gt;&lt;br&gt;Here's the big secret - Big5 uses the exact same SDK as every other app.  The SDK provides a component to access websites, called WebView, that lots of apps use, including Big5.  The security risk in Big5 is the same security risk that any application that accesses a web site has!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Mon, 08 Sep 2008 14:15:59 -0000</pubDate></item><item><title>Re: Apple Too Stupid to Understand Utility of Outside-The-Box Apps</title><link>http://britg.com/2008/09/08/apple-too-stupid-to-understand-utility-of-outside-the-box-apps/#comment-2231203</link><description>Wrong on every level - big5 uses exactly the same tools that every  &lt;br&gt;other app uses!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Mon, 08 Sep 2008 11:24:22 -0000</pubDate></item><item><title>Re: Apple Too Stupid to Understand Utility of Outside-The-Box Apps</title><link>http://britg.com/2008/09/08/apple-too-stupid-to-understand-utility-of-outside-the-box-apps/#comment-2231109</link><description>Very true and this is what scares me the most- not that the reviewers  &lt;br&gt;are stupid but that they DO understand and are intentionally blocking</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Mon, 08 Sep 2008 11:18:11 -0000</pubDate></item><item><title>Re: Apple Too Stupid to Understand Utility of Outside-The-Box Apps</title><link>http://britg.com/2008/09/08/apple-too-stupid-to-understand-utility-of-outside-the-box-apps/#comment-2230598</link><description>Haha, ok I agree the headline was a bit over the top, but it just reads better than 'Some Team In Apple's Iphone App Review Department Is Too Stupid To Understand Utility of Outside-The-Box Apps".&lt;br&gt;&lt;br&gt;Regarding your points - the first few steps of that messy process is meant to be alleviated by getting approved for the app store.  If Big5 were a downloadable app, all a user would have to do is 1) open the app, 2) type in the web address just like in Safari.&lt;br&gt;&lt;br&gt;You are probably right about apple censoring apps that act as another web browser for whatever reason.  But, just compare that what Microsoft got in a lot of trouble for doing with Internet explorer in windows.  Same exact situation.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Mon, 08 Sep 2008 10:37:46 -0000</pubDate></item></channel></rss>