Etiquette on Wave to is too complicated

One of my favorite blogs on Google  Wave (The Shiny Wave)  have picked up a Wave with Etiquette on Google Waves. The interesting aspect is that when you are working with somebody else you can get a lot of noise or disturbance. Many times when you are collaborating with a lot of other people you are missing the rules for the conversation. This etiquette is a way to make some of the rules more global.

With no Access Control Layers (ACL) or rules it is not possible to ban people from editing any part of the Wave. That mean if you have public waves or to a group waves you need to hope your users does not make any changes. So Google Wave is build on trust and you need to trust the people in order to make posts go nuts.

There is a good judgment of people not to mess up any documents. An example is the The Declaration of Independence, where it would look really strange if anyone changed on the wave. It seems like nobody are vandalizing the document. On a side note the document and users seems to originate from, which must be a hosted domain. So you can share from hosted domains to Wave. Can anyone edit in the Wave hire?

The blog on the Shiny Wave mentions a Wave By Elliot Cable, which talks about the different types of moderation. All waves should med have on of the following tags. I would suggest you to go to the wave to get the full idea of each type.

  • tag:moderated: is the mildest form of moderation and therefore give most discussions.
  • tag:edit-moderated: is where only the initial blip should not be changed but the rest are more relaxed.
  • tag:reply-moderated: is where the participants should collaborate in a separate Wave, the Wave owner will then transfer the content to the Wave.
  • tag:locked: is when you don’t anybody to edit in your Wave, so why use Wave?

One problem is that you have to understand the difference between those four levels of interaction. If you have not written the rules or been a part in the generation, you will not know how to see the difference and what you are allowed to to on the current Wave. This could stop people from taking a part in the discussion.

Most if not all of the rules described hire should be possible to implement programmatic. It would make it much easier for users to implement the changes suggested. Then it is just to make the changes a part of the ACL for the Wave protocol, which obvious also needs to support the changes.

Bookmark and Share