All Quiet on the Wave Front

Yes, I know that I deserve to be shot for the many puns contained in that short title, but I just could not resist.

I have noticed for the past week or so, that wave has been a  lot quieter, while my inbox used to be full, now there are just a couple of updates a day. This is strange, since I would expect an increase in activity, especially since Google has been releasing a lot of Wave invites lately.

Either it is simply the holidays, as people tend to shift focus away from technology to family at this time of the year, or it is the fact that people are getting over waving for the sake of waving, and are starting to use wave differently.

I am not sure which one it is, but we will see if the usage goes back up in January. Any ideas why wave has been so quiet? Please comment if you have any thoughts on this.

  • Share/Bookmark

Wave Spam

Today, I have seen two instances of wave spam, in a single day. One was in a public thread that I am subscribed to, in which somebody simply added a blip saying: “I wrote an article about google wave… Go see it at http://*****”… I consider it spam, since he did not even say anything about how his article would be relevant to the discussion in any way… I did not even bother reading it.

The second one was much more direct… Another user created a wave promoting a security business, and invited a bunch of people to it (including yours truly). What makes the second one strange is that the product is available only in a specific area, which means that the vast majority of people he invited are nowhere near the target market.

I pretty much expect spam to bloom on the wave, but it it still saddening to actually see it.

  • Share/Bookmark

The Google Wave API

As many of you know,  Google Wave has an API that enterprising developers can use to create their own bots and extensions. I have recently started playing around with it, so here is my short introduction to it.

At the time of this writing, the Google Wave API is supported only for Java and Python. Google seems to be supporting Python a lot, and apparently a large amount of their infrastructure is implemented in it. Java support seems to have been added mainly due to its popularity.

I am sure that other programming languages will be supported soon, either by Google itself, or by third parties providing wrappers.

Although I am a Java programmer, I have decided to use Python for my own projects, partially as a challenge, and partially because I think that the Python API is more likwly to be better tested.

From my reading, the bot API is very much event driven, basically bot writing seems to consist of writing event handlers for events such as people joining the wave, blips getting edited, etc. Apparently the first blip is treated differently from the rest of them, which is something I will have to keep in mind as I work on my Uberbot.

At the moment, all Google Wave apps need to be hosted with Google, on the appspot.com domain, although I hear that there are plans to allow other apps at some point in the future. To do so, you will need to get a Google App Engine account. You will also be limited to 10 apps on an account.

For more information, you might want to read the Wave API FAQ. So far, I have worked through the bot creation tutorial, and it works fine, but due to personal issues, I have yet to actually write any code of my own, I will post the occasional update as I work on my bot, and hopefully unveil it next year.

  • Share/Bookmark

The Death of Instant Messaging

An observation in an earlier article got me to thinking about how Wave stacks up against more traditional Instant Messaging applications.

Wave is more immediate that traditional Instant Messaging, since seeing somebody typing in real time allows me to see what they are saying before they complete the full sentence. Of course, this could lead to problems as people jump to conclusions before a thought is finished, but so far, this seems to be a good thing.

The most important thing about Wave, which puts it head and shoulders over “traditional”instant messaging, is the fact that the conversations are retained, and easily searchable, while IM systems often have this feature (GoogleTalk does, for one), with wave it feels natural and integrated, rather than an afterthought.

The combination of synchronous and asynchronous communication is one of wave’s greatest strengths, since you can chat real time with a person, or simply type them a message for later, depending on time constraints, and what kind of thing you are in the mood for. You can even start typing a message, and if the person sees you, the exchange can turn into something far more immediate… It feels far more natural, at least to me.

Of course, for those of you that find yourself missing the old way, there is an extension that will allow more traditional Instant Messaging within Wave.

There has been a lot of debate about whether Google Wave will be the death of email as we know it. I still do not know about that, but I am sure it will be the death of Instant Messaging as we know it.

  • Share/Bookmark

The Google Wave Links (weekly)

Posted from Diigo. The rest of my favorite links are here.

  • Share/Bookmark

An Amusing Look at Getting Started with Google Wave

Autostraddle has posted a very amusing introduction, outlining how they got started with Google Wave. Just go and read it

  • Share/Bookmark

