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!!!

Wave This API released. Plus Official Chrome Extension and Bonus Unofficial WordPress Widget is a post from: The Geekorium

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.

Remove: Remove Yourself! Remove Others! is a post from: The Geekorium

https://wave.google.com/wave/wavethis?t=[insert title]&c=[insert content]

Using a bit of PHP in WordPress and a plugin called Samsarin PHP Widget (that allows php in a special widget) I created the Wave This! button over at the side. Feel free to use it!

The PHP I used was as follows:

<?php if ( is_single($post)) {
$excerpt = urlencode(get_the_excerpt());
$posttitle = urlencode(get_the_title());
?>
<a href="https://wave.google.com/wave/wavethis?t=<?php echo $posttitle ?>&c=%22<?php echo $excerpt; ?>%22"><img src="http://turbo.firstwaves.org/wavethis-button-dark.png" alt="Wave This!" /></a>
<?php } ?>

Simply install and activate the plug-in. Add the Samsarin widget to your sidebar and past the code in as you see it. It will only appear on post pages (not the front page).

I created a couple of button images you can feel free to use:

So that’s the new Wave This! button. Go ahead and give it a try. If you’re a developer I’d be interested in seeing other ways to implement this.

New “Wave This!” Function and Buttons is a post from: The Geekorium

In a short and succinct tweet by Joakim Nejdeby, we finally have news of Google Wave in an Apps environment. With almost little to no fanfare.

Google Wave activated for our students, http://wave.student.liu.se #googlewave #Google #GoogleApps #liu

Joakim Nejdeby is the CIO of Linköping University, a large University in Sweden with some twenty-five thousand students. In an email exchange with Mr Nejdeby, I clarified some of the details of the roll-out. I asked if this was an official partnership with Google and if we could expect an announcement from them. He replied:

From what I understand this is a preview activated for a few customers using Google Apps. I expect the twitter and Facebook announcement [from Nejdeby himself] was the official announcement. We will likely add information on our student pages as well.

Asked whether the student accounts were compatible with the current public Wave infrastructure, or if they were limited to sending waves withing their own domain Nejdeby replied:

I have not seen any observable difference between the regular Wave system and our preview. From what I can see there are no limitations in interactions between our users and the public system.

I’ve asked to connect with Mr Nejdeby (a fan of Google Wave from day one) on Wave to see how well the two systems interoperate. If it does indeed work as well as Nejdeby says, then this (to my knowledge) will be the first large scale public roll-out of Google Wave outside of the Google Public Preview opened last September. Linköping University has activated Google Wave on their domain for 31858 users and reports that they currently have close to seventeen thousand active Apps users. How many active Wave users this will translate to remains to be seen.

It may be by releasing Wave in contained environments such as universities, Google hopes to continue testing and expanding in an environment that is more receptive to the collaborative nature of Wave. One of the complaints leveled at Wave has been that people fail to see the need for another communication medium in their daily workflow. As a new technology without widespread use, it’s difficult to use on a daily basis as a user’s main means of communication. Perhaps with large businesses and education institutions on board Wave might see increased uptake as people learn how simple it can make internal collaboration. We may even see these large organisations driving a push to activate Wave for other companies and institutions as they get used to using them amongst themselves.

It should be noted that this opening up is not quite the announcement of full-scale federation that some Wave developers and users are hoping for. The Apps infrastructure is run by Google and managed by the individual organisations, so can more easily integrate with the public Google Wave service. Hopefully though, as Google Wave grows in popularity with education and business it will spur development of competing products on top of the Wave Protocol.

Update: I apparently missed that Google said they were making Wave available to select institutions “this fall”, 2009 soon after Wave was opened to the public.

Image by Joakim Nejdeby

Google Wave Available to 31000 University Students is a post from: The Geekorium

For dedicated geeks, there are browser extensions, OS specific software, iPhone Push notifications, and more.

But most of these don’t figure in the non-geek arsenal for managing the wash of information from the internet. And for regular folk convincing them to use Wave without these sorts of notifications will be hard simply because they don’t want to bother checking for new waves as well as new emails.

Convincing them may have just gotten easier however with the release of integrated email notifications for your Wave inbox. In a post on the official Google Wave Blog, Ged Ellis explains how to turn on email notifications for new waves. Using the drop down list next to the inbox link (it’s hidden until you hover over it) you can choose an email address to have notifications sent to. The tool even picked my Google Apps email even though it’s not my official Wave address because I’ve set it as primary in my Google profile.

If you want to use Google Wave with your friends, family or colleagues who aren’t logging in frequently, help them to turn on notifications. Then, they can get updates on their Google Wave account, even if they mainly stick to checking their email inbox.

Perhaps this feature was always on the cards, or maybe it was a reaction to the waning interest in Wave from the geek community. By making it easier to get notifications people might start inviting friends who might otherwise be uninterested in another tool to check. I know I’ll be inviting my wife and a couple of buddies that I’ve previously thought might be uninterested thanks to this addition.

However it’s still a long way from the ultimate integration I see is necessary for Wave to finally catch on — using Wave as a full email client. As long as email and waves are two separate entities in two separate products there will still be two places someone must visit to get both the old (email) and new (wave) forms of communication. Notifications via email just makes this more obvious. Ideally Wave should be usable as a hub for all sorts of communication. Currently the closest we have to this ideal is email, but it’s dependent on services sending out notifications. With Wave, the potential for any third-party to integrate services via bots and gadgets gives Wave a clear advantage.

