Lars Rasmussen on Google Wave via CNET UK.

Told you so

Lars Rasmussen talks to CNET UK is a post from First Waves

This is exciting. More detail up soon.

A quote from Novell: Demonstrating Inter-company Collaboration is a post from First Waves

In a Wave entitled “Google Wave User Black List”, Lars piped up to offer advice on the best way to avoid and take action against known trolls and abusers and offered the above titbit about the imminent release of the ability to remove participants from Wave.

This is big news for Wave, and one of the most important features noticeably missing from the Google Wave interface. Wave abuse, trolling and destruction are all unavoidable realities of using Wave at the moment, and although usually infrequent, can significantly lower the enjoyment and tone of a Wave. Unfortunately, while every one can agree that a removal tool is necessary (and there’s an unusable greyed out button to show that the Wave team think it’s important as well) it hasn’t been implemented yet. One of the reasons for this delay must be the extraordinary thought and research that must be put into such a feature, to make certain that the feature itself is not abused. Care must be taken to see that users who are added and then removed retain some control of their legitimate contributions within context. The ability to remove people from such a collaborative space is an enormous can of worms, and one that most people would agree is important enough to get right the first time.

The wave that Lars opened up on was created to list known trolls and spammers.

• Once you have added public with full access, making an abuse user read-only is more effective than removing them from the wave will.
• There will soon be a way for you to report abuse directly to our internal abuse team
• The feature you are asking for: block a user from a particular wave and all future waves created by you is exactly right but it will take us many months to get there…

This is tremendous news, and along with the ability to make participants read-only, and even score them with karma give users a powerful arsenal to shape the Wave experience the way they want.

Hat tip to The Shiny Wave: Google Wave User Black List.

Lars: Remove Participant Feature due “Within a Month” is a post from First Waves

6 Tips For Using Google Wave On Your First Project.

This is the first of six excellent things to keep in mind when using Wave for the first time, let alone on a project. Wave is full of potential, but people seem to forget it’s still just getting off the ground.

I love that people are using it for projects already.

Expectations is a post from First Waves

Google Wave to have application store | News | TechRadar UK

This will be a very important development in the success of Wave. The iPhone has grown enormously by making high quality apps simple to pay for and receive. The key difference for Wave will be that the protocol is open for anyone to extend, and the main client (the Google Wave interface) is web based.

Keep in mind too, that over time other clients will emerge that will access the Wave protocol, and it will be interesting to see if the marketplace will extend to such clients.

A Wave Extension Market Place? is a post from First Waves

gxg at FORS Shortcuts and useful searches already, but the information about URLs is important and useful.

One take-away from the section on searches is the reader tip published at Lifehacker about limiting waves to certain languages.

3 Things you should know about Wave is a post from First Waves

The problems Wave solves is a post from First Waves

Google Wave Is The Future of Real Time Collaboration

Wave and Real Time Collaboration is a post from First Waves

I’m certain that this will not be as big an issue in later iterations of Wave, and there are already some safeguards in place. Nevertheless, it is a real issue to watch as Wave matures.

The Freedom Problem is a post from First Waves

What You’re Missing About Google Wave is a post from First Waves