Posts made in 2010

Today at the Google I/O Conference (the same one that Google Wave was announced at last year) Lars Rasmussen gave a brief update on Google Wave. The biggest news is that Google Wave is now available for any one to sign up without an invitation. This makes it much more likely that large groups will just get started collaborating on Wave without having to coordinate Wave invitations for everyone. While the service was invite-only it had the appearance of being a “tech elite” product. As more people found uses for it in group situations (classrooms, meetings) the need to make it easy for the people that actually wanted to use the product to do so became obvious.

In a guest post on the Huffington Post, Lars explains:

For this reason, today we opened up Google Wave to everyone. You no longer need an invitation to use the service. Simply go to wave.google.com and sign right in. Likewise, if you administer a Google Apps domain, you can now easily enable Google Wave for all your users at no extra cost. Google Wave is now officially part of Google Labs, the same place my team launched Google Maps close to 5 years ago.If you tried Google Wave earlier and found it not quite ready for real use, we think you’ll find that a lot has changed, and now is a good time to give it another look.

Did you catch that second part? That was the other half of the announcement: Google Wave is now live for all Apps for Your Domain accounts! If you are using Gmail or Google Calendar on your own domain name, you can now use Google Wave too, and it integrates fully with the normal Google Wave experience. Those of you who have been waiting for this since launch, or since Linkoping University announced it for their students, well wait no more!

It took about 3 hours from the announcement to being able to add Wave to my own domain account. Setup is a breeze. Click the “Add more services” link on your App Dashboard to install the Wave Preview. Then get Waving!

Don’t forget to Wave @ me and add josh@nunnone.com to your Wave contacts.

A few weeks ago, I noticed a new feature of Google Wave that allowed a user to easily send websites and content to a new wave to easily share with others. The feature (called “Wave This”) was not officially announced at the time, and I was asked politely not to say anything more at the time until the team could officially announce it.

In addition to this, the Wave This function has an official Chrome Extension. Install the extension, and you can send any page to Wave with a click!

Finally, you can also use an undocumented Wave This feature to add a Wave contact button to your sites. At the top of my page I’ve added a “Wave @ me!” button that starts a new wave with me as a participant so you can easily contact me in Google Wave. To add the button to your own site it’s as easy as filling your details in the code below:

<a href="https://wave.google.com/wave/wavethis?t=Contact+via+[Your-Site-Name]&r=[fill-in-your-@-wave-address-here]" title="Contact me in Google Wave" class="vt-p"><img src="[your-button-image]" alt="Wave at me!"></a>

The &r parameter for adding a recipient isn’t listed on the API page and support might be pulled or altered so use at your own risk. Additionally, be aware that the Wave This function currently defaults to the Google Wave Preview account only, so if you use a different client (a Google Wave for Domain Apps account for instance, or Novell Pulse) you’re out of luck for now.

So there you have it! A new API, an awesome function, and my modest widget. Have at it! Make some buttons!! Start spreading Wave!!!

Something that’s been bugging me about the Google Wave interface are the icons that show you three participants from each wave in your inbox (and other searches). The origins of the feature make sense – in email we’re used to seeing who an email is from right from our inbox. In one and two person waves it does kind of make sense, but when you have multiple participants the icons stop being useful and just become clutter. To me it adds nothing to my ability to identify a wave and just makes my inbox “noisy”. The icons in the wave make sense, but I’d like a more thought out approach to identifying waves. Something like:

• Make waves I’ve started a slightly different colour (like sites where the author’s comments are shaded slightly blue).
• Don’t show icons at all in the inbox/searches (or make it easy to show and hide).
• Let me tag or bookmark specific blips within waves and make it obvious from the inbox which waves have “starred blips”.

Now this post wasn’t started just as a gripe against something I’d like to see changed – I’d like to hear what things you’d change about wave if you could. I’m not necessarily talking features we know might come (like the recently switched on “Remove” button). I mean interface and behaviour changes that don’t make sense to you, or made sense at first, but don’t now you’ve used it a bit. What are your specific gripes and revolutionary ideas that would make using Wave more of a delight for you?

The most long-awaited feature (besides the seemingly dead “Draft” button) has finally been imlemented by the Google Wave team. That’s right, Remove Participant is here! What this means if you’re not an addicted Wave user, is that wave authors now have total control over who comes and goes from their waves.

This is a big deal for Google Wave. The button has been there since the beginning, but grayed out and unusable. It’s taken some of the shine off Wave that until today you were unable to recall waves or remove people added accidentally.

It works in a pretty straight forward way. You decide someone should not be a participant any more and you click remove. The person who is removed sees a big red X on the wave in their inbox and opening the wave shows the last thing they were able to see before you removed them. If you remove them before they even open the wave, they won’t even know it existed!

Part of me balks at the idea of removing waves right out from under their noses if they haven’t opened them. It feels somewhat dishonest – but it’s actually just fixing a email shortcoming! I think we’ve gotten so used to the idea that once something is sent, it can’t be unsent that it feels a bit weird to actually be able to do it again. Keep in mind though that this probably isn’t foolproof. If for example someone’s waves become “unsynchronised” while you are removing them from the wave, they might still see it – leaving you thinking that you got to it in time.

Another big issue in the months since launch has been Wave abuse. Waves have been destroyed by malicious (and accidental) addition of bots, or overwhelming the wave with large amounts of spammy text. At the moment, the best way to deal with this has been to reduce the abuser’s participation to “Read-Only” and report them to the abuse team. This remains the best way to halt an ongoing attack, but now it’s also possible to clean up after an abuser by removing the sign they were ever there in the first place.

But it’s not going to happen overnight. It will be five years before we can say “this actually works.”

Lars Rasmussen on Google Wave via CNET UK.

Told you so