<?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 First Waves</title>
	<atom:link href="http://firstwaves.org/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://firstwaves.org</link>
	<description>Examining Google+ as it Grows</description>
	<lastBuildDate>Thu, 14 Jul 2011 17:42:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>Comment on Google+ (or Google Plus if you wanna be search-engine friendly) by Zombie_Plan</title>
		<link>http://firstwaves.org/google-plus/#comment-129</link>
		<dc:creator>Zombie_Plan</dc:creator>
		<pubDate>Thu, 14 Jul 2011 17:42:00 +0000</pubDate>
		<guid isPermaLink="false">http://firstwaves.org/?p=229477777#comment-129</guid>
		<description>That will probably be the case, yeah.

However, what will happen with the dislike button? Will we be able to -1 things? In further thinking, maybe they&#039;ll add the ability to auto-post links to things you like on Google+</description>
		<content:encoded><![CDATA[<p>That will probably be the case, yeah.</p>
<p>However, what will happen with the dislike button? Will we be able to –1 things? In further thinking, maybe they’ll add the ability to auto-post links to things you like on Google+</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Google+ (or Google Plus if you wanna be search-engine friendly) by Screenbeard</title>
		<link>http://firstwaves.org/google-plus/#comment-128</link>
		<dc:creator>Screenbeard</dc:creator>
		<pubDate>Thu, 14 Jul 2011 10:54:00 +0000</pubDate>
		<guid isPermaLink="false">http://firstwaves.org/?p=229477777#comment-128</guid>
		<description>Thanks for pointing that out. it&#039;s not very obvious though, and I think eventually this will be integrated into Youtube to replace the like button.</description>
		<content:encoded><![CDATA[<p>Thanks for pointing that out. it’s not very obvious though, and I think eventually this will be integrated into Youtube to replace the like button.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Google+ (or Google Plus if you wanna be search-engine friendly) by Zombie_Plan</title>
		<link>http://firstwaves.org/google-plus/#comment-127</link>
		<dc:creator>Zombie_Plan</dc:creator>
		<pubDate>Wed, 13 Jul 2011 14:53:00 +0000</pubDate>
		<guid isPermaLink="false">http://firstwaves.org/?p=229477777#comment-127</guid>
		<description>There is actually already a +1 on Youtube. If you click the Share button, besides the Facebook and Twitter icons, the +1 is all &quot;HELLO CLICK ME&quot;.

Love the post, and I&#039;m really happy to see First Waves being all awesome. I look forward to everything you write.</description>
		<content:encoded><![CDATA[<p>There is actually already a +1 on Youtube. If you click the Share button, besides the Facebook and Twitter icons, the +1 is all “HELLO <span class="caps">CLICK</span> ME”.</p>
<p>Love the post, and I’m really happy to see First Waves being all awesome. I look forward to everything you write.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Google Wave Live and Available for Everyone! Including Google Apps users! by MR</title>
		<link>http://firstwaves.org/google-wave-live-and-available-for-everyone-including-google-apps-users/#comment-71</link>
		<dc:creator>MR</dc:creator>
		<pubDate>Wed, 20 Oct 2010 19:22:23 +0000</pubDate>
		<guid isPermaLink="false">http://firstwaves.org/?p=229477740#comment-71</guid>
		<description>I don&#039;t understand.&lt;br&gt;Will be close Wave or not?&lt;br&gt;</description>
		<content:encoded><![CDATA[<p>I don’t understand.<br />Will be close Wave or not?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Google Wave Live and Available for Everyone! Including Google Apps users! by MR</title>
		<link>http://firstwaves.org/google-wave-live-and-available-for-everyone-including-google-apps-users/#comment-126</link>
		<dc:creator>MR</dc:creator>
		<pubDate>Wed, 20 Oct 2010 14:22:00 +0000</pubDate>
		<guid isPermaLink="false">http://firstwaves.org/?p=229477740#comment-126</guid>
		<description>I don&#039;t understand.
Will be close Wave or not?
</description>
		<content:encoded><![CDATA[<p>I don’t understand.<br />
Will be close Wave or not?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Wave This API released. Plus Official Chrome Extension and Bonus Unofficial WordPress Widget by Tweets that mention First Waves » Wave This API released. Plus Official Chrome Extension and Bonus Unofficial Wordpress Widget -- Topsy.com</title>
		<link>http://firstwaves.org/wave-this-api-released-plus-official-chrome-extension-and-bonus-unofficial-wordpress-widget/#comment-70</link>
		<dc:creator>Tweets that mention First Waves » Wave This API released. Plus Official Chrome Extension and Bonus Unofficial Wordpress Widget -- Topsy.com</dc:creator>
		<pubDate>Wed, 19 May 2010 21:34:23 +0000</pubDate>
		<guid isPermaLink="false">http://firstwaves.org/?p=229477737#comment-70</guid>
		<description>[...] This post was mentioned on Twitter by Russell Tripp, Joshua Nunn. Joshua Nunn said: FW Post: Wave This &lt;span class=&quot;caps&quot;&gt;API&lt;/span&gt; released. Plus Official Chrome Extension and Bonus Unofficial Wordp... http://e01.li/9KzVDj [...]</description>
		<content:encoded><![CDATA[<p>[…] This post was mentioned on Twitter by Russell Tripp, Joshua Nunn. Joshua Nunn said: FW Post: Wave This &lt;span class=“caps”&gt;API&lt;/span&gt; released. Plus Official Chrome Extension and Bonus Unofficial Wordp… <a href="http://e01.li/9KzVDj" rel="nofollow">http://e01.li/9KzVDj</a> […]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Google Wave Available to 31000 University Students by Testing Google Wave for Apps &#8212; Mastering WAVE</title>
		<link>http://firstwaves.org/google-wave-for-apps-being-rolled-out-to-some-organisations/#comment-39</link>
		<dc:creator>Testing Google Wave for Apps &#8212; Mastering WAVE</dc:creator>
		<pubDate>Tue, 18 May 2010 17:57:35 +0000</pubDate>
		<guid isPermaLink="false">http://firstwaves.org/?p=229477531#comment-39</guid>
		<description>[...] Waves has already covered some of the functionality at with their post Google Wave Available to 31000 University Students. Where they talk about a university using Wave and show some [...]</description>
		<content:encoded><![CDATA[<p>[…] Waves has already covered some of the functionality at with their post Google Wave Available to 31000 University Students. Where they talk about a university using Wave and show some […]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Remove: Remove Yourself! Remove Others! by joshnunn</title>
		<link>http://firstwaves.org/remove-remove-yourself-remove-others/#comment-68</link>
		<dc:creator>joshnunn</dc:creator>
		<pubDate>Fri, 07 May 2010 05:35:28 +0000</pubDate>
		<guid isPermaLink="false">http://firstwaves.org/?p=229477709#comment-68</guid>
		<description>It really is a good time to get back into Wave. With Google I/O coming up, they&#039;re on a new feature spree at the moment, and it&#039;s only going to get better. There are probably a couple of posts I could write about why now is a great time to get back into Wave. The Wave Watchers (a group of wave enthusiasts and developers) are putting together a comprehensive post of this nature as we speak! &lt;br&gt;&lt;br&gt;As for your security concerns, I think it&#039;s right to be somewhat wary. It&#039;s new technology and a new idea, and it may very well have fundamental flaws in the way it&#039;s currently implemented. It is however, only a &quot;preview&quot; still, and anyone using it for top-secret sensitive data does so at their own risk. The way to minimise your risk is to not use gadgets that have not been thoroughly vetted (the source is always easily available) or not use them at all, and only invite users that you trust.</description>
		<content:encoded><![CDATA[<p>It really is a good time to get back into Wave. With Google I/O coming up, they’re on a new feature spree at the moment, and it’s only going to get better. There are probably a couple of posts I could write about why now is a great time to get back into Wave. The Wave Watchers (a group of wave enthusiasts and developers) are putting together a comprehensive post of this nature as we speak! </p>
<p>As for your security concerns, I think it’s right to be somewhat wary. It’s new technology and a new idea, and it may very well have fundamental flaws in the way it’s currently implemented. It is however, only a “preview” still, and anyone using it for top-secret sensitive data does so at their own risk. The way to minimise your risk is to not use gadgets that have not been thoroughly vetted (the source is always easily available) or not use them at all, and only invite users that you trust.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Remove: Remove Yourself! Remove Others! by Tobias</title>
		<link>http://firstwaves.org/remove-remove-yourself-remove-others/#comment-67</link>
		<dc:creator>Tobias</dc:creator>
		<pubDate>Fri, 07 May 2010 04:37:36 +0000</pubDate>
		<guid isPermaLink="false">http://firstwaves.org/?p=229477709#comment-67</guid>
		<description>Hey Josh, I followed your link from LifeHacker about your standup desk and you linked to this blog.&lt;br&gt;&lt;br&gt;I got in on Google Wave a while back now (I think it was the second big wave of invites) and did quite a bit of poking around and analysis of security measures and so on. In the end I decided that I probably wouldn&#039;t use Google&#039;s implementation of the Wave protocol due to the problem you mentioned at the end of this post: Wave abuse.&lt;br&gt;&lt;br&gt;I think that fundamentally the Wave protocol has a security &quot;issue&quot;. Not a bug, not necessarily a flaw, but it has several things that make me uncomfortable with it. I wrote more about it on my research blag: &lt;a href=&quot;http://www.tobiaslabs.com/59/some-security-issues-with-google-wave/&quot; rel=&quot;nofollow&quot;&gt;http://www.tobiaslabs.com/59/some-security-issu...&lt;/a&gt;&lt;br&gt;&lt;br&gt;I link to a support forum where a person argued that the &quot;Remove&quot; function of the Wave protocol may not even &quot;make sense&quot;, but I think Google&#039;s implementation on this is pretty reasonable. I think I&#039;ll start using Google Wave again to see how I like the recent changes.</description>
		<content:encoded><![CDATA[<p>Hey Josh, I followed your link from LifeHacker about your standup desk and you linked to this blog.</p>
<p>I got in on Google Wave a while back now (I think it was the second big wave of invites) and did quite a bit of poking around and analysis of security measures and so on. In the end I decided that I probably wouldn’t use Google’s implementation of the Wave protocol due to the problem you mentioned at the end of this post: Wave abuse.</p>
<p>I think that fundamentally the Wave protocol has a security “issue”. Not a bug, not necessarily a flaw, but it has several things that make me uncomfortable with it. I wrote more about it on my research blag: <a href="http://www.tobiaslabs.com/59/some-security-issues-with-google-wave/" rel="nofollow">http://www.tobiaslabs.com/59/some-security-issu…</a></p>
<p>I link to a support forum where a person argued that the “Remove” function of the Wave protocol may not even “make sense”, but I think Google’s implementation on this is pretty reasonable. I think I’ll start using Google Wave again to see how I like the recent changes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Remove: Remove Yourself! Remove Others! by Screenbeard</title>
		<link>http://firstwaves.org/remove-remove-yourself-remove-others/#comment-125</link>
		<dc:creator>Screenbeard</dc:creator>
		<pubDate>Fri, 07 May 2010 00:35:00 +0000</pubDate>
		<guid isPermaLink="false">http://firstwaves.org/?p=229477709#comment-125</guid>
		<description>It really is a good time to get back into Wave. With Google I/O coming up, they&#039;re on a new feature spree at the moment, and it&#039;s only going to get better. There are probably a couple of posts I could write about why now is a great time to get back into Wave. The Wave Watchers (a group of wave enthusiasts and developers) are putting together a comprehensive post of this nature as we speak! 

As for your security concerns, I think it&#039;s right to be somewhat wary. It&#039;s new technology and a new idea, and it may very well have fundamental flaws in the way it&#039;s currently implemented. It is however, only a &quot;preview&quot; still, and anyone using it for top-secret sensitive data does so at their own risk. The way to minimise your risk is to not use gadgets that have not been thoroughly vetted (the source is always easily available) or not use them at all, and only invite users that you trust. </description>
		<content:encoded><![CDATA[<p>It really is a good time to get back into Wave. With Google I/O coming up, they’re on a new feature spree at the moment, and it’s only going to get better. There are probably a couple of posts I could write about why now is a great time to get back into Wave. The Wave Watchers (a group of wave enthusiasts and developers) are putting together a comprehensive post of this nature as we speak! </p>
<p>As for your security concerns, I think it’s right to be somewhat wary. It’s new technology and a new idea, and it may very well have fundamental flaws in the way it’s currently implemented. It is however, only a “preview” still, and anyone using it for top-secret sensitive data does so at their own risk. The way to minimise your risk is to not use gadgets that have not been thoroughly vetted (the source is always easily available) or not use them at all, and only invite users that you trust. </p>
]]></content:encoded>
	</item>
</channel>
</rss>

