<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for Canyon R</title>
	<atom:link href="http://canyonr.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://canyonr.com</link>
	<description>Standing on the corner of Technology and Reality</description>
	<lastBuildDate>Tue, 13 Apr 2010 13:59:48 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>Comment on Why I bought a Nexus One. by Brakk</title>
		<link>http://canyonr.com/2010/04/why-i-bought-a-nexus-one/comment-page-1/#comment-52</link>
		<dc:creator>Brakk</dc:creator>
		<pubDate>Tue, 13 Apr 2010 13:59:48 +0000</pubDate>
		<guid isPermaLink="false">http://canyonr.com/?p=51#comment-52</guid>
		<description>I&#039;m holding out for a DOS based smart phone.</description>
		<content:encoded><![CDATA[<p>I&#8217;m holding out for a DOS based smart phone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why I bought a Nexus One. by Canyon</title>
		<link>http://canyonr.com/2010/04/why-i-bought-a-nexus-one/comment-page-1/#comment-46</link>
		<dc:creator>Canyon</dc:creator>
		<pubDate>Mon, 12 Apr 2010 15:17:55 +0000</pubDate>
		<guid isPermaLink="false">http://canyonr.com/?p=51#comment-46</guid>
		<description>I&#039;ll see what I can do for an unboxing video. There are already so many out there I&#039;ll try to find a unique view to take.</description>
		<content:encoded><![CDATA[<p>I&#8217;ll see what I can do for an unboxing video. There are already so many out there I&#8217;ll try to find a unique view to take.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why I bought a Nexus One. by Albert Nabarrete</title>
		<link>http://canyonr.com/2010/04/why-i-bought-a-nexus-one/comment-page-1/#comment-47</link>
		<dc:creator>Albert Nabarrete</dc:creator>
		<pubDate>Mon, 12 Apr 2010 12:41:17 +0000</pubDate>
		<guid isPermaLink="false">http://canyonr.com/?p=51#comment-47</guid>
		<description>Thanks a lot!  That was really helpful, I just bookmarked your site.</description>
		<content:encoded><![CDATA[<p>Thanks a lot!  That was really helpful, I just bookmarked your site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why I bought a Nexus One. by David Beroll</title>
		<link>http://canyonr.com/2010/04/why-i-bought-a-nexus-one/comment-page-1/#comment-45</link>
		<dc:creator>David Beroll</dc:creator>
		<pubDate>Mon, 12 Apr 2010 09:46:44 +0000</pubDate>
		<guid isPermaLink="false">http://canyonr.com/?p=51#comment-45</guid>
		<description>Can&#039;t wait to see the unboxing...you are going to record the unboxing?  Looking forward to seeing it.</description>
		<content:encoded><![CDATA[<p>Can&#8217;t wait to see the unboxing&#8230;you are going to record the unboxing?  Looking forward to seeing it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The ubiquity of Google Wave by Brakk</title>
		<link>http://canyonr.com/2009/10/the-ubiquity-of-google-wave/comment-page-1/#comment-40</link>
		<dc:creator>Brakk</dc:creator>
		<pubDate>Thu, 15 Oct 2009 15:47:14 +0000</pubDate>
		<guid isPermaLink="false">http://canyonr.com/?p=43#comment-40</guid>
		<description>Everyone said the same thing about Twitter. Nobody really knew what it was good for, not even the developers. Who wanted another chat service that also ate up your text messages? In the end (which I think is still yet to come), it was the user community that defined and shaped what Twitter is now. People started using @ to refer to other users and # for topic tags, so the Twitter service incorporated those as features into their software.

I think the same will be true for Google Wave. It is a new tool, of which a use is yet to be defined.</description>
		<content:encoded><![CDATA[<p>Everyone said the same thing about Twitter. Nobody really knew what it was good for, not even the developers. Who wanted another chat service that also ate up your text messages? In the end (which I think is still yet to come), it was the user community that defined and shaped what Twitter is now. People started using @ to refer to other users and # for topic tags, so the Twitter service incorporated those as features into their software.</p>
<p>I think the same will be true for Google Wave. It is a new tool, of which a use is yet to be defined.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on I want my A-Space by Canyon</title>
		<link>http://canyonr.com/2008/12/i-want-my-a-space/comment-page-1/#comment-37</link>
		<dc:creator>Canyon</dc:creator>
		<pubDate>Thu, 04 Dec 2008 04:58:40 +0000</pubDate>
		<guid isPermaLink="false">http://canyonr.com/?p=27#comment-37</guid>
		<description>Yes, that is correct. But I feel there are some details that are important in understanding the context.

1) &quot;Safe&quot; is a subjective term. Users might feel safe with a &quot;private&quot; page on Facebook or MySpace. Yet companies wouldn&#039;t feel &quot;safe&quot; with employees posting corporate info or discussing internal details on that same page. They would want a system that is controlled by their IT staff and therefor subject to the protections and controls they feel &quot;safe&quot; with. By extension, users will feel safer posting to the internal, officially sanctioned, site because they don&#039;t have fear of saying something sensitive in a public forum. There are still the political concerns around what is posted, but those exist in all corporate communications.

2) The exact function and format for the tools is, hopefully, up to the implementers but the A-Space product seems to have more features and capabilities than any other products currently available. I&#039;m really wishing out loud that someone will take the lack of such a product on the public market as an opportunity and attempt to fill that void. But as you say, it is just a starting point.</description>
		<content:encoded><![CDATA[<p>Yes, that is correct. But I feel there are some details that are important in understanding the context.</p>
<p>1) &#8220;Safe&#8221; is a subjective term. Users might feel safe with a &#8220;private&#8221; page on Facebook or MySpace. Yet companies wouldn&#8217;t feel &#8220;safe&#8221; with employees posting corporate info or discussing internal details on that same page. They would want a system that is controlled by their IT staff and therefor subject to the protections and controls they feel &#8220;safe&#8221; with. By extension, users will feel safer posting to the internal, officially sanctioned, site because they don&#8217;t have fear of saying something sensitive in a public forum. There are still the political concerns around what is posted, but those exist in all corporate communications.</p>
<p>2) The exact function and format for the tools is, hopefully, up to the implementers but the A-Space product seems to have more features and capabilities than any other products currently available. I&#8217;m really wishing out loud that someone will take the lack of such a product on the public market as an opportunity and attempt to fill that void. But as you say, it is just a starting point.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on I want my A-Space by kevincurry.blogspot.com/</title>
		<link>http://canyonr.com/2008/12/i-want-my-a-space/comment-page-1/#comment-36</link>
		<dc:creator>kevincurry.blogspot.com/</dc:creator>
		<pubDate>Thu, 04 Dec 2008 02:45:59 +0000</pubDate>
		<guid isPermaLink="false">http://canyonr.com/?p=27#comment-36</guid>
		<description>I think, Canyon, what you are arguing is that the solution is to reduce the problem to:  1) create a safe virtual space in which people can operate safely.  2)  deploy common collaboration and social networking tools in the space.  Do I have it about right?  I hope so because it seems a good starting point.</description>
		<content:encoded><![CDATA[<p>I think, Canyon, what you are arguing is that the solution is to reduce the problem to:  1) create a safe virtual space in which people can operate safely.  2)  deploy common collaboration and social networking tools in the space.  Do I have it about right?  I hope so because it seems a good starting point.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on I want my A-Space by Canyon</title>
		<link>http://canyonr.com/2008/12/i-want-my-a-space/comment-page-1/#comment-35</link>
		<dc:creator>Canyon</dc:creator>
		<pubDate>Wed, 03 Dec 2008 21:07:32 +0000</pubDate>
		<guid isPermaLink="false">http://canyonr.com/?p=27#comment-35</guid>
		<description>No, they shouldn&#039;t release schematics for at tank, but what I&#039;m talking about isn&#039;t the plans for a tank. I&#039;m talking about a software product that, while more advanced and full featured then other packages, doesn&#039;t bring any novel or unreproducible technology with it. The value that A-Space brings to the government is the content within it not any secret about how it was constructed. Releasing the code behind A-Space wouldn&#039;t reveal any classified secrets or even open up the government&#039;s internal A-Space to any possible attacks because it isn&#039;t accessible to the public. It might even make it more secure if an open review of the code reveals any potential problems that can then be fixed.

But more importantly, releasing the plans to a tank would only be useful to rival tank manufactures and those trying to discover weaknesses in the tank design. Releasing A-Space would be useful to any company or group who would benefit from a centralized social information sharing site, like mine and maybe even yours.</description>
		<content:encoded><![CDATA[<p>No, they shouldn&#8217;t release schematics for at tank, but what I&#8217;m talking about isn&#8217;t the plans for a tank. I&#8217;m talking about a software product that, while more advanced and full featured then other packages, doesn&#8217;t bring any novel or unreproducible technology with it. The value that A-Space brings to the government is the content within it not any secret about how it was constructed. Releasing the code behind A-Space wouldn&#8217;t reveal any classified secrets or even open up the government&#8217;s internal A-Space to any possible attacks because it isn&#8217;t accessible to the public. It might even make it more secure if an open review of the code reveals any potential problems that can then be fixed.</p>
<p>But more importantly, releasing the plans to a tank would only be useful to rival tank manufactures and those trying to discover weaknesses in the tank design. Releasing A-Space would be useful to any company or group who would benefit from a centralized social information sharing site, like mine and maybe even yours.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on I want my A-Space by thedrake000</title>
		<link>http://canyonr.com/2008/12/i-want-my-a-space/comment-page-1/#comment-34</link>
		<dc:creator>thedrake000</dc:creator>
		<pubDate>Wed, 03 Dec 2008 17:15:25 +0000</pubDate>
		<guid isPermaLink="false">http://canyonr.com/?p=27#comment-34</guid>
		<description>I understand the need to return taxpayer investment to citizens, but the logic here does not track.  Should the government release the information to make a tank?</description>
		<content:encoded><![CDATA[<p>I understand the need to return taxpayer investment to citizens, but the logic here does not track.  Should the government release the information to make a tank?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why go back to paper? by Kally</title>
		<link>http://canyonr.com/2007/11/why-go-back-to-paper/comment-page-1/#comment-33</link>
		<dc:creator>Kally</dc:creator>
		<pubDate>Wed, 09 Apr 2008 13:49:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.canyonr.com/2007/11/07/why-go-back-to-paper/#comment-33</guid>
		<description>I hope with the purchase of a better phone/organizer you can be re-inspired. I would also like to make a correction to this posting.  You wrote:  &quot;The palm accompanied me to the mall, camping, on job interviews, and even doing the laundry.&quot;
 **  I am not saying you don&#039;t help with the laundry but the last time you &quot;left to do/moniter laundry&quot; was at the 1st apartment we lived in. During this time you had the Newton. You aquired the Palm when we lived in the house on 9th Street (Remember when you left it at AMC Theaters right after you first got it?) where we had a washer and dryer in the home. We no longer had to leave to do laundry and since then laundry has been by my doing. Unless you are counting the time or two when our washing machine broke down at the house on 4th Place and you went to a laundry mat to do laundry.</description>
		<content:encoded><![CDATA[<p>I hope with the purchase of a better phone/organizer you can be re-inspired. I would also like to make a correction to this posting.  You wrote:  &#8220;The palm accompanied me to the mall, camping, on job interviews, and even doing the laundry.&#8221;<br />
 **  I am not saying you don&#8217;t help with the laundry but the last time you &#8220;left to do/moniter laundry&#8221; was at the 1st apartment we lived in. During this time you had the Newton. You aquired the Palm when we lived in the house on 9th Street (Remember when you left it at AMC Theaters right after you first got it?) where we had a washer and dryer in the home. We no longer had to leave to do laundry and since then laundry has been by my doing. Unless you are counting the time or two when our washing machine broke down at the house on 4th Place and you went to a laundry mat to do laundry.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
