<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" 
      xmlns:thr="http://purl.org/syndication/thread/1.0">
  <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php" />
  <link rel="self" type="application/atom+xml" href="http://www.readwriteweb.com/atom.xml" />
  <id>tag:,2009:/1/tag:www.readwriteweb.com,2009://1.15237-</id>
  <updated>2009-11-22T22:50:35Z</updated>
  <title>Comments for Google Wave: Our First Hands-On Impressions</title>
  
  <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.23-en</generator>
  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237</id>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.readwriteweb.com/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=15237" title="Google Wave: Our First Hands-On Impressions" />
    <published>2009-06-03T04:48:21Z</published>
    <updated>2009-06-03T19:57:29Z</updated>
    <title>Google Wave: Our First Hands-On Impressions</title>
    <summary>Google Wave: Our First Hands-On Impressions
</summary>
    <author>
      <name>Frederic Lardinois</name>
      
    </author>
    
    <category term="Features" />
    
    <category term="Google" />
    
    <category term="NYT" />
    
    <category term="Products" />
    
    <content type="html" xml:lang="en" xml:base="http://www.readwriteweb.com/">
      <![CDATA[<p><img alt="google_wave_logo_jun09.png" src="http://www.readwriteweb.com/images/google_wave_logo_jun09.png"  />When <a href="http://wave.google.com/">Google Wave</a> made its <a href="http://www.readwriteweb.com/archives/google_wave_google_tries_to_reinvent_email.php">public debut</a> last week, it created quite a stir, but without being able to get a hands-on look at the product, it was quite hard to really grasp the implications of what Google was trying to do. Today, we got access to Wave, and after testing it for a while, we can confidently say that Google is indeed on to something. The developer sandbox version we have access to is still a bit rough around the edges, and quite a few functions are still unavailable.</p>]]>
      <![CDATA[<h2>Just a Preview - Lots More to Come</h2>

<p>During our test this afternoon, we also got to chat with Jens and Lars Rasmussen, who gave the first official demo last week. They stressed that the team is currently fully focused on getting the developer preview for third-party developers right, so everything we say here about the UI is still in flux and will definitely change before the final release.</p>

<p><img alt="google_wave_large_first_impressions.jpg" src="http://www.readwriteweb.com/images/google_wave_large_first_impressions.jpg"  /></p>

<p>Chances are that you have already seen <a href="http://www.cnet.com.au/google-wave-screenshots-339296698.htm">some screenshots</a> or <a href="http://www.youtube.com/watch?v=v_UyVmITiYQ">seen the demo on YouTube</a> (more than 1.5 million people have seen it already), but here is a <a href="http://www.screencast.com/t/jjGLQxkvDs4">short video</a> of what a wave looks like in action.</p>

<h2>What is Wave?</h2>

<p>One thing we immediately noticed is that it takes a little bit to get used to how Wave works. The first thing new users will probably notice is that Wave always shows you exactly what your contacts are typing in real-time (if you ever used the talk command in UNIX, you know what this feels like). Even when adding a map, you can see how someone scrolls around it to mark a spot, for example. After using it for a while, we have come to think as Wave as real-time email with a big dose of IM built-in, but even this only just describes a small part of what Wave can do.</p>

<h2>Giving it a Spin</h2>

<p>As you have probably seen in the videos and screenshots, Wave features a sidebar on the left and two large columns on the right. Overall, the look (but not the functionality) is somewhat reminiscent of the layout you would expect from an email client or a three-pane feed reader.</p>

<p><img alt="google_wave_embed_google_jun09.png" align="right" src="http://www.readwriteweb.com/images/google_wave_embed_google_jun09.png"  />The sidebar features the functions for navigation, as well as your contacts. The larger column on the left is basically your inbox. By default, this column shows recently active conversations, or, depending on what you want to look at, a history of archived waves, waves marked as spam (there is, of course, no spam on Wave yet), or all the waves initiated by you.</p>

<p>The most interesting column, though, is the one on the right, because this is where you type your messages. Here, you can initiate new messages and waves, but you can also easily respond to messages, add new contacts to a wave, and send private messages to select users. One nice feature is that you can pick a specific word or phrase and respond to that, instead of the whole message.</p>

<h2>Doing the Wave</h2>

<p>As you are typing a message, a number of new icons appear at the top of the column. Currently, the most interesting one here is the Google widget, which allows you to very easily search Google and add a link to the wave. You can also search YouTube and Google Images and embed videos and pictures with just one click. The Wave team will surely expand these offerings (there is already a link to search Google Books, though it is currently not active, yet). Another option here is to embed a map that you can extend by setting place markers and drawing lines.</p>

<p>To add a picture or any other kind of file to a wave, you just have to drag and drop it onto a wave from your desktop. Wave also features a nice, <a href="http://en.wikipedia.org/wiki/Lightbox_(JavaScript)">lightbox</a>-style photo viewer that allows you to browse through all the images in a wave.</p>

<p>In the long term, all of these functions will be expanded by third-party developers who will probably come up with exciting new ways to make use of Wave. Given that the open APIs will allow developers to take Wave into new directions, and also implement its functionality in other places, we are very excited to hear that the team will open up Wave to more developers later this week. </p>

<p><img alt="card_wave_jun09.jpg" src="http://www.readwriteweb.com/images/card_wave_jun09.jpg"  /></p>

<p>According to the Rasmussen brothers, only a small number of third-party developers have access to Google Wave at this point. However, by the end of the week, this number should go up to almost 2000 - and judging from what we have heard and <a href="http://lists.wikimedia.org/pipermail/foundation-l/2009-May/052160.html">read</a>, there is a lot of interest in the developer community and we will definitely see a lot of activity in this area in the next few months.</p>

<h2>Not just Real-Time Chat</h2>

<p>It should also be noted that the real-time chat is really only one aspect of Wave. There is no reason why the chat couldn't be used as an internal micro-blogging tool, for example. As Jens Rasmussen pointed out to us, it is this mix of uses in different scenarios that may be the most exciting aspect of Wave. While the real-time aspects of Wave are currently at the forefront of what people have been excited about, there is no reason why users couldn't use it as a replacement for regular email as well - or why they couldn't switch from one mode to another at will.</p>

<h2>A Few More Thoughts</h2>

<blockquote><img alt="google_wave_navigation_jun09.png" align="right" src="http://www.readwriteweb.com/images/google_wave_navigation_jun09.png"/><ul>
  <li>Presence will be indicated by a green dot on users' avatars - very much like IM. </li>

  <li>One thing that got to us was that hitting the Enter key will just give you a new line, but to finish a message, you have to hit Shift+Enter, which takes a bit of getting used to. </li>

  <li>At this point, long waves with a lot of concurrent users can get a bit confusing. While the messages are timestamped, it would be great if there were some stronger visual clues as to which messages are new. You can easily get to new messages by hitting the space bar, but even then, sometimes it is still a bit hard to see what messages you are actually looking at. </li>

  <li>Unlike Gmail, Wave actually features traditional folders and you can filter out messages by keywords. In addition, you can also tag waves. </li>

  <li>It would be nice if you could turn the real-time aspect of Wave off and only have your messages appear in a Wave after it was completed. </li>

  <li>The playback function that was prominently featured in the demo last week is interesting, but we are not sure how useful it will be in daily use. </li>

  <li>Currently, the automatic spell-checker on Wave is offline, so we couldn't test it, but we'll update this post once it works again. </li>

  <li>We tested Wave in Firefox, Chrome, Safari, and Internet Explorer - as expected, it didn't work in IE but worked perfectly fine in all the other browsers. </li>
</ul>
</blockquote>
<h2>Will Wave Revolutionize EMail?</h2>

<p>The big question on everybody's mind, though, is if Google and the Wave team can hold true to their promise of 'reinventing email for the 21st century.' What we have seen so far is only the tip of the iceberg, but we can already envision how this could replace our internal chat room here at RWW, and how it could revolutionize the way employees in a company communicate. Wave definitely takes some getting used to, but once you get into the flow of things, regular email suddenly feels stale and slow. </p>

<p>Like any great tool, Wave gives its users a lot of flexibility and never gets in your way. If you want a Wave to look more like a document instead of a conversation, Wave will work just as well as when you just want to use it as a chat room.</p>

<p>It's still too early to argue about whether Wave can or will ever replace email (it's only a developer preview at this point after all). However, after using it for a while we were already wishing that we could add more of our contacts to our list so that it could become our default messaging system. Until then, though, we are back to Gmail and IM.</p>
<center>
  <p><object width="560" height="340"><param name="movie" value="http://www.youtube.com/v/v_UyVmITiYQ&hl=en&fs=1"></param><param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src="http://www.youtube.com/v/v_UyVmITiYQ&hl=en&fs=1" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="560" height="340"></embed></object></p>
</center>]]>
    </content>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:140688</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c140688" />
    <title>Comment from Niklas on 2009-06-02</title>
    <author>
        <name>Niklas</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>They don't mention a trust model in the demo. I find it hard to believe that they are going to reinvent email without fixing spam.</p>]]>
    </content>
    <published>2009-06-03T05:42:29Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:140690</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c140690" />
    <title>Comment from Jean-Michel Decombe on 2009-06-02</title>
    <author>
        <name>Jean-Michel Decombe</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>To better understand Google Wave, people have to think of waves as collaborative activities, rather than trying to compare them to emails and instant messages. Thus, Google Wave is not reinventing email or instant messaging, but rather integrating their functionality into a larger concept that will eventually render them obsolete on their own, especially since it is entirely possible to use a wave simply as a thread of emails or instant messages.</p>

