WEBVTT - Google Waves at TechStuff 0:00:00.320 --> 0:00:02.880 Brought to you by the reinvented two thousand twelve camera. 0:00:03.200 --> 0:00:08.920 It's ready. Are you get in touch with technologies with 0:00:09.039 --> 0:00:16.120 tech stuff from how stuff works dot com. You've heard 0:00:16.160 --> 0:00:19.760 the rumors before, perhaps and whispers written between the lines 0:00:19.800 --> 0:00:24.759 of the textbooks. Conspiracies, paranormal events, all those things that 0:00:24.880 --> 0:00:28.760 disappear from the official explanations. Tune in and learn more 0:00:28.800 --> 0:00:30.560 of the stuff they don't want you to know in 0:00:30.600 --> 0:00:43.239 this video podcast from how stuff works dot com. Hello everybody, 0:00:43.240 --> 0:00:46.040 and welcome to tech stuff. My name is Chris Poulette, 0:00:46.040 --> 0:00:48.000 and I'm an editor here at how stuff Works dot com, 0:00:48.040 --> 0:00:51.240 and sitting across from me as usual, is senior writer 0:00:51.360 --> 0:00:57.240 Jonathan Strickland. Hey there, Well all right then, So why 0:00:57.480 --> 0:01:01.040 why why are you waving at me? Oh? That can 0:01:01.080 --> 0:01:07.399 all be explained with a little listener mail. List listener 0:01:07.400 --> 0:01:12.160 mail comes from Lee. Note read in monotone. Oh wait, 0:01:12.200 --> 0:01:15.720 that's that's a stage direction. Hang on, he doesn't take 0:01:15.760 --> 0:01:18.640 direction while I can tell you this from my experience. Hi, 0:01:18.920 --> 0:01:24.760 Google released Google Wave. What is it? Please answer? Love always, 0:01:25.080 --> 0:01:30.559 Lee from Bowling Brook, Illinois. PS. I listened to every podcast. 0:01:31.080 --> 0:01:34.640 You are the highlight of my week. Oh I'm sorry, 0:01:34.760 --> 0:01:38.399 that wasn't quite monotone. Thanks Lee. Uh, I'm glad that 0:01:38.400 --> 0:01:41.959 we're the highlight. Also kind of sad about that. But 0:01:42.040 --> 0:01:45.760 let's talk about Google Wave then. Now, this is something 0:01:45.760 --> 0:01:48.960 that we can actually talk about from experience, because Chris 0:01:48.960 --> 0:01:51.320 and I have been playing with Google Wave for almost 0:01:51.400 --> 0:01:54.920 an entire day. You've been playing with it longer than 0:01:54.960 --> 0:01:57.360 I have. This is true. I got my invite um 0:01:57.400 --> 0:01:59.840 about a little less than a week ago, actually only 0:01:59.840 --> 0:02:03.160 a few days ago. Yeah, yeah, I got mine this morning. Right, 0:02:03.200 --> 0:02:06.720 I've got I've got like three days on Chris as 0:02:06.760 --> 0:02:10.240 far as the Google Wave experience. But let's let's uh, 0:02:10.600 --> 0:02:14.040 let's take in the way back machine, wave back machine, 0:02:14.160 --> 0:02:16.720 the wave back Hey, yeah, let's go into the wave 0:02:16.800 --> 0:02:25.800 back machine. Let's go someplace tropical, Liz take us away. 0:02:27.080 --> 0:02:29.840 Oh this is nice. It's much better than you know, 0:02:29.880 --> 0:02:32.720 the studio where I can hear the fan on the 0:02:32.760 --> 0:02:36.000 computer going. I'm much preferred like the the tweets of 0:02:36.040 --> 0:02:40.800 the the the twitter twittering birds, the sea birds, and 0:02:40.840 --> 0:02:43.720 the the sound of the waves laughing the shore. It's 0:02:43.760 --> 0:02:46.520 amazing soundscaping that Liz is down here, isn't it. It 0:02:46.600 --> 0:02:52.200 is amazing. So before we get lost in this tweeting 0:02:52.320 --> 0:02:54.600 is sort of communication. Yeah, we don't want to stay 0:02:54.600 --> 0:02:57.200 here too long because we'll probably get burned because Chris 0:02:57.200 --> 0:03:01.639 and I are both rather pale, sickly tech geeks. So 0:03:02.880 --> 0:03:04.680 let's let's talk about you know, you know what beach 0:03:04.680 --> 0:03:08.280 were on? Right? What are we on? Australia's beach? They 0:03:08.280 --> 0:03:12.280 only have the one, the only No, I'm kidding all 0:03:12.320 --> 0:03:16.920 the way around, so we're on the reason why I 0:03:16.960 --> 0:03:20.480 say Australia is because it was a team of Google 0:03:20.639 --> 0:03:25.400 folks from Australia who developed Google Wave and they unveiled 0:03:25.639 --> 0:03:30.240 this development development. You know what it's that it's that 0:03:30.520 --> 0:03:34.560 twenty hour flight to Australia that's doing it to me. 0:03:34.960 --> 0:03:40.640 They unveiled this at the Google's Io Developer event back 0:03:40.760 --> 0:03:44.840 in the spring of two thousand nine. Really, yes, and 0:03:44.880 --> 0:03:47.880 it was that short time ago. Yeah, it seems like 0:03:47.880 --> 0:03:49.920 it was a long long time ago, does it. Yeah, 0:03:50.280 --> 0:03:52.360 it was, no, it was just we've been talking about 0:03:52.360 --> 0:03:54.680 Wave for so long. Now. Well, we saw the we 0:03:54.720 --> 0:03:57.560 saw the preview for it, and it was very impressive 0:03:57.600 --> 0:04:02.960 to us. Um. The preview is a ninety eighty minute, 0:04:03.000 --> 0:04:07.400 eighty minute long presentation that that this team gave and 0:04:07.440 --> 0:04:10.720 it wasn't without its hiccups. The first thing we should 0:04:10.720 --> 0:04:13.960 say about Google Wave is that it's a tool that 0:04:14.120 --> 0:04:22.640 is in the preview stage. It's not even in beta, beta, beta. 0:04:22.720 --> 0:04:24.320 For such a long time, I was going to make 0:04:24.400 --> 0:04:28.080 that same comment, Yeah, no, no, no, that's good Google 0:04:28.120 --> 0:04:29.960 back in the way back machine. No no no, no, no no, 0:04:30.000 --> 0:04:35.599 we're still on the beach um. So yeah, Google, Google 0:04:35.680 --> 0:04:39.600 is all about the beta phase of testing, right but 0:04:40.120 --> 0:04:42.239 this is in the preview stage and it's a tool 0:04:42.320 --> 0:04:45.239 that was pretty impressive. I think it took a while 0:04:45.320 --> 0:04:48.200 for the audience to really get into it, but as 0:04:48.480 --> 0:04:52.640 the team began to unveil the different features of Google Wave, 0:04:53.120 --> 0:04:55.839 people were really starting to get excited. And the reason 0:04:55.880 --> 0:04:59.000 why they were unveiling it at the Developers Conference is 0:04:59.120 --> 0:05:03.920 it's not just a a replacement for email or instant 0:05:03.960 --> 0:05:07.920 messaging or anything like that. It's a platform for applications. 0:05:08.839 --> 0:05:13.760 So in a way, they're kind of um reinventing the 0:05:13.839 --> 0:05:19.560 way people could communicate over the web. Now it's in 0:05:19.680 --> 0:05:23.320 its most rudimentary stage right now. At the Developers Conference, 0:05:23.360 --> 0:05:25.440 they went ahead and gave everyone who went to the 0:05:25.440 --> 0:05:29.479 Developers Conference and invite into Google Wave to to check 0:05:29.520 --> 0:05:31.680 out the preview. Hey, last year, you brought me back 0:05:31.720 --> 0:05:35.440 a little compass this year, Yeah, last year I went 0:05:35.520 --> 0:05:38.960 to the Developers Conference. This year of I just couldn't 0:05:38.960 --> 0:05:40.680 do it. I was going to E three. I knew 0:05:40.680 --> 0:05:42.480 that I had I had a ton of other stuff 0:05:42.520 --> 0:05:47.159 going on. I couldn't make it to the conference. Rights, Right, 0:05:47.320 --> 0:05:50.359 they were ending out invites to the most amazing tool 0:05:50.800 --> 0:05:52.760 that Google has come up with in a really long time, 0:05:52.880 --> 0:05:56.560 or what appeared to be according to the video. Right. 0:05:57.279 --> 0:06:00.760 So Chris and I we we kind of we tried 0:06:00.800 --> 0:06:04.560 to pull our weight, you know. We tried to pull 0:06:04.640 --> 0:06:08.839 some strings and grease some palms and go to some 0:06:08.920 --> 0:06:11.680 back alleys and talk to some shady Google people and 0:06:11.720 --> 0:06:18.600 get ourselves some invites. And that failed miserably. Yeah, they 0:06:18.600 --> 0:06:22.040 started asking us Wave questions like, hey, guys, how does Wave? 0:06:22.120 --> 0:06:25.200 Where can we go? Yeah, we had a lot of 0:06:25.200 --> 0:06:28.359 people asking us these questions, and we honestly couldn't answer 0:06:28.400 --> 0:06:31.800 them because we had no access to Wave whatsoever. Well, 0:06:31.839 --> 0:06:34.240 then Google made an announcement back at the end of 0:06:34.279 --> 0:06:37.960 September that on September it was going to open up 0:06:38.160 --> 0:06:44.040 one hundred thousand invitations to Google Wave and the way 0:06:44.040 --> 0:06:46.080 that you would get an invite. They had been accept 0:06:46.320 --> 0:06:50.720 accepting applications pretty much all summer long. You could go 0:06:50.800 --> 0:06:55.080 to Google's uh the Google Wave website, and it would 0:06:55.120 --> 0:06:57.840 have a little form you'd fill out. We fill out 0:06:57.880 --> 0:07:02.120 your information, include your your email account or whatever her 0:07:02.160 --> 0:07:06.560 Google account, and fill out some other little bits like say, 0:07:06.600 --> 0:07:09.400 if you were willing to test for bugs, and if 0:07:09.400 --> 0:07:11.600 you saw bugs, if you would report in that kind 0:07:11.600 --> 0:07:15.200 of stuff. Then I had a section for notes, and 0:07:15.240 --> 0:07:17.560 they suggested that you'd be creative, so I sent in 0:07:17.640 --> 0:07:21.840 an epic poem. Um yeah, My first line was singing 0:07:21.920 --> 0:07:26.520 me oh muse, and then I put an iambic pentameter 0:07:27.240 --> 0:07:30.160 my request to be in Google Wave. Apparently that was 0:07:30.200 --> 0:07:33.320 not impressive enough, because I did not get one of 0:07:33.320 --> 0:07:41.400 those invites. The apparently not. So what was my saving 0:07:41.440 --> 0:07:44.920 grace was that one of the listeners that we have, 0:07:45.040 --> 0:07:47.720 one of my Twitter followers and a listener of tech stuff, 0:07:47.920 --> 0:07:53.280 didn get accepted into the the initial round. And Google 0:07:53.320 --> 0:07:57.480 Wave is a communication tool, so you have to have 0:07:57.680 --> 0:08:01.080 at least two people running Google a Wave to really 0:08:01.120 --> 0:08:03.240 be able to use it, otherwise you're just you know, 0:08:03.280 --> 0:08:07.360 it's I blogged about this recently and I mentioned that 0:08:07.920 --> 0:08:10.320 if you don't have two people, it's as if you 0:08:10.360 --> 0:08:13.000 have an email program and you're the only person in 0:08:13.040 --> 0:08:16.160 the world who has the email program, So you can't 0:08:16.240 --> 0:08:18.160 send you can't do anything with it. You know, you can't. 0:08:18.280 --> 0:08:22.320 You could write messages, but you can't send it to anyone. Right. Well, 0:08:22.360 --> 0:08:24.880 what Google did was they gave the people that in 0:08:24.920 --> 0:08:28.800 that first round a limited number of invitations to send 0:08:28.800 --> 0:08:31.720 out to other people. Right, So this way you could 0:08:31.760 --> 0:08:34.360 guarantee that you would have one or two other people 0:08:34.440 --> 0:08:38.920 at least with whom you could start conversations. Um, I 0:08:38.960 --> 0:08:43.680 believe it was eight invites. They called them nominations, so 0:08:43.679 --> 0:08:47.199 you can nominate people to get Google Wave. Uh, it 0:08:47.240 --> 0:08:49.840 was not immediate the nomination and who you would make. 0:08:49.880 --> 0:08:51.880 You could make a nomination, but it would not immediately 0:08:51.960 --> 0:08:54.040 invite someone into Google Wave. You still had to wait 0:08:54.120 --> 0:08:57.480 because I got the nomination or I was told that 0:08:57.520 --> 0:09:00.520 I was nominated, and then it took almost an entire 0:09:00.600 --> 0:09:04.199 week before I actually got the official invite to get 0:09:04.240 --> 0:09:08.160 into Google Wave. Yeah. As a matter of fact, as 0:09:08.200 --> 0:09:13.600 of this morning, it's still the same way. Yeah. See, 0:09:13.640 --> 0:09:16.120 I didn't even get nominations, So before any of our 0:09:16.160 --> 0:09:18.920 listeners right in and beg me for nominations. Let me 0:09:18.960 --> 0:09:23.480 tell you I don't have any. Because I was I 0:09:23.520 --> 0:09:26.640 was nominated, I did not get my own set up. 0:09:27.440 --> 0:09:30.600 So the economy finally gain of him the nod and 0:09:30.920 --> 0:09:32.920 so it was a Thursday night when I got the nomination. 0:09:32.960 --> 0:09:34.839 I went ahead and felt out the info and then 0:09:34.840 --> 0:09:37.079 I started to try I played with Wave a little bit, 0:09:37.200 --> 0:09:43.120 and it's a bizarre tool. If it's hard to explain it, 0:09:43.120 --> 0:09:46.320 it kind of it's kind of a combination of email, 0:09:47.160 --> 0:09:54.200 instant messaging, collaborative software, and an application platform. Actually, I 0:09:54.240 --> 0:09:57.360 think if you're a UH, someone who has used other 0:09:57.440 --> 0:10:01.120 Google products in the past, it won't be completely foreign 0:10:01.120 --> 0:10:04.079 to you because it has elements. As far as I'm concerned, 0:10:04.080 --> 0:10:07.920 it has elements of Gmail UH and that you know 0:10:07.960 --> 0:10:12.040 how Gmail threads conversations together, that's part of it. And 0:10:12.080 --> 0:10:16.920 then the collaborative UH networking and being able to work 0:10:16.960 --> 0:10:19.560 on the same project at the same time. Google Docs 0:10:19.600 --> 0:10:22.760 has that UM, but it sort of smashes them all 0:10:22.760 --> 0:10:25.560 together with an UH an element of I am a 0:10:25.559 --> 0:10:29.760 little Google Chat. Yeah. So I mean the difference is 0:10:30.600 --> 0:10:33.400 an email is like a static message. It is a 0:10:33.440 --> 0:10:35.640 static message it's not like that. It is that you 0:10:35.679 --> 0:10:38.200 send an email to somebody else, they can they might 0:10:38.240 --> 0:10:39.719 be able to edit it, but they can only edit 0:10:39.720 --> 0:10:43.040 it themselves on that machine. So if you ask five questions, 0:10:43.080 --> 0:10:44.840 if you if I send an email with five questions 0:10:44.880 --> 0:10:46.880 to Jonathan, he can answer all five of those questions 0:10:46.920 --> 0:10:50.320 and and reply to me. But if he sends, if 0:10:50.320 --> 0:10:52.520 I send him a message on Google Wave, he can 0:10:52.559 --> 0:10:55.040 answer each one of those questions in real time, and 0:10:55.080 --> 0:10:57.640 we can actually have a conversation about that one message. 0:10:57.720 --> 0:11:01.360 Rather than sending message after message. We have one message 0:11:01.360 --> 0:11:04.160 that is being pass that is being worked on simultaneously 0:11:04.200 --> 0:11:06.000 by the two of us. And more so, if you 0:11:06.040 --> 0:11:08.800 have multiple people, Let's say that you're trying to communicate 0:11:08.840 --> 0:11:11.040 with five people. You send out the same list of 0:11:11.160 --> 0:11:14.840 questions to five people, You're gonna get five emails back 0:11:14.880 --> 0:11:18.200 with their each person's answers. Right, So now you've got 0:11:18.200 --> 0:11:23.360 Now you've got and and yeah, you don't have everyone's 0:11:23.360 --> 0:11:27.240 answers in one place until you transfer it Google Wave. 0:11:27.320 --> 0:11:29.560 You could invite those five people into a wave with 0:11:29.640 --> 0:11:33.160 you list of five questions. Each person could reply on 0:11:33.240 --> 0:11:35.600 his or her own time, and then you have one 0:11:35.600 --> 0:11:42.280 place with all the answers. So it's a centralized communication device. Um, 0:11:42.320 --> 0:11:45.200 you do see updates in real time. So if if 0:11:45.320 --> 0:11:48.439 Chris were in a wave, that he and I were 0:11:48.440 --> 0:11:50.440 in together, and a wave is just think of a 0:11:50.440 --> 0:11:54.360 wave as a conversation. So let's say that Chris has 0:11:54.400 --> 0:11:56.920 opened up a wave. For example, this morning, we were 0:11:56.960 --> 0:12:00.360 creating a rundown for tex Stuff Live. So let's say 0:12:00.400 --> 0:12:02.160 that Chris has got an idea for a story for 0:12:02.200 --> 0:12:05.920 tech stuff Live and he types out the title. I 0:12:06.040 --> 0:12:08.240 log into Google Wave. I see that Chris is working 0:12:08.240 --> 0:12:10.080 on a wave and that he's invited me. I go 0:12:10.200 --> 0:12:13.720 into that wave. I can actually see as he's typing. 0:12:13.760 --> 0:12:17.800 I'll see the letters appear on the screen in real time. Yep. 0:12:18.120 --> 0:12:20.640 So I can then see like, oh I hate that story. 0:12:20.679 --> 0:12:23.120 I can reply immediately and say, look, let's not waste 0:12:23.120 --> 0:12:25.240 our time on that. That's that's story is old and 0:12:25.240 --> 0:12:28.400 no one's interested. And then Chris will go and eat 0:12:28.440 --> 0:12:30.640 a gallon of butter pecan ice cream and cry in 0:12:30.679 --> 0:12:36.240 the corner. This is pretty much what we call Tuesday morning. Yeah. Um, 0:12:36.600 --> 0:12:40.280 and if Jonathan happens to not be watching, uh you know, 0:12:40.320 --> 0:12:43.720 he doesn't have Google Wave open, then when he comes 0:12:43.760 --> 0:12:47.160 back from uh, you know, going to get his twelfth 0:12:47.160 --> 0:12:49.880 cup of coffee in the morning, and he can come 0:12:49.880 --> 0:12:52.120 back to his desk, open Google Wave and he'll see 0:12:52.400 --> 0:12:54.800 all of the changes that I've made to our wave 0:12:54.920 --> 0:12:59.760 message highlighted, so he'll know specifically what changes I've made. 0:13:00.520 --> 0:13:01.800 You know, he doesn't have to go through and away 0:13:01.800 --> 0:13:04.400 a minute. Was that and there before? No? No, yeah that, No, 0:13:05.360 --> 0:13:06.960 he doesn't have to worry about that stuff. It's gonna 0:13:06.960 --> 0:13:09.320 be readily apparent to him. And if you have multiple 0:13:09.360 --> 0:13:12.160 people in a wave at the same time all typing, 0:13:12.880 --> 0:13:17.160 each person's uh contributions will be marked with a little 0:13:17.360 --> 0:13:20.560 icon that has their Google Wave name on it. Okay, 0:13:20.679 --> 0:13:22.560 so let's say there's three people all typing in a 0:13:22.559 --> 0:13:24.920 Google Wave at the same time. If you were to 0:13:24.960 --> 0:13:27.160 take a break and stop typing to look and see 0:13:27.160 --> 0:13:29.520 what other people are typing, you'd see that your buddy 0:13:29.520 --> 0:13:33.320 Alex is typing one message maybe you know, two replies up, 0:13:33.400 --> 0:13:36.240 and your brother, your your you know, buddy Bob, he's 0:13:36.280 --> 0:13:38.640 typing something a little further down, and then you would 0:13:38.679 --> 0:13:41.400 see both being updated in real time. Um. And it's 0:13:41.480 --> 0:13:43.560 nice that it's labeled because that way you can see 0:13:43.559 --> 0:13:48.120 who labeled what, who who contributed what. It still seems 0:13:48.120 --> 0:13:52.920 pretty chaotic, so the team included another feature that's pretty 0:13:53.000 --> 0:13:57.960 useful called playback. Yes, playback lets you look at a 0:13:58.000 --> 0:14:02.200 Google wave and view it in in various iterations. So 0:14:02.240 --> 0:14:05.239 each time someone's coming and made a change, you can 0:14:05.480 --> 0:14:07.880 go to that point and see what the wave looked 0:14:07.880 --> 0:14:10.600 like before the changes were made and what looked like 0:14:10.720 --> 0:14:12.880 after the changes were made, So that way you can 0:14:12.920 --> 0:14:15.560 review edits. So let's say that Let's say that you 0:14:15.679 --> 0:14:18.000 have not been in wave for a while, and you've 0:14:18.040 --> 0:14:21.120 got two friends who have been in this wave. You're 0:14:21.120 --> 0:14:23.760 all discussing something important, like you you've got a big 0:14:23.800 --> 0:14:26.480 party coming up and you're planning it with these two 0:14:26.480 --> 0:14:30.880 other people, and while you were offline, they had a discussion, 0:14:31.160 --> 0:14:34.800 edited things and then moved on from there. You log 0:14:34.880 --> 0:14:36.520 in and you see the edits, but you don't see 0:14:36.520 --> 0:14:38.520 any of the discussion. You can use the playback to 0:14:38.640 --> 0:14:41.680 go back and look through and see if there was 0:14:41.720 --> 0:14:45.120 something important that you missed. So that was a good 0:14:45.160 --> 0:14:47.720 feature to add in there. It does. It does take 0:14:47.720 --> 0:14:49.920 you step by step through the process. You can see 0:14:49.920 --> 0:14:52.960 everything that has been done to that document. Yeah, Um, 0:14:53.000 --> 0:14:56.400 there is another bit of mash up involved in the 0:14:56.440 --> 0:15:00.560 Google Wave that I didn't speaking of Google products that 0:15:00.560 --> 0:15:04.080 that I didn't mention. And that's a blogger you might 0:15:04.080 --> 0:15:07.400 be saying, blogger, how does that factor into anything? Well, 0:15:08.080 --> 0:15:10.840 it's got a little bit of a content management system 0:15:10.880 --> 0:15:15.000 to it also sort of a CMS. Uh, and you 0:15:15.040 --> 0:15:18.840 can add links to the document. You know, that's not 0:15:18.880 --> 0:15:23.680 really that revolutionary, um, but you can also use these 0:15:23.680 --> 0:15:29.000 tools to to add maps or videos or all kinds 0:15:29.000 --> 0:15:31.960 of other things to the wave. And and not only that, 0:15:32.000 --> 0:15:35.680 you can actually embed waves into a blog, which is 0:15:35.760 --> 0:15:37.440 really cool because you can actually put it on a 0:15:37.480 --> 0:15:39.040 web page. And if you are part of the one 0:15:39.080 --> 0:15:42.160 of the waivers in this group, um, you can actually 0:15:42.160 --> 0:15:46.240 see real time changes on a blog as you would 0:15:46.280 --> 0:15:49.560 in Wave. That's what's supposed to happen. What's cool is 0:15:49.560 --> 0:15:51.840 that if someone were to say, look at your blog 0:15:51.880 --> 0:15:54.440 and leave you a comment, you can see the comment 0:15:54.480 --> 0:15:57.960 appear in real time on Wave. You could respond in 0:15:58.080 --> 0:16:01.440 Wave and have it show up on the blog. So 0:16:01.440 --> 0:16:06.000 it becomes kind of a blog management tool that sense um. 0:16:06.040 --> 0:16:08.800 And yeah, the some of the other gadgets that you 0:16:08.840 --> 0:16:12.080 can add into Google Wave are pretty cool. There's some 0:16:12.200 --> 0:16:14.920 pretty simple ones. There's one that's a yes, no, maybe pole. 0:16:16.360 --> 0:16:18.280 So let's say that you create a wave with like 0:16:18.320 --> 0:16:20.960 twelve people and you're trying to see who would be 0:16:21.000 --> 0:16:23.960 available on a certain day for a party. And you 0:16:24.320 --> 0:16:27.040 send out a wave of saying, I'm looking at you know, 0:16:27.120 --> 0:16:31.400 October thirty for a Halloween party. Who's available? You put 0:16:31.400 --> 0:16:34.640 in the yes, no, maybe. Each person just clicks whichever 0:16:34.720 --> 0:16:38.640 response um applies to the him or herself, and then 0:16:38.680 --> 0:16:41.080 you'll see like if if, like you know, seven people 0:16:41.120 --> 0:16:42.960 click yes, and you can see which of the seven 0:16:43.000 --> 0:16:47.480 people click yes. Everyone can see it actually, and uh, 0:16:47.640 --> 0:16:50.520 I mean it's it's a built in gadget. It's already there. 0:16:50.600 --> 0:16:53.280 You don't have to design it yourself, so you can 0:16:53.320 --> 0:16:56.119 just drop it in there and and does all the 0:16:56.120 --> 0:16:58.920 the organizing for you. And you can change your answer 0:16:58.960 --> 0:17:01.240 at any time, so you don't like, if you've clicked 0:17:01.280 --> 0:17:04.160 on yes and you meant no, that's not a big deal. 0:17:04.200 --> 0:17:06.119 You can just click on no and it'll swap you 0:17:06.200 --> 0:17:09.399 over to the other column and that's fine. But there 0:17:09.400 --> 0:17:12.439 are plenty of other gadgets. There's the map gadget, so 0:17:12.480 --> 0:17:14.800 you can create used Google maps and look at. You 0:17:14.800 --> 0:17:17.080 can create a map, interactive map with a whole bunch 0:17:17.119 --> 0:17:20.320 of people. So you can do that for anything from 0:17:20.359 --> 0:17:24.600 just giving people directions to a location to maybe doing 0:17:24.640 --> 0:17:26.639 a scavenger hunt if you want it. I mean, there 0:17:27.320 --> 0:17:31.480 limitless applications really, it's just limited by your own imagination 0:17:31.640 --> 0:17:34.520 and the people with who you and the people who 0:17:34.560 --> 0:17:36.440 are on Wave. I was totally going to make that point, 0:17:36.840 --> 0:17:38.560 which will probably be just like three or four other 0:17:38.600 --> 0:17:42.320 people you actually know in your life at least. Yeah. Yeah, 0:17:42.359 --> 0:17:44.639 once it opens up wider will be much more useful. 0:17:44.840 --> 0:17:47.200 But there are a lot of other uh well, there 0:17:47.400 --> 0:17:50.240 are a few other applications that are available now. What 0:17:50.320 --> 0:17:52.960 I'm excited to see is what comes available in the future. 0:17:53.080 --> 0:17:58.679 Because it's such an open platform, you could create a 0:17:59.040 --> 0:18:04.119 kind of a a miniaturized Worldwide Web around a specific 0:18:04.200 --> 0:18:07.439 topic like imagine that you just want to discuss with 0:18:07.480 --> 0:18:10.679 your friends, very specifically a show you want to go 0:18:10.760 --> 0:18:13.679 to and you want to try and convince some people. 0:18:13.800 --> 0:18:15.840 Some people know the band that you want to go see, 0:18:15.880 --> 0:18:18.520 some people don't. So in this wave where you're inviting 0:18:18.560 --> 0:18:20.800 people to go, you include a map to the venue, 0:18:21.119 --> 0:18:24.800 to include um links to the venue's website, so people 0:18:24.840 --> 0:18:27.359 can get a look at what the venue looks like inside, 0:18:27.400 --> 0:18:29.240 you know, look at pictures. You could you can upload 0:18:29.280 --> 0:18:32.120 pictures to the wet wave so people could look at 0:18:32.160 --> 0:18:36.000 a slide show of pictures. Um. You could embed video 0:18:36.160 --> 0:18:38.440 of the band. Let's say the band's got a YouTube video. 0:18:38.480 --> 0:18:41.000 You could embed that YouTube video in the wave so 0:18:41.040 --> 0:18:44.000 people could listen and see what it looks like before 0:18:44.480 --> 0:18:49.080 committing to to going or not going. It's and it's 0:18:49.080 --> 0:18:51.159 such a centralized way of doing it. You don't have 0:18:51.240 --> 0:18:54.960 to use eight different tools, right, you know, So it 0:18:55.080 --> 0:18:58.000 makes makes it much easier to do that kind of thing. 0:18:58.000 --> 0:19:00.960 And like I said, we're using it now. At least 0:19:01.000 --> 0:19:03.560 we used it today to create a rundown for tech 0:19:03.560 --> 0:19:06.440 Stuff Live um and it worked pretty well. Yeah, it did. 0:19:07.400 --> 0:19:09.480 I think it would get confusing if you were working 0:19:09.520 --> 0:19:11.600 with maybe five or six other people all at the 0:19:11.600 --> 0:19:13.919 same time, But with just the two of us, it 0:19:14.000 --> 0:19:17.719 was easily manageable. Yeah. Yeah, do you want to talk 0:19:17.760 --> 0:19:22.280 about robots, Sure, talk about robots. Um. The Google Wave 0:19:22.359 --> 0:19:27.879 team has enabled the possibility that robots can also help you. Yeah, 0:19:28.640 --> 0:19:38.960 like data and uh, yes, and not so much. You 0:19:39.040 --> 0:19:45.240 used an android a droid and they're all robots anyway, 0:19:45.480 --> 0:19:50.320 we're not actually talking about that type of robot. Robots 0:19:50.320 --> 0:19:53.040 basically are sort of like the bots that you see 0:19:53.080 --> 0:19:57.760 on chat or in chat rooms. UM. You can actually 0:19:57.760 --> 0:20:01.960 have a robot that's in h involved in the wave 0:20:02.040 --> 0:20:05.800 with you, with other people, and so it basically functions 0:20:05.840 --> 0:20:09.000 like a script like you can have it if you 0:20:09.040 --> 0:20:11.639 start doing certain things in the wave and the robot 0:20:11.720 --> 0:20:14.840 is part of that, it might automatically go ahead and 0:20:15.040 --> 0:20:17.600 take care of some things that you would normally do yourself. 0:20:18.280 --> 0:20:22.399 So it's basically like a series of scripts. UM. But 0:20:22.640 --> 0:20:25.720 you know it can UM. It can allow you to 0:20:25.800 --> 0:20:28.720 look for certain topics and waves that you're you're trying 0:20:28.760 --> 0:20:31.679 to look for, and it can UH. There's actually an 0:20:31.720 --> 0:20:37.240 automatic translation UH system, which is really cool. If you 0:20:37.240 --> 0:20:42.080 have somebody, say in Germany and someone in I don't know, China, 0:20:42.280 --> 0:20:45.240 and they want to work with one another on the wave, UH, 0:20:45.240 --> 0:20:47.320 they can talk in their native languages without having to 0:20:47.400 --> 0:20:50.600 learn a new language, and Google will use its translation 0:20:50.680 --> 0:20:54.320 tools to automatically translate that for them into something vaguely 0:20:54.359 --> 0:20:58.760 resembling their native language. You'll actually see both both threats, 0:20:58.960 --> 0:21:01.800 so you'll see the original language that the person is 0:21:01.840 --> 0:21:04.320 typing in and then you'll see the translation as well. 0:21:05.000 --> 0:21:07.680 So like, for instance, I'm saying that I'm talking about 0:21:07.720 --> 0:21:10.480 the Palm Prex with my friend in Germany, and I 0:21:10.520 --> 0:21:13.520 don't happen to know that palm pre and German is 0:21:14.880 --> 0:21:19.240 shot and flugan flag and we wolf in China. Uh, 0:21:19.720 --> 0:21:22.720 Google knows, and so Google, you know, I'll type in 0:21:22.760 --> 0:21:26.800 palm prex, but it'll come out as HTCG one right 0:21:26.880 --> 0:21:31.200 shot and fluid and flag. Yes I'm kidding, I'm kidding, 0:21:32.800 --> 0:21:36.320 but yeah, yeah, I said that was one of the functions. Yeah, 0:21:36.320 --> 0:21:38.320 that was one of the most impressive functions that I saw. 0:21:38.400 --> 0:21:40.000 And a lot of these are on the video if 0:21:40.000 --> 0:21:41.760 you really I mean again, the video is like an 0:21:41.760 --> 0:21:45.680 hour and twenty minutes long, but it's it's worth watching. Yeah, yeah, 0:21:45.760 --> 0:21:50.399 well they Uh, the startup the little um Waves that 0:21:50.440 --> 0:21:54.200 I got from Google as starters had some some stuff 0:21:54.200 --> 0:21:56.600 on YouTube, so I'm assuming that that can actually be 0:21:56.680 --> 0:21:59.159 viewed by other people than are just on Wave, So 0:21:59.200 --> 0:22:02.680 there's probably quite a few demo videos that are available 0:22:02.680 --> 0:22:06.199 there actually. Um I included a YouTube demo video of 0:22:06.240 --> 0:22:09.040 Wave on one of my blog entries back when Wave 0:22:09.119 --> 0:22:11.359 was first announced. Actually, I think Marshall did too, so 0:22:11.440 --> 0:22:14.200 I think we double dipped into the Google Wave pool. 0:22:14.640 --> 0:22:19.080 To speak you you like that, there's a little bit 0:22:19.119 --> 0:22:23.600 of a pun. Um. I'm really excited to see where 0:22:23.640 --> 0:22:27.560 this goes. Right now. I think it's got amazing potential 0:22:27.880 --> 0:22:32.560 but very limited use. And again most of that is 0:22:32.600 --> 0:22:36.080 because it's just it's there's not enough people on it 0:22:36.240 --> 0:22:40.720 to really test it now. It's in preview, they're still 0:22:40.720 --> 0:22:44.280 building out the infrastructure. It's not ready for widespread release, 0:22:44.359 --> 0:22:47.560 so I can't. I can't argue with their decision. It's 0:22:47.600 --> 0:22:50.280 just frustrating because you could. I can see so many 0:22:50.320 --> 0:22:53.160 potential uses for this, and I'm just dying to get 0:22:53.200 --> 0:22:56.840 to that point. Um. What I'm worried about is that 0:22:58.240 --> 0:23:01.480 Google will either lose interest in the project or they'll 0:23:01.800 --> 0:23:05.040 redirect them into some sort of other project and this 0:23:05.119 --> 0:23:09.280 will never come to fruition. I okay, you don't have 0:23:09.320 --> 0:23:11.880 to worry about that. Well, no, because I don't work 0:23:11.880 --> 0:23:13.960 for Google. I can't. I'm not the one who makes 0:23:14.000 --> 0:23:17.760