Google Wave Blog Carnival

Just a heads up that two of my articles have managed to find their way into the first edition of the Google Wave Blog Carnival.

  • Share/Bookmark

Google Wave Keyboard Shortcuts

Google Wave is one of those applications that really benefits from the use of keyboard shortcuts. You can navigate and use everything with the mouse, but the keyboard makes things far more simple and intuitive, once you get used to them.

So, without further ado, here is a list of Google Wave Shortcuts. Most of them are listed on the Official Help site, but I have tried to include some of the lesser know ones, and advice on how to use them.

Navigation

  • Up/Down Arrows - Used to navigate from blip to blip
  • Left/Right - Used to navigate between panels, normally between the search and wave panels
  • Home/End - Used to go to the first/last blip in a wave
  • Space - This takes you to the next unread blip (either a new blip, or one that has changed since you last read it). Something that a lot of people struggle to get used to is the fact that pressing space takes them to an unread blip, even if it is in another wave. After the initial adjustment period, I find this way of doing things much more convenient.
  • Ctrl – Space - Marks all the blips in the current wave as read.
  • Ctrl – Click (or Cmd-Click on OS X) - Opens a wave link in a new panel.

Ways to Edit

  • Enter - Reply to the current blip, the reply will appear below the current blip. If there is text selected, than the reply appears as a blip directly below that text, within the current blip.
  • Shift – Enter - Reply at the end of the current thread
  • Ctrl – E - Edit the current message