<p>Google Wave is the closest that anyone had designed so far to replicate, in digital form, the process of collaborating in analog form. When you go about your day, you do not put yourself in a "talking" mode, then in a "writing a letter" mode or "sharing a document" mode, and so forth. You just mix these modes seamlessly, usually while focused on a single activity, e.g. making progress on project XYZ. You can also juggle business and personal activities at the same time, in which case you would have multiple waves open and dynamically updated, in the digital realm.</p>

<p>What is exciting is that people will develop wave extensions that will be editors and viewers for all sorts of content (graphs, charts, spreadsheets, presentations, playlists, photos, etc.), so you will hardly ever need to work outside of Google Wave, as it will be a great framework for many of your digital activities. If you are a practitioner, for instance, you could have one wave per client or project.</p>

<p>So Google Wave might well be an important milestone in the race to make the browser the "operating system" (loosely defined, mostly from the user's perspective) and moving more developers away from designing native applications (except for the core ones) in favor of wave extensions.</p>]]>
    </content>
    <published>2009-06-03T05:54:20Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:140692</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c140692" />
    <title>Comment from Jean-Michel Decombe on 2009-06-02</title>
    <author>
        <name>Jean-Michel Decombe</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>And, yes indeed, they still have a lot of work to do before all the important aspects of a good design are  fully in place (trust, security, privacy, integrity, performance, scalability, and so forth), but that should eventually happen, especially with the resources that they have at their disposal at Google. There are not many companies where that could happen.</p>]]>
    </content>
    <published>2009-06-03T05:57:45Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:140693</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c140693" />
    <title>Comment from Marc van Wijk on 2009-06-02</title>
    <author>
        <name>Marc van Wijk</name>
        <uri>http://www.crystalvisions.nl</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.crystalvisions.nl">
        <![CDATA[<p>What I'd like to know is: is there any way of communicating from Wave with users with regular e-mail? <br />
It will only truly "replace" e-mail if everyone uses it. As long as you have contacts that still rely on e-mail, you'd just have one more app to use next to your e-mail client, IM tool etc.</p>]]>
    </content>
    <published>2009-06-03T06:09:22Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:140694</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c140694" />
    <title>Comment from Jose on 2009-06-02</title>
    <author>
        <name>Jose</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>According to a tweet from Forrester's @jowyang, many of Wave's features are already available in many enterprise-level collaboration solutions. However, it's obvious that the real power behind Wave relies on its APIs. </p>

<p>If Wave and it's developer community manage to deliver on its promise of streamlining the way that people communicate online, it could become one sort of communications hub for people. It's not hard to picture a scenario where people use Google Wave with a series of gadgets that integrate communications from facebook to twitter and aggregates them in one single place into different waves. In esence, wave could help blur the barriers between different applications and coversations living in different places.</p>

<p>Finally, I think Google Wave may progress the social web into more advanced stages of evolution. For example, now shopping could really be social. It would be a matter of creating a wave, inviting some friends, pulling shopping items from different websites via some gadget, discuss with your friends what to buy, and checking out using some payment-processign gadget (paypal, google checkout, etc). </p>]]>
    </content>
    <published>2009-06-03T06:10:27Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:140703</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c140703" />
    <title>Comment from Mahesh CR on 2009-06-02</title>
    <author>
        <name>Mahesh CR</name>
        <uri>http://friendfeed.com/maheshcr</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://friendfeed.com/maheshcr">
        <![CDATA[<p>To view Google Wave as the next gen email/im/current crop of communication tools is to miss the point. </p>

<p>Wave is a collaboration substrate for the Internet. A standardized set of protocols and code assets for applications to collaborate. The specific examples provided are almost incidental and help sell the Wave vision and perhaps gain traction initially. </p>

<p>The key innovations of Wave for internet scale collaboration are i) Wave protocol, which is based on XMPP, and provides the real-time nature of this beast ii) XML based document notion, provides a serializable data structure for capturing state of a collaboration effort and iii) Wave operational transforms, that encodes changes to the XML state as a set of XML messages which in turn can be federated with participants in the Wave. </p>