Types of Waves

Over my time in Google Wave, I have noticed that waves can be divided into several groups, depending on the intention of the people that have created and joined them. This is my attempt for a (somewhat limited) look at the different types of waves that I have observed so far.

Chat

These are the waves in which wave is used as a chat platform. They could be either public or closed, and tend to grow quickly when public, although they just stop after a while. They tend to function more like a forum thread than an IM chat, although they are really a combination of both.

Document Creation

These waves are normally done in order to create a document of some sort, be it a book, article, specification or something else. Normally the starting blip is the document itself, while the discussion takes place below it, or possibly using inline blips in the document itself. Sometimes the discussion is split off into a separate wave. This type of wave starts showing where Google Wave becomes a very powerful tool for collaboration, although the best way of working with them has yet to be developed, and will most likely vary from organisation to organisation.

Introduction Wave

I have seen a number of those since I got onto wave, normally started by people as they join wave, and they are still trying to figure things out… Its normally a case of  ”I am on wave!… Now what?” that so many seem to experience when first joining. Normally it ends up an exchange of hints and tips for beginners, before it gets brought down by the combined weight of extensions and bots as people use them to test out what they can do with wave. They are an important first step for any waver.

Meta-waves

These are the waves about wave and waving in general… The introduction waves sometimes fit into this category, but more often they are discussions of various bots and apps, wave best practices, and the Way forward for Google Wave. A ton of those discussions are public, and considering the stage of development that Wave is in, it is hardly surprising that at times it seems that the only thing that people use Google Wave for is discussing Wave itself.

Gaming Waves

These are the waves devoted to games of various types, mostly role-playing games of some sort, although Sudoku seems to be surprisingly popular as well. In this way, wave users can play together, and chat about the game in real time as they want to.

Project Discussion

I think this is the area where waves shine, as people can use it to discuss various projects, possibly drafting relevant documents in the process. Most of these waves would be public, so it is impossible to say how many of them there are at this moment in time.

Mutual Interest Waves

There are a ton of waves that seem to act more like forums, where people gather to discuss common interest, this could be anything, I have seen gaming, anime and religion waves, and I am sure that there are many other examples. As far as I know, most of those waves are public, and if there are any private ones, nobody has invited me to one yet.

Live Event Waves

This is something that wave has learned from twitter. Basically, by creating a wave for an event (conference, sporting event… anything), people can comment on what is happening, while those that cannot attend the event directly can comment, and ask questions. I have seen the suggestion for doing this with videos (so that the video can be discussed), but I have yet to see any such waves in practice.

Personal Waves

These are waves that people make for themselves… Perhaps as a way to take notes, or maybe just to get their thoughts organised before opening the wave to the public. I would include waves made for the initial testing of bots here as well.

Dead Waves

These are the abandoned public waves… Sometimes they are just fogotten, and sometimes they have been consumed by bots, and now await the foolish waver that will mistake them for something active… There are way too many of them at the moment, with no way to get rid of them, yet.

Well there you go, my list of the types of waves I have encountered so far. Anything you would like to add? And more importantly is this division of wave types useful in the least?

  • Share/Bookmark

Napkin – Extension Review

Napkin is a very nice little Extension for Google Wave, allowing Wave users to work on and share simple sketches. This is very very far from a full featured image editor, much more suited for doing a quick sketch to explain or highlight a concept. All the parties in the wave can edit and view the “napkin”.

Using it is simple, just edit the blip it is in, and click and drag in the window to draw. There aren’t too many controls to confuse things, just the color and thickness selectors, and an undo button if you make a mistake.

Overall, Napkin is a gadget that has many uses, mainly in discussing ideas, and in communicating things which are better represented visually. I would love to see a game of charades on wave using it!

napkin

My only objection is the fact that there is no eraser function.

If you want to know more, you can check out the Project Site.

  • Share/Bookmark

The Google Wave Links (weekly)

Posted from Diigo. The rest of my favorite links are here.

  • Share/Bookmark

More invites on Offer

Well, there has been a new release of invites from the Google Wave team, and I got a whole bunch of them, so anybody who wants one, please leave a comment, and I will try to get you one! The supplies, while plentiful now, are limited!

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