<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments for xyzzy xyzzy...</title>
	<atom:link href="http://xyzzyxyzzy.net/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://xyzzyxyzzy.net</link>
	<description>...you are in a grid of twisty, little links, all alike. there's a teleport gate here.</description>
	<pubDate>Wed, 09 Jul 2008 02:39:10 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>Comment on updated mono build script for hardy heron and mono 1.9.1 by Darb Dabney&#8217;s OpenSim Blog &#187; OpenSim 0.5.8 server 64-bit build steps for Ubuntu 8.04 HOWTO</title>
		<link>http://xyzzyxyzzy.net/2008/05/08/updated-mono-build-script-for-hardy-heron-and-mono-191/#comment-238</link>
		<dc:creator>Darb Dabney&#8217;s OpenSim Blog &#187; OpenSim 0.5.8 server 64-bit build steps for Ubuntu 8.04 HOWTO</dc:creator>
		<pubDate>Mon, 07 Jul 2008 05:27:06 +0000</pubDate>
		<guid isPermaLink="false">http://xyzzyxyzzy.net/?p=103#comment-238</guid>
		<description>&lt;p&gt;[...] Upgrade to Mono 1.9.1 per previous page&#8217;s performance hint IMHO it is a big hairy deal to compile the latest Mono from source, but at this point it sort of [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] Upgrade to Mono 1.9.1 per previous page&#8217;s performance hint IMHO it is a big hairy deal to compile the latest Mono from source, but at this point it sort of [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on updated mono build script for hardy heron and mono 1.9.1 by Darb Dabney&#8217;s OpenSim Blog &#187; An OpenSim server 64-bit HOWTO for svn_5341 post-0.5.8</title>
		<link>http://xyzzyxyzzy.net/2008/05/08/updated-mono-build-script-for-hardy-heron-and-mono-191/#comment-237</link>
		<dc:creator>Darb Dabney&#8217;s OpenSim Blog &#187; An OpenSim server 64-bit HOWTO for svn_5341 post-0.5.8</dc:creator>
		<pubDate>Mon, 07 Jul 2008 02:39:13 +0000</pubDate>
		<guid isPermaLink="false">http://xyzzyxyzzy.net/?p=103#comment-237</guid>
		<description>&lt;p&gt;[...] previous page&#8217;s performance hint IMHO it is a big hairy deal to compile the latest Mono from source, but at this point it sort of [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] previous page&#8217;s performance hint IMHO it is a big hairy deal to compile the latest Mono from source, but at this point it sort of [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on weird inventions: the jerusalem compass&#8230;or: patenting magic by Chaim</title>
		<link>http://xyzzyxyzzy.net/2007/12/20/weird-inventions-the-jerusalem-compassor-patenting-magic/#comment-235</link>
		<dc:creator>Chaim</dc:creator>
		<pubDate>Wed, 28 May 2008 10:00:45 +0000</pubDate>
		<guid isPermaLink="false">http://xyzzyxyzzy.net/2007/12/20/weird-inventions-the-jerusalem-compassor-patenting-magic/#comment-235</guid>
		<description>&lt;p&gt;Hi,&lt;/p&gt;

&lt;p&gt;Acutally, I live in Jerusalem and what Yossi said is true, that is if we understand what the original commentor was referring to.
   I have the compass, and it has a mechanical recalibrator so that when ever you travel from country to country, you can re-set it  one time, "just like your watch", and it will alway point in the proper direction.
    If you live in Israel as I do, so there is no difference. When you travel to Tel Aviv it is set for Tel Aviv, if you travel to Be'er Sheva, down South, so it has a recalibration for each city in Israel. It makes no difference if you travel N,S,E or West, it is recalibrated just as you would do when travelling through different international countries.
  The first comment above is confusing as the term, "margin of error" is used. there is no margin of error when one travels N,S. E. or W wether in the U.S. or in Israel etc. As long as one adjusts the compass in accordance with the proper instructions. Even in Jerusalem there are settings for different neighborhoods, so in this case it is not pointing to Jerusalem, but rather to Har habais. Some Rabbi's use the compass for weddings to know in which direction to face the chupah.
   "Margin of error", can only be understood to refer to something that  is not functioning proplerly, i.e. even when you follow the instructions. So, if you are in Tel Aviv, and the compass is NOT functioning properly, i.e. maybe there is some metal too close to it, and we all know what metal (iron) will do to a magnetic compass. So, since one is relatively close to Jerusalem,(about 40 miles), since they are so close, even if the compass is a little bit off,i.e 5 degrees etc, due to some "margin of error", it will still be pointing to Jerusalem. But, if 5,000 miles away, something is causing the compass to malfunction as stated, the same 5 degrees would be much more of a significant descrepency than if close to Jerusalem.
    The part above about the "world being round", I am not sure what that refers to. Firstly the world is NOT round but more pumpkin shaped. And, what does it mean that no matter which way you face you will be facing, Jerusalem, Mecca etc.   I guess this is probably some Letzanus.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Hi,</p>