<p>@Jean-Michel I second your thoughts!</p>]]>
    </content>
    <published>2009-06-03T06:34:45Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:140714</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c140714" />
    <title>Comment from Todd Hoff on 2009-06-02</title>
    <author>
        <name>Todd Hoff</name>
        <uri>http://friendfeed.com/toddh</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://friendfeed.com/toddh">
        <![CDATA[<p>Do we have a collaboration problem? Do we not collaborate pretty well on FF, FB, Twitter?</p>]]>
    </content>
    <published>2009-06-03T06:37:12Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:140715</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c140715" />
    <title>Comment from Jason Nunnelley on 2009-06-02</title>
    <author>
        <name>Jason Nunnelley</name>
        <uri>http://friendfeed.com/jasonn</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://friendfeed.com/jasonn">
        <![CDATA[<p>Google's Wave is just integrated with the Google space. Another, doesn't have to be the only.</p>]]>
    </content>
    <published>2009-06-03T06:39:48Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:140707</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c140707" />
    <title>Comment from James: Lowes Home Improvement on 2009-06-02</title>
    <author>
        <name>James: Lowes Home Improvement</name>
        <uri>http://www.lowes-home-improvement.com/</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.lowes-home-improvement.com/">
        <![CDATA[<p>Hi, nice post. I have been wondering about this issue,so thanks for sharing. I’ll definitely be subscribing to your posts. Keep up the good work<br />
</p>]]>
    </content>
    <published>2009-06-03T06:39:57Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:140716</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c140716" />
    <title>Comment from Frederic on 2009-06-02</title>
    <author>
        <name>Frederic</name>
        <uri>http://friendfeed.com/frederic</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://friendfeed.com/frederic">
        <![CDATA[<p>Mahes - I agree - there is a lot of interesting stuff going on when it comes to Wave's back-end. I was just looking at what a user can expect from it at this point. We'll cover the developer features in more depth once more developers get access to it and once we get a chance to talk to developers and see how they want to use it.</p>]]>
    </content>
    <published>2009-06-03T06:47:18Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:140710</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c140710" />
    <title>Comment from alex on 2009-06-02</title>
    <author>
        <name>alex</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>"It would be nice if you could turn the real-time aspect of Wave off and only have your messages appear in a Wave after it was completed. "</p>

