We have begun testing remove participant internally and hopefully it will hit externally within a month
Lars Rasmussen, one of the lead Wave developers.
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.
Set suitable expectations. Despite the months of buzz, and blogosphere– and Twitterverse-wide clamoring for Google Wave invites, the product is still in preview and has some rough edges. Therefore, it does all parties good to be realistic, even if everybody is psyched to be the first kid on their block to use it on a live project.
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.
“…developers have asked us a lot for a market place where we’ll help them sell their extensions to our users including a revenue share so we’ll also make some money from it.
“I’ll be very surprised if we don’t go down that route.”
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.
I predict this will mean a lot more extensions will be made open source or free. Of course it’s highly dependent on the quality and user experience of the store. If a developer can make an extension open source, but still make it available in the same marketplace many will choose to do so.
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.
I use portable Firefox for browsing at work with a modified user-agent (pretending it’s Internet Explorer, of course!) and Google Wave keeps alerting me the browser is not supported. To bypass this annoying check, go directly to https://wave.google.com/wave/?nouacheck. Of course, some browsers just can’t handle the storm: in my experience so far, Opera 10 fails to load Wave every time with a nasty error.
I believe that people who don’t see what Google Wave is for are simply looking at it from the wrong angle. Wave is not a social tool. It’s not Twitter, it’s not GTalk, it’s not Facebook. It was never designed to appeal to the crowds of geeks who are currently trying it out. Wave is built for the corporate environment. It’s a tool for getting work done. And as far as those go, it’s an excellent tool, even at this very early stage.
This in no way represents a new social networking tool, and I think using it as such would be rather cumbersome. The beauty of it is, the user can control the experience and dictate its purpose.
All of this freedom—being able to add to, edit, or delete anyone else’s blip in any wave—doesn’t just lead to accidental destruction but concerns about people “putting words into their mouths”, and raises a number of trust issues for many.
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.
What is amazing is that Google has developed a real-time communication framework that can work in a federated environment.
People aren’t getting it right now because they’re expecting the beta to all be about polishing the User Experience. But it’s not about polishing: it’s about defining.
Email chains—the closest thing to waves at this point—are all fun and games until someone CC’s the wrong person, like a parent, relative, boss or overly-sensitive co-worker.
Five Reasons to Be Terrified of Google Wave
A refreshing look at some of the downsides of waves as a new communication medium.
Can a small startup — made up the two co-founders and one employee working in a studio apartment in Silicon Valley — go head-to-head with a powerhouse like Google on something as revolutionary as the re-invention of e-mail?
Can a startup challenge Google on the re-invention of e-mail?
Are tools like CC Betty approaching the re-invention of email in a more practical way?
View more by category: Link (31), Quote (17), Post (16), Media (11), Status (6). Or by month: March 2010. Or visit the Complete Archive.
aves