<p>Acutally, I live in Jerusalem and what Yossi said is true, that is if we understand what the original commentor was referring to.
   I have the compass, and it has a mechanical recalibrator so that when ever you travel from country to country, you can re-set it  one time, &#8220;just like your watch&#8221;, and it will alway point in the proper direction.
    If you live in Israel as I do, so there is no difference. When you travel to Tel Aviv it is set for Tel Aviv, if you travel to Be&#8217;er Sheva, down South, so it has a recalibration for each city in Israel. It makes no difference if you travel N,S,E or West, it is recalibrated just as you would do when travelling through different international countries.
  The first comment above is confusing as the term, &#8220;margin of error&#8221; is used. there is no margin of error when one travels N,S. E. or W wether in the U.S. or in Israel etc. As long as one adjusts the compass in accordance with the proper instructions. Even in Jerusalem there are settings for different neighborhoods, so in this case it is not pointing to Jerusalem, but rather to Har habais. Some Rabbi&#8217;s use the compass for weddings to know in which direction to face the chupah.
   &#8220;Margin of error&#8221;, can only be understood to refer to something that  is not functioning proplerly, i.e. even when you follow the instructions. So, if you are in Tel Aviv, and the compass is NOT functioning properly, i.e. maybe there is some metal too close to it, and we all know what metal (iron) will do to a magnetic compass. So, since one is relatively close to Jerusalem,(about 40 miles), since they are so close, even if the compass is a little bit off,i.e 5 degrees etc, due to some &#8220;margin of error&#8221;, it will still be pointing to Jerusalem. But, if 5,000 miles away, something is causing the compass to malfunction as stated, the same 5 degrees would be much more of a significant descrepency than if close to Jerusalem.
    The part above about the &#8220;world being round&#8221;, I am not sure what that refers to. Firstly the world is NOT round but more pumpkin shaped. And, what does it mean that no matter which way you face you will be facing, Jerusalem, Mecca etc.   I guess this is probably some Letzanus.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on splitting opensim&#8217;s chat module by Nathan Eckenrode</title>
		<link>http://xyzzyxyzzy.net/2008/05/27/splitting-opensims-chat-module/#comment-234</link>
		<dc:creator>Nathan Eckenrode</dc:creator>
		<pubDate>Tue, 27 May 2008 13:48:24 +0000</pubDate>
		<guid isPermaLink="false">http://xyzzyxyzzy.net/?p=112#comment-234</guid>
		<description>&lt;p&gt;this is awesome! i love the direction that this is taking!&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>this is awesome! i love the direction that this is taking!</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on being slartibartfast&#8230; by Cranky</title>
		<link>http://xyzzyxyzzy.net/2008/03/10/being-slartibartfast/#comment-232</link>
		<dc:creator>Cranky</dc:creator>
		<pubDate>Fri, 23 May 2008 13:24:19 +0000</pubDate>
		<guid isPermaLink="false">http://xyzzyxyzzy.net/2008/03/10/being-slartibartfast/#comment-232</guid>
		<description>&lt;p&gt;Very good tut. Had a new terrain in just a few minutes.&lt;/p&gt;

&lt;p&gt;This bit was the sticking point for several days for me:
rename all *.raw files to *.r32 so that opensim does not mistake them for LindenLab raw files&lt;/p&gt;

&lt;p&gt;Two points to add:
terrain commands have since dropped the 'script' part and no need to run a script to load terrains at startup, they stick now.&lt;/p&gt;

&lt;p&gt;Slartibartfast indeed!
Keep up the good work.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Very good tut. Had a new terrain in just a few minutes.</p>

<p>This bit was the sticking point for several days for me:
rename all *.raw files to *.r32 so that opensim does not mistake them for LindenLab raw files</p>

<p>Two points to add:
terrain commands have since dropped the &#8217;script&#8217; part and no need to run a script to load terrains at startup, they stick now.</p>

<p>Slartibartfast indeed!
Keep up the good work.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on which serialization format for OpenSim REST services? by Gareth Nelson</title>
		<link>http://xyzzyxyzzy.net/2008/05/14/serialization-format-for-opensim-rest-services/#comment-230</link>
		<dc:creator>Gareth Nelson</dc:creator>
		<pubDate>Sat, 17 May 2008 19:15:14 +0000</pubDate>
		<guid isPermaLink="false">http://xyzzyxyzzy.net/?p=104#comment-230</guid>
		<description>&lt;p&gt;I just ran into this post by chance........&lt;/p&gt;

&lt;p&gt;LLSD wins hands down, why have more formats than needed?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I just ran into this post by chance&#8230;&#8230;..</p>