<p>watch the video again... this option already exists...</p>]]>
    </content>
    <published>2009-06-03T06:59:43Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:140717</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c140717" />
    <title>Comment from invariant on 2009-06-03</title>
    <author>
        <name>invariant</name>
        <uri>http://friendfeed.com/invariant</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://friendfeed.com/invariant">
        <![CDATA[<p>What Wave does is make it easier for other developers to make their web apps work in real time.  The demos they show make the case for the real time web being useful.  FF is ahead of the game, but soon a web app that isn't doing real time will feel as dated as one that doesn't use AJAX today.  Much like AJAX, that can be a good and bad thing.</p>]]>
    </content>
    <published>2009-06-03T07:04:55Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:140712</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c140712" />
    <title>Comment from Internet Fax Reviews on 2009-06-03</title>
    <author>
        <name>Internet Fax Reviews</name>
        <uri>http://onlinefaxreviews.net/</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://onlinefaxreviews.net/">
        <![CDATA[<p>I think that Google is really making the way for innovation and other sites will follow. They were able to bring down Yahoo.</p>]]>
    </content>
    <published>2009-06-03T07:07:02Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:140713</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c140713" />
    <title>Comment from MacStories on 2009-06-03</title>
    <author>
        <name>MacStories</name>
        <uri>http://www.macstories.net/</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.macstories.net/">
        <![CDATA[<p>There's no doubt Google Wave is really cool and innovative, but I don't believe it will replace email.</p>

<p>The reason is simple: the coolest thing of regular emails is that, once sent, you can decide to answer after 2 minutes or after 2 days. <br />
As long as there will be people that use Gmail (or people that log into their inbox 30 minutes a day), Wave won't totally revolutionize the market, but it only offer a better chance to the people that decide to try it.</p>

<p>Speaking as an Italian, there's a lot of people here that still don't use email (you may say "what????") so maybe Wave should be a great opportunity for them..I don't know, let's see how Google will present this product.</p>]]>
    </content>
    <published>2009-06-03T07:08:07Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:140718</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c140718" />
    <title>Comment from Rahul Deodhar on 2009-06-03</title>
    <author>
        <name>Rahul Deodhar</name>
        <uri>http://friendfeed.com/rahuldeodhar</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://friendfeed.com/rahuldeodhar">
        <![CDATA[<p>Will it threaten microsoft Outlook and Lotus notes "corporate" dominance? Particularly given its "federation" architecture aiding privacy and IPR protection</p>]]>
    </content>
    <published>2009-06-03T07:15:13Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:140719</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c140719" />
    <title>Comment from Oopdate on 2009-06-03</title>
    <author>
        <name>Oopdate</name>
        <uri>http://www.oopdate.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.oopdate.com">
        <![CDATA[<p>I don't want you can see what I'm typing in realtime :))) Hope this can be turned off like in IM</p>]]>
    </content>
    <published>2009-06-03T07:38:22Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:140722</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c140722" />
    <title>Comment from Priyanka  on 2009-06-03</title>
    <author>
        <name>Priyanka </name>
        <uri>http://www.priyankawriting.blogspot.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.priyankawriting.blogspot.com">
        <![CDATA[<p><br />
"expectedly it doesn't work on IE" :D</p>]]>
    </content>
    <published>2009-06-03T07:55:51Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:140724</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c140724" />
    <title>Comment from Musashi on 2009-06-03</title>
    <author>
        <name>Musashi</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>I really do hope that they build security in from the beginning instead of viewing it as an hacked add-on after the fact.</p>