Editing a Blip

  • Ctrl – B - Bold
  • Ctrl – I - Italic
  • Ctrl – U - Underline
  • Ctrl – L - Create a link from highlighted text (apparently the wave team is planning to change this one soon)
  • Ctrl – C - Copy highlighted text
  • Ctrl – X - Cut the highlighted text
  • Ctrl – V - Paste
  • Ctrl – 1 – Make the current line a Heading 1 (similar to <h1> html Tag
  • Ctrl – 2 – Make the current line a Heading 2 (similar to <h2> html Tag
  • Ctrl – 3 – Make the current line a Heading 3 (similar to <h3> html Tag
  • Ctrl – 4 – Make the current line a Heading 4 (similar to <h4> html Tag
  • Ctrl – 5 – Start a bulleted list
  • Ctrl – 6 – Remove any heading or list formating from the current line
  • Shift + Enter - Finish Editing

I hope that you find those shortcuts useful. Give them a  try at least, they will make your time in Google Wave a lot smoother and more productive.


  • Share/Bookmark

A very cool application of Google Wave

The Skype Journal has the story about an interesting mashup using Google Wave

They talk about a Gadget that allows users to make Skype calls from within Google Wave, which will then be recorded in a wave, with each person’s contribution to the conversation kept separate.

I have to honestly admit that this is one of the coolest applications of Wave I have ever seen!

  • Share/Bookmark

Votely Review

This is my first attempt at a bot/extension review, I hope you find it useful. Please let me know if you want me to do more of those!

If you have spent any time investigating the public waves, you are bound to have seen votely… It normally looks something like this:

Votely Unclicked

Upon Clicking on the plus (or minus, if you disliked the wave you found it in), it would transform into this:

Votely clickedWell, you might not have been aware, that in addition to recording how many people liked the wave, it also kept a database of the most popular public waves, which you can see at the waverz website.

Votely is not a simple extension, but rather a combination of extension and bot. The extension takes care of the visual aspects of the app, while the bot handles the communication with the site. in order to add votely toa wave, simply add the user wavevotely@appspot.com, which will then automatically add the extension to the initial blip of the wave.  You should really add votely only to public waves, although there is nothing stopping you from adding it to private waves

The Votely site offers an RSS feed of the voted on waves, as well as the ability to view the most recently voted on, and the most popular waves.

Votely is a useful little app to keep an eye on the Wavesphere. My only objection is that its current look and feel does not match wave completely (at least for me).

I do think that there is room for expansion, for example, being able to see the most popular tags would be a nice addition to it, and a dedicated wave (perhaps in addition to the site) with the results would be nice.

  • Share/Bookmark

Wave was Down

Wave was down earlier today, which gave us all a chance to see the wave down image:

Wave Fail

  • Share/Bookmark

Google Wave Searches

Search is how Google got started, so it is hardly surprising that it plays a big part in Google Wave as well. Through search, it is a lot easier to manage waves, as well as looking up information in waves.

Some helpful Search Parameters

I have taken these from the Search Cheat Sheet wave, which still has plenty more. This is simply a list of those that I think would be the most useful.

The basic way to search is by typing in a keyword or a phrase, which will return any waves that contain the word or phrase, either in any blips in the wave, or in the title of the wave. For it to be really useful, excpet for very general searches, I would recommend combining it with some of the other operators, listed below:

Specifying Where to Search

  • title:[keyword] — finds waves which have [keyword] in the title. Most of the time this is more useful for finding relevant waves.
  • caption:[keyword] — finds waves which have an attachment where [keyword] occurs in the caption. I have never used it myself, but I guess it could have its uses

Status

  • is:read — finds all read waves.
  • is:unread — finds all unread waves
  • is:unmute — finds all waves not muted
  • is:note — finds all waves which have you as the only participant and contributor, you can use this for documents that you are working on, or to leave notes to yourself.

Participants

  • by:[address] — finds waves from the participant identified by the address, you can also use from:me to find all the waves you have initiated
  • with:[address] — find waves with a specific person (or with:public, which returns waves open to the public.)
  • only:[address] — finds waves to which only the participant specified by the given address contributed (the wave might have more participants, but this is the only one that has actually added something to the wave)

Date Search

  • past:[date term] — finds all waves in the last period.
  • previous:[date term] — finds all waves in the period before the last period.
  • before:[date term] — finds all waves before a certain period.
  • after:[date term] — finds all waves after a certain period.

which can be combined with date terms:

  • day
  • week
  • month
  • year

So, you can write, for example: past:4days, or even past:4d, or if you prefer after:10-dec-2008 (which would bring up everything, since wave did not exist then). Alas, after will not bring unwritten waves, in case you wanted to see what you were planning to write.

Personal Setup

  • in:[folder name] — find waves in the folder with the given name. For example, in:inbox.
  • in:[search name] — find waves in the saved search with the given name.
  • is:unfiled — find waves which have not been moved to a user folder.

Tags

  • tag:[tag name] — finds waves with the tag [tag name]. It will also find tags that have a portion of that tag in them, for example a search for tag:moderated will return waves that have tag:reply-moderated as a tag, as well.

Saved Searches

It is possible to save any search as a saved search, and even apply filters based on search parameters. This is useful in order to keep all the waves for a single project together, just give them all the same tag, or to find the waves that were updated recently.

Another idea is to set up a saved search for public waves about a topic you are interested in, for example  with:public title:”Google Wave” will ensure that you can see all the new waves about Google Wave as they are created. This works very similar to Google Alerts.

One saved search I have found useful is in:inbox is:unread, which allows me to see any waves that have been updated. I actually use this search instead of the regular inbox.

s

  • Share/Bookmark

The Developers behind the Wave

CNN.com has a very good article looking at the two brothers, Lars and Jens Rasmussen (the same two guys that started Google Maps), who are behind Google Wave. They are nothing if not ambitious!

  • Share/Bookmark

Wave Etiquette

Google Wave is a social space (among other things), and is used for interaction and communication between people. As such, certain standards of behavior will need to be observed in order to make using the Wave smooth and enjoyable for everyone. With a new virtual environment, like Google Wave, what these standards are is something which will develop over time, although certain agreements are starting to emerge.

Tthe entirety of the rules below can be summed up with “don’t be a douchebag”.

Having said that, here are some more specific guidelines, of course this will vary from wave to wave.

The Etiquette Wave is a wave giving out some rules of etiquette. This article is based on that wave and my own observations.

Standard Netiquette

These are the rules of online etiquette, already established by forums, social media and Internet Messaging systems, they apply on Wave as well.

  • Do not use ALL CAPS. All Caps signify that you are shouting, and that would be considered rude in most situation.
  • Use the same language as all the other participants in the wave. If for some reason you would prefer to have a discussion in another language, create a separate wave, and link to it from the original one.
  • When it comes to language, try to keep swearing to a minimum. Obviously, if everybody else in the wave is swearing up a storm, than feel free to join in, but generally speaking, you want to keep the discussion at  civil level.
  • While spelling and grammar are not as important as they used to be, try to make your posts and comments easy to understand.
  • Do not post promotional material, unless it is relevant (In other words, do not spam)
  • Do not link to porn or nudity, without at least warning the people reading. A lot of people are accessing wave from work, and it is considered polite to include something like NSFW (Not Safe for Work) next to a link that could be considered questionable.

Wave Netiquette

Here are some standards which are specific to wave. Like I said earlier, everything is still developing, but these seem to be the emerging norms.

  • The person posting the initial blip (the first blip in the wave) is generally considered the go-to person for etiquette decisions. They sometimes chose to set explicit rules for the Wave, in which case any participant to the wave is expected to follow them. At the moment, there is no way to enforce any of these rules. If there is any doubt, you can always ask the person for clarification in a blip. The Moderation tags (as defined in this wave ) are sometimes used to indicate what sort of permissions the wave owner wants to give to the participants.
  • Do not link to non-public waves from public ones. This is just annoying, since the people who are on the wave already know about it, and the people who are not will just get an error.
  • If a wave is private, do not make it public, without the permission of the owner of the wave.
  • Warn if linking from a private wave to a public one, since anybody viewing the public wave gets added to it automatically, and some people would prefer to keep their google wave ids private.
  • Keep disagreements, especially heated ones, to private blips
  • Do not add bots or gadgets to a public wave, unless you are the wave starter
  • It is normally considered polite to remove any empty blips you see, if they are older than about an hour (they are often produced by mistake)

Developing Areas

There are still some areas where there is room for discussion, such as:

  • When is it Ok to invite other participants to a private wave? – There is some work being done with this in the Wave Classification Model wave (link to wave, will only work for those with a wave account), which classifies how open the information in the wave should be.
  • When is it Ok to edit somebody else’s blip? – The current norm seems to be that the initial blip is open for editing (although in some waves the owner can declare it not to be), since that is normally the document that is the focus of the wave. Lots of people support editing down a blip discussion to summarize it, although you should generally ask, in order to avoid causing offence.
  • When can you change the tagging structure of a Wave? – According to the etiquette guide, you should not, but in practice people seem to use the tagging functionality without any limitations.
  • When to use inline blips, and when to use a simple reply? – I support using inline blips for simple responses, that do not really add much to the discussion (things such as indicating agreement, without adding anything else  to the discussion), or when you are replying directly to another blip. In practice, this is one of the areas where there seems to be no norm yet.
  • Is it ok to interrupt someone while they are typing? – Should you wait for somebody to finish before you stat responding to their post? It seems that most people do wait, although I have seen some cases where they do not… I would think that the principle of “don’t interrupt” should be adhered to even in the wave.

We are all still trying to figure out how to best use Google Wave. In order to do that, we will also need to figure out how to use it to communicate with each other. On the Wave, like anywhere else, I think we should just try to treat each other with respect, and the rules of behavior will emerge from that.

Etiquette Wave

Wave Classification Model

g

  • Share/Bookmark

I have invites!

I am now the proud owner of 6 invites for Google Wave, so if you would like to join Google Wave, please post a comment with a good reason why I should give it to you, and it will be yours.

  • Share/Bookmark

Wave Defacement

I just found my first case of wave defacement!

I was innocently perusing the public wave about votely (an extension which I plan to review soon), and I clicked on the link. Instead of the expected list of top public waves i expected, I was greeted by some really nasty porn.. . (don’t worry, i do not plan to review it).

I then realized that the link had been changed (I have used it before, and my first theory was that the destination site had been hacked).

I changed the link back to what it should be, and remembered the playback function, which I had not had reason to use yet, and I tracked back to see who the culprit of this dastardly deed was! It took me a bit of scrolling back and forth, but eventually I managed to identify when the link changed (as well as another changed link I had missed).

Soon after I announced my findings in the thread, the person who did that apologized, saying he had been upset with the person who started the wave, and changed it in anger.

So, everything was Ok in the end… But this incident did serve to illustrate a problem with the wave as it currently stands: The fact that anyone can edit a public wave… And in the cases of links, the editing need not be obvious to the casual glance. Like so many other people, I think Wave really needs some moderation capabilities.

Ironically enough, I had already been brainstorming a post about Google Wave Etiquette, so expect it sometime next week.

  • Share/Bookmark
Subscribe to RSS Feed Follow me on Twitter!