<p>LLSD wins hands down, why have more formats than needed?</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on automatically downloading LindenLab™ account statements by Matthias Hub</title>
		<link>http://xyzzyxyzzy.net/2008/05/15/automatically-downloading-lindenlab%e2%84%a2-account-statements/#comment-229</link>
		<dc:creator>Matthias Hub</dc:creator>
		<pubDate>Fri, 16 May 2008 08:09:27 +0000</pubDate>
		<guid isPermaLink="false">http://xyzzyxyzzy.net/?p=106#comment-229</guid>
		<description>&lt;p&gt;dude, you rock!&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>dude, you rock!</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on which serialization format for OpenSim REST services? by Kyle H</title>
		<link>http://xyzzyxyzzy.net/2008/05/14/serialization-format-for-opensim-rest-services/#comment-228</link>
		<dc:creator>Kyle H</dc:creator>
		<pubDate>Wed, 14 May 2008 13:42:56 +0000</pubDate>
		<guid isPermaLink="false">http://xyzzyxyzzy.net/?p=104#comment-228</guid>
		<description>&lt;p&gt;I've sent my message to opensim-dev in support of JSON, for reasons which relate partially to "how expensive is it to transmit XML?  how expensive is it to parse XML?"  I also like your point that JSON distinguishes between 4711 and "4711".&lt;/p&gt;

&lt;p&gt;Really, a representation language that can be described in 5 state diagrams is much better than the huge and overspecified cruft from the W3C.  Regardless of the fact that there's a documented interface to parse it, how many times have the XML parsers been found to have bugs?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I&#8217;ve sent my message to opensim-dev in support of JSON, for reasons which relate partially to &#8220;how expensive is it to transmit XML?  how expensive is it to parse XML?&#8221;  I also like your point that JSON distinguishes between 4711 and &#8220;4711&#8243;.</p>

<p>Really, a representation language that can be described in 5 state diagrams is much better than the huge and overspecified cruft from the W3C.  Regardless of the fact that there&#8217;s a documented interface to parse it, how many times have the XML parsers been found to have bugs?</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on which serialization format for OpenSim REST services? by Mo Hax</title>
		<link>http://xyzzyxyzzy.net/2008/05/14/serialization-format-for-opensim-rest-services/#comment-227</link>
		<dc:creator>Mo Hax</dc:creator>
		<pubDate>Wed, 14 May 2008 12:00:23 +0000</pubDate>
		<guid isPermaLink="false">http://xyzzyxyzzy.net/?p=104#comment-227</guid>
		<description>&lt;p&gt;Hate to be the wet blanket, but Agile places the burden of 'proof' on JSON to show that adding yet another tech to the OpenSim code base is worth it, not matter how simple and cool it is.&lt;/p&gt;

&lt;p&gt;What is it going to be used for? Who's the customer? People coding administrative front ends? Does this have any chance of growing into something more, like a way to query or add serialized assets?&lt;/p&gt;

&lt;p&gt;JSON seems obvious if this is just for administrative front end mashups. Maybe we limit the scope to that and make it JSON.&lt;/p&gt;

&lt;p&gt;LLSD would be my pick for asset serialization and such since it is more largely compatible with LL and the working group and includes three forms, xml, binary, and 'human readable', which I think is the one you are comparing JSON with.&lt;/p&gt;

&lt;p&gt;I suppose nothing wrong with having right tool for the job, and little mashes up better than JSON. But overall I prefer using what we have.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Hate to be the wet blanket, but Agile places the burden of &#8216;proof&#8217; on JSON to show that adding yet another tech to the OpenSim code base is worth it, not matter how simple and cool it is.</p>

<p>What is it going to be used for? Who&#8217;s the customer? People coding administrative front ends? Does this have any chance of growing into something more, like a way to query or add serialized assets?</p>

<p>JSON seems obvious if this is just for administrative front end mashups. Maybe we limit the scope to that and make it JSON.</p>

<p>LLSD would be my pick for asset serialization and such since it is more largely compatible with LL and the working group and includes three forms, xml, binary, and &#8216;human readable&#8217;, which I think is the one you are comparing JSON with.</p>

<p>I suppose nothing wrong with having right tool for the job, and little mashes up better than JSON. But overall I prefer using what we have.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on installing mono 1.9 by xyzzy xyzzy&#8230; &#187; updated mono build script for hardy heron and mono 1.9.1</title>
		<link>http://xyzzyxyzzy.net/2008/03/27/installing-mono-19/#comment-224</link>
		<dc:creator>xyzzy xyzzy&#8230; &#187; updated mono build script for hardy heron and mono 1.9.1</dc:creator>
		<pubDate>Thu, 08 May 2008 14:10:38 +0000</pubDate>
		<guid isPermaLink="false">http://xyzzyxyzzy.net/2008/03/27/installing-mono-19/#comment-224</guid>
		<description>&lt;p&gt;[...] (and my custom compiled kernel1) i ended up with a mutilated mono installation. just following my previous recipe didn&#8217;t work out too well for the mono document [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] (and my custom compiled kernel1) i ended up with a mutilated mono installation. just following my previous recipe didn&#8217;t work out too well for the mono document [...]</p>]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.345 seconds -->