<p>Security by default (SSL and encrypted storage) would be really nice and would automatically avoid a lot of the security holes inherent in our current Email and IM systems. </p>]]>
    </content>
    <published>2009-06-03T08:19:31Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:140731</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c140731" />
    <title>Comment from Ben Werdmuller on 2009-06-03</title>
    <author>
        <name>Ben Werdmuller</name>
        <uri>http://benwerd.com/</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://benwerd.com/">
        <![CDATA[<p>I really do think the email comparison thing is a red herring here. As someone alluded to above, Wave is a collaboration infrastructure for the Internet. I see it being very good at being an intranet, virtual learning environment and group sharing space generally; not so good for the kinds of one-on-one messages we use email for.</p>

<p>In fact, I'd even go so far as to say - corporate policy issues aside - that Wave is Google's Sharepoint killer.</p>]]>
    </content>
    <published>2009-06-03T09:52:24Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:140734</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c140734" />
    <title>Comment from Spencer Spellman on 2009-06-03</title>
    <author>
        <name>Spencer Spellman</name>
        <uri>http://www.writtenbysumer.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.writtenbysumer.com">
        <![CDATA[<p>I've heard the same responses from several developers, that it's still has some bug and kinks to work out, but that the potential is pretty big with Wave from first indications. Whether it reinvents email or not, is yet to be seen. I don't think Google has to do that, because even if it doesn't, it at least changes how people communicate in different ways. Google is definitely onto something big here.</p>]]>
    </content>
    <published>2009-06-03T11:14:10Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:140743</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c140743" />
    <title>Comment from MMO Pinoy on 2009-06-03</title>
    <author>
        <name>MMO Pinoy</name>
        <uri>http://mmo.juanderpulpinoy.com/</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://mmo.juanderpulpinoy.com/">
        <![CDATA[<p>I'm excited for Google Wave!</p>]]>
    </content>
    <published>2009-06-03T12:42:31Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:140745</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c140745" />
    <title>Comment from Website Services on 2009-06-03</title>
    <author>
        <name>Website Services</name>
        <uri>http://www.shapia.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.shapia.com">
        <![CDATA[<p>I am sure, Google Wave will change the way people interact in an organisation.Way to go, Brin and Page...</p>]]>
    </content>
    <published>2009-06-03T13:01:58Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:140749</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c140749" />
    <title>Comment from Maggie Leber on 2009-06-03</title>
    <author>
        <name>Maggie Leber</name>
        <uri>http://www.twitter.com/maggiel</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.twitter.com/maggiel">
        <![CDATA[<p>I seem to recall in the demo there was a "draft" mode where your blip would not appear until you manually published it.</p>]]>
    </content>
    <published>2009-06-03T13:38:46Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:140753</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c140753" />
    <title>Comment from Paul on 2009-06-03</title>
    <author>
        <name>Paul</name>
        <uri>http://paulmwatson.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://paulmwatson.com">
        <![CDATA[<p>How is addressing handled? Does every Wave user you want to "wave with" have to have a Wave ID of some sort? Is it an email? What happens when you wave someone who doesn't have wave, do they get an email that kicks it off?</p>

<p>And how do Wave URLs work? If I want to link between two Waves or link to a Wave from a normal HTML page how do I do that?</p>]]>
    </content>
    <published>2009-06-03T15:32:49Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:140758</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c140758" />
    <title>Comment from Matt on 2009-06-03</title>
    <author>
        <name>Matt</name>
        <uri>http://pressplaysolutions.com/</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://pressplaysolutions.com/">
        <![CDATA[<p>Google Wave really does seem to be onto something. I wonder if Google will just fold in their other apps into the Wave when this thing is truly ready. The other thing I have to wonder is how this is going to be successful in business environments if so many still use IE.</p>]]>
    </content>
    <published>2009-06-03T16:00:16Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:140761</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c140761" />
    <title>Comment from Michael on 2009-06-03</title>
    <author>
        <name>Michael</name>
        <uri>http://friendfeed.com/sull</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://friendfeed.com/sull">
        <![CDATA[<p>i envision waves getting embedded inside of email message body and via gmail users can interact with the wave as they would if it were embedded on a web page.  if not gmail... such as outlook or any email client that doesnt support wave embeds, a gracefull fallback to a link to view the wave permalink.  </p>

<p>a wave inside emails inside gmail could let users remain with their current familiar workflow while still benefitting from all that wave has to offer.  the wave could be organized as any other email.  the email could optionally be bolded as unread when new activity occurrs in the wave, for example.  <br />
the wave could be forwarded to others etc.  </p>

<p>so if wave is not an email replacement, in this context, it certainly could be an email enhancement... or at least a gmail enhancement.</p>

<p>@sull</p>]]>
    </content>
    <published>2009-06-03T16:45:55Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:140781</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c140781" />
    <title>Comment from Zen Anon on 2009-06-03</title>
    <author>
        <name>Zen Anon</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>Correct me if I'm wrong, but I believe that in the keynote they mentioned being able to turn of the real-time typing.  Perhaps it hasn't been implemented yet.</p>]]>
    </content>
    <published>2009-06-03T18:50:12Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:140827</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c140827" />
    <title>Comment from Dmitry on 2009-06-03</title>
    <author>
        <name>Dmitry</name>
        <uri>http://www.waytorussia.net</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.waytorussia.net">
        <![CDATA[<p>I'd love to have a possibility to select a part of the text I'm reading, send it to the wave for immediate discussion.</p>]]>
    </content>
    <published>2009-06-03T22:14:39Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:140853</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c140853" />
    <title>Comment from Logical Extremes on 2009-06-03</title>
    <author>
        <name>Logical Extremes</name>
        <uri>http://friendfeed.com/logicalextremes</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://friendfeed.com/logicalextremes">
        <![CDATA[<p>Two key client features that will be needed for mainstream adoption are handling mutliple accounts and POP-like local access. I've written more about these here: <a href="http://logicalextremes.blogspot.com/2009/06/2-essential-features-for-google-wave.html" rel="nofollow">http://logicalextremes.blogspot.com/2009/06/2-essential-features-for-google-wave.html</a></p>]]>
    </content>
    <published>2009-06-04T03:07:58Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:141047</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c141047" />
    <title>Comment from nvee on 2009-06-05</title>
    <author>
        <name>nvee</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>What happens when Google Wave is hit by Spam in real-time - Its a tsunami!!!:-)) </p>]]>
    </content>
    <published>2009-06-05T08:24:31Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:141164</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c141164" />
    <title>Comment from Yann on 2009-06-05</title>
    <author>
        <name>Yann</name>
        <uri>http://minimaldesign.net/</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://minimaldesign.net/">
        <![CDATA[<p>Spam is probably not an issue. I didn't look at the tech behind Wave, but I'm assuming it's not built on email protocols... ;) atually, it's probably one of the main reason why Wave *will* replace email in the long run.</p>]]>
    </content>
    <published>2009-06-06T00:41:28Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:141176</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c141176" />
    <title>Comment from Jason Nunnelley on 2009-06-05</title>
    <author>
        <name>Jason Nunnelley</name>
        <uri>http://friendfeed.com/jasonn</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://friendfeed.com/jasonn">
        <![CDATA[<p>@rahuldeodhar I seriously doubt Wave will take market share from Outlook and Exchange for the big corporate space. It's a data ownership issue. They may adopt cloud or hosted solutions, but they'll be the last, very last people to do so. Plus, Outlook and Exchange fit the corporate environment very well, it's extremely integrated where it's dominant. Talk to some big law firms and see how entrenched those products and services are today.</p>]]>
    </content>
    <published>2009-06-06T02:23:45Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:141427</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c141427" />
    <title>Comment from Nils Östergren on 2009-06-08</title>
    <author>
        <name>Nils Östergren</name>
        <uri>http://www.nilsostergren.se</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.nilsostergren.se">
        <![CDATA[<p>Where will the ads be displayed?</p>]]>
    </content>
    <published>2009-06-08T10:07:18Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:141491</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c141491" />
    <title>Comment from it&apos;s a protocol on 2009-06-08</title>
    <author>
        <name>it&apos;s a protocol</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>Wave is also a protocol and an opensource server</p>

