<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Disqus - Latest Comments for James Henstridge</title><link>http://disqus.com/people/9d9b7698c26959f57c0e3814005b8b52/</link><description></description><language>en</language><lastBuildDate>Tue, 04 Nov 2008 03:38:04 -0000</lastBuildDate><item><title>Re: Games Worth Playing - Miguel de Icaza</title><link>http://migueldeicaza.disqus.com/games_worth_playing_miguel_de_icaza/#comment-490033</link><description>One of the best PS2 games I played last year was Okami.  It is a decent length, and the story line was interesting (based on various bits of Japanese mythology/history).  The brush/calligraphy based attack system was unlike anything I'd used before.&lt;br&gt;&lt;br&gt;There is also a Wii port now.  I haven't tried it, but I can see the attack system fitting that controller pretty well.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">James Henstridge</dc:creator><pubDate>Mon, 19 May 2008 11:01:04 -0000</pubDate></item><item><title>Re: oh. hi. - Miguel de Icaza</title><link>http://migueldeicaza.disqus.com/oh_hi_miguel_de_icaza/#comment-697512</link><description>It isn't like this is the first time pop culture references have worked their way into API naming.&lt;br&gt;&lt;br&gt;IIRC, gtk_file_chooser_set_local_only() was a League of Gentlemen reference.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">James Henstridge</dc:creator><pubDate>Wed, 18 Jun 2008 03:30:29 -0000</pubDate></item><item><title>Re: Securing a Unix Domain Socket: Looking for Help - Miguel de Icaza</title><link>http://migueldeicaza.disqus.com/securing_a_unix_domain_socket_looking_for_help_miguel_de_icaza/#comment-2367740</link><description>One extra layer of protection you could use is to check the SO_PEERCRED socket option on the application side to make sure the correct user connected.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">James Henstridge</dc:creator><pubDate>Mon, 15 Sep 2008 21:43:52 -0000</pubDate></item><item><title>Re: Securing a Unix Domain Socket: Looking for Help - Miguel de Icaza</title><link>http://migueldeicaza.disqus.com/securing_a_unix_domain_socket_looking_for_help_miguel_de_icaza/#comment-2382608</link><description>My understanding is that a client can't affect the information returned by SO_PEERCRED on the other end of the socket (assuming they can't setuid() or similar).  The default access configuration for PostgreSQL on my machine uses peer credentials to authenticate local connections, so they obviously trust it (&lt;a href="http://www.postgresql.org/docs/8.3/static/auth-methods.html#AEN26734" rel="nofollow"&gt;http://www.postgresql.org/docs/8.3/static/auth-...&lt;/a&gt;).&lt;br&gt;&lt;br&gt;Of course, this isn't available everywhere, so might not be appropriate for some of your target systems.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">James Henstridge</dc:creator><pubDate>Tue, 16 Sep 2008 06:41:20 -0000</pubDate></item><item><title>Re: Mono's SIMD Support: Making Mono safe for Gaming - Miguel de Icaza</title><link>http://migueldeicaza.disqus.com/monos_simd_support_making_mono_safe_for_gaming_miguel_de_icaza/#comment-3469540</link><description>I assume the "Vector3f" bits in the second code snippet should be "Vector4f", right?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">James Henstridge</dc:creator><pubDate>Tue, 04 Nov 2008 03:38:04 -0000</pubDate></item><item><title>Re: Delegating your OpenID so it works with Wordpress Plugin</title><link>http://jonesieboy.disqus.com/delegating_your_openid_so_it_works_with_wordpress_plugin/#comment-2268068</link><description>If you are delegating, wouldn't it be easier to go all out and point directly at your myOpenID XRDS document?&lt;br&gt;&lt;br&gt;Just set X-XRDS-Location to &lt;a href="http://robertjones.myopenid.com/xrds" rel="nofollow"&gt;http://robertjones.myopenid.com/xrds&lt;/a&gt; and it will expose all the capabilities of the provider, including OpenID 2.0 support.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">James Henstridge</dc:creator><pubDate>Thu, 13 Dec 2007 04:24:19 -0000</pubDate></item><item><title>Re: BazaarNG and Mercurial and Git</title><link>http://phildawesstuff.disqus.com/bazaarng_and_mercurial_and_git/#comment-2753312</link><description>You might want to check out bzr 0.8 when it comes out (should be within a week), as it addresses a number of the issues you bring up.&lt;br&gt;&lt;br&gt;There is a new branch format that will improve network performance.&lt;br&gt;&lt;br&gt;There is a new repository concept that allows you to share the version control information for multiple branches in a shared location (a parent directory).  If your branches are related, this will save a lot of space.  You can also have branches without a working tree (i.e. only version control data).&lt;br&gt;&lt;br&gt;And while bzr is backed by Canonical, there is a fair number of external contributors (just check the revision history).</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">James Henstridge</dc:creator><pubDate>Thu, 27 Apr 2006 10:32:07 -0000</pubDate></item><item><title>Re: Reformatted Bazaar docs</title><link>http://sandipbnet.disqus.com/reformatted_bazaar_docs/#comment-18822516</link><description>Wouldn't a better solution be to get the Python docutils package to convert reStructuredText to texinfo?&lt;br&gt;&lt;br&gt;Having two sources for the documentation will just result in things getting out of sync, so unless you can convince people to switch to texinfo completely, then it probably won't get accepted.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">James Henstridge</dc:creator><pubDate>Tue, 07 Jun 2005 07:27:03 -0000</pubDate></item><item><title>Re: Reformatted Bazaar docs</title><link>http://sandipbnet.disqus.com/reformatted_bazaar_docs/#comment-18822518</link><description>&lt;p&gt;In that case, you'd do better trying to convince people to switch to texinfo as a source.  I do wonder why you'd choose texinfo over something like docbook/xml though.&lt;/p&gt;&lt;br&gt;&lt;p&gt;I think you are underestimating what the docutils package can do though -- it seems expressive enough, and the tools available seem okay too.  Are there particular things you want to express in the documentation that reStructuredText can't handle?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">James Henstridge</dc:creator><pubDate>Tue, 07 Jun 2005 21:21:22 -0000</pubDate></item></channel></rss>