All said though, the notifications are a welcome addition, and will make convincing friends and family to join that much easier. Time will tell if it helps Wave get the consistent user numbers it needs to take off.

Google Wave Gets Email Notifications is a post from: The Geekorium

In my post yesterday I noted the increased push by the Wave developers to make it easier for the wave community to build and deploy extensions. It turns out this flurry of activity coincided with the imminent release of Version 2 of the Wave API, announced today.

The first new feature is the:

Active API: In v2, robots can now push information into waves (without having to wait to respond to a user action). This replaces the need for our deprecated cron API, as now you can update a wave when the weather changes or the stock price falls below some threshold. You can learn more in the Active API docs.

If I understand this correctly (and I’m not a developer so correct me if I’m wrong) this means that before today, a robot in a wave might have had to wait until a user opened a wave before it could refresh the information in the wave (updating stocks etc), now the robot can initiate a wave update itself, making it possible to have robots create new blips in response to events. This is a much smarter way for a robot to behave, and should make for far more interesting and functional bots.

For a more enlightened perspective from a wave developer, check out Mastering Wave’s take on the announcement.

So what I initially thought was just a push to get developers involved was actually leading to an announcement of a massive upgrade to the API. In the end though, the aim is the same — to get developers engaged and creating interesting software to make Wave an indispensable tool.

Google Wave Developer Blog: Introducing Robots API v2: The Rise of Active Robots.

Image by http://www.flickr.com/photos/avoiretc/ / CC BY 2.0

Google Wave Births “Active Robots” is a post from: The Geekorium

Well, with the release of the Read-Only feature, you can now specify select users and groups as read-only participants, meaning they can see your waves in production, but can’t edit them themselves. Perfect for the thousands of informational waves that are available, particularly those that might not have been edited in a while but might be ripe for archiving. To make a user or group read-only, simply click on their icon and select read-only from the new drop down box.

The second feature is one of the other most requested tools — the ability to restor a wave to a former state. Those destroyed and damaged waves I mentioned? Now they have a chance of resurection, without the annoying cutting and pasting that went with the process before now. While playing back a wave, click Restore when you’re at the point before it all went pear-shaped. You won’t lose any data, as the state will be copied to the end of the playback and you can still see the changed that were made after that point.

Between these two new (some would argue vital) tools, Wave becomes more than a novel real-time experiment, and begins to take shape as the useful documenting, collaboration tool it always promised to be. Of course, there are still more changes needed before it becomes a reliable collaboration tool (revert single blips, read-only main blips with posting rights) and the team promise much more in their announcement post, but this is a terrific first step.

Restore a Wave to a former state, or make it Read-Only. is a post from: The Geekorium

The service does not yet allow you to add users by their googlewave.com account (gmail.com only), and the permissions can only be handled through the Google Groups interface. It also seems that to avoid spam (being able to send messages to an everyone in a public group at once) users must pro-actively seek out the group wave and follow it to move it to their inbox [currently waiting for confirmation of this].

Like any Wave feature, this is still being developed and its behaviour could change over time. The Wave team have said they will continue to enhance the groups feature to make groups easier to navigate.

Waving with groups — Google Wave Blog.

Group Waves is a post from: The Geekorium

The downside of this was a significant gotcha: just clicking a public wave was enough to add you to the Wave permanently and drag the wave into your inbox. From that point, your only recourse to silence the wave was to mute it (archiving only works as long as no one else contributes), and muting does not remove you from the wave.

The inability to remove yourself from a wave you have participated in is an accounting feature I guess. When the development team finally gives us the ability to remove ourselves, we still need to know which waves we have participated in.

But back to the sticky business of autofollowing public waves. What it meant was the risk of associating with Waves you never meant to follow. A misplaced click (very easy in the fast-flowing river of public waves) meant a new wave in your inbox and your face on the top of a wave. For example, clicking a wave called  “I hate my boss” immediately associated you with that wave!

Today Google have rolled out a new feature to fix this. Two new buttons now let you Follow and Unfollow a wave. When you click on an interesting public wave, you are no longer added automatically. Once you click off that wave, it will disappear into the stream and you will have no further part in it. To monitor it in your inbox/folder structure, you can now choose to follow it (using the Follow button of course), and it will move into your inbox, where you can treat it like any other wave you are in. You can move it to folders, searches will include it and it will behave like a normal wave with one key difference: you will not appear in the list of wave users at the top.

This makes a huge difference, and means that public waves now take on a sort of social networking aspect, as you can follow the information and people who interest you without being directly involved (sort of like feed readers or Twitter lists). It also improves the user experience by making public waves something you have to explicitly choose to have in your inbox.

To remove a wave from your inbox, you can simply click Unfollow and the wave will disappear as though it was never there.

Keep in mind though that the public wave behaves as it used to the second you edit it. As soon as you create or edit a blip, the wave will add you as a participant and the wave will appear in your inbox as though you had followed the wave. This makes perfect sense, as participation triggers all the accounting measures that must keep track of who made what changes. Unfollow will not remove you from the wave, it will merely be archived from view (the old Mute function).

All in all these changes are a welcome fix to one of the most vexing problems of the initial release. I look forward to seeing the other improvements as Google Wave develops!

Follow your waves — Google Wave Blog.

Follow, Follow, Follow, Follow the Waves You Choose is a post from: The Geekorium