<p>everyone will be able to create his/her own server, his own client and use it on a private network or on internet like a typical smtp server (federation of servers)</p>

<p>or to use the opensource server from google to start</p>

<p>in fact, nothing will tie you to google servers and web interface google. You could use the google wave.com , like you use the gmail.com  or not.</p>

<p><br />
in fact, wave is like a total replacement of smtp/imap.</p>]]>
    </content>
    <published>2009-06-08T16:29:23Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:141511</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c141511" />
    <title>Comment from accent furniture on 2009-06-08</title>
    <author>
        <name>accent furniture</name>
        <uri>http://www.theaccentfurniture.com/</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.theaccentfurniture.com/">
        <![CDATA[<p>Google Wave is a communication protocol that supports communication in the form of E-Mail, Forum Discussion, Social Networking, Micro Blogging, Video Sharing, Photo Sharing, Chatting and Application Sharing amongst software (server and client apps).</p>

<p>On top of the communication protocol, they will make a easier to imagine product "Goolge Wave" which does the tasks discussed in last paragraph. I think it's the next generation of Gmail that embrace all those above function.</p>

<p>The communication protocol includes API for connection and extension to non-Google Wave application such as Twitter and Facebook. So in theory it's the backbone of communications between any internet applications.<br />
</p>]]>
    </content>
    <published>2009-06-08T18:19:58Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:141521</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c141521" />
    <title>Comment from Nathan on 2009-06-08</title>
    <author>
        <name>Nathan</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p><li>"It would be nice if you could turn the real-time aspect of Wave off and only have your messages appear in a Wave after it was completed."</li></p>

<p>To be clear, you can turn this off for yourself!  If you watch the demo again, (somewhere in the first 10-15 mins or so) they talk about how you can choose to just let your messages appear when you are done (with a joke about bad spelling :-) ), but they said it is not active yet.  Just to make sure everyone realizes this functionality.  I'm surprised that you didn't mention Twave (Twitter gadget for Wave) or the robots (Translators, stock quotes, etc.) and that you didn't expand on the support for inline iGoogle gadgets and other tools that are already available.</p>]]>
    </content>
    <published>2009-06-08T20:15:14Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:141610</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c141610" />
    <title>Comment from PigSpigot on 2009-06-09</title>
    <author>
        <name>PigSpigot</name>
        <uri>http://www.pigspigot.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.pigspigot.com">
        <![CDATA[<p>I could see this being very fun for planning things with friends and family: camping trips, bachelor/ette parties, etc. you discuss the trip, you share links and photos and the wave becomes a big part of the fun. <br />
Same goes for work collaboration. We use basecamp and gmail to communicate, but i think something gets lost without the real time feeds. im chat fills in there, but linking all of this stuff would be great. count me among excited and curious early adopters, at least to try a ride on the wave.</p>]]>
    </content>
    <published>2009-06-09T14:19:11Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:141787</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c141787" />
    <title>Comment from James on 2009-06-10</title>
    <author>
        <name>James</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>It's a neat technology and I'm glad they opened up the discussion on the protocol to the public, but what ever happened to opening an RFP/RFC on the IETF site?</p>

<p>For Wave to integrate alongside or replace email altogether, it will have to support the fundamental features of email: plain-text format (which I think it has via XML serialization), encryption, and freedom of provider.</p>

<p>They will also have to prove that the implementation is simple enough to be adopted and improved upon by the community. Already I can see some flaws in its design which might make adoption difficult: the federated OT process they use for the concurrent character-by-character document editing is non-trivial and deterministic. This means that every implementation must be using the same algorithms always.</p>

<p>I have no doubt that these corners will be smoothed over as time goes on and we discover better ways of doing this, but it looks like it will be a large uphill battle from here.</p>]]>
    </content>
    <published>2009-06-10T15:24:27Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:149141</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c149141" />
    <title>Comment from Sachendra Yadav on 2009-07-26</title>
    <author>
        <name>Sachendra Yadav</name>
        <uri>http://sachendra.wordpress.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://sachendra.wordpress.com">
        <![CDATA[<p>The biggest problem it solves is that you no longer have to write "See comments inline"</p>

<p><a href="http://sachendra.wordpress.com/2009/07/26/email-2-0-google-wave-solves-the-see-comments-inline-problem/" rel="nofollow">http://sachendra.wordpress.com/2009/07/26/email-2-0-google-wave-solves-the-see-comments-inline-problem/</a></p>]]>
    </content>
    <published>2009-07-26T09:01:42Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.15237-comment:163275</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.15237" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/google_wave_our_first_hands-on_impressions.php#c163275" />
    <title>Comment from Bill on 2009-10-17</title>
    <author>
        <name>Bill</name>
        <uri>http://www.acslater.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.acslater.com">
        <![CDATA[<p>If anyone is looking for help with Wave or looking for invites or a Developer to help your ideas come to life check out <a href="http://www.gwavecentral.com" rel="nofollow">http://www.gwavecentral.com</a></p>]]>
    </content>
    <published>2009-10-17T17:12:46Z</published>
  </entry>

</feed>