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.
In Post on 2010-01-31 by Joshua Tagged: blogging, client, embed, future, interface, opensource, use case
Want to share a public wave with someone who hasn’t jumped on the Wave bandwagon? Need to publish a Wave in a way that keeps it safe from editors and wanna-be trolls? How ’bout this Wave Reader that takes a wave and displays it as a web page without the reader needing an account.
In Post on 2009-10-27 by Joshua Tagged: email, extensions, future, money, preview, roadmap, store
The Next Web attended the Google Wave GTUG (Google Technology User Group) meetup in London where Lars Rasmussen and Stephanie Hannon (the two responsible for Google Wave) gave a presentation on some upcoming Google Wave APIs. James Glick from The Next Web has included a dot-point summary of the most important parts, a few of which I have included below. Read his article for even more juicy inside information.
To cut a potentially exhausting blog post short, a summary of snippets from their presentation include:
Extension gallery to be fully up and running in months with a wider collection and sharing functionality.
An extension store is planned where developers would be able to display and charge for apps.
[… snipped …]
Google Wave will be able to be deployed within networks and intranets for organisations and companies to use internally.
Although it has been requested by a substantial amount of preview users, there are no plans to intergrate Gmail or any mail with Google Wave. The APIs though, will provide developers with the ability to do it in the future…
Read the article at The Next Web for more
The rest of the items on Glick’s list show Wave team is obviously committed to improving the experience for everyone. The four items I’ve included above highlight for me the potential for Wave to grow beyond the bounds of what Google can achieve and put it firmly in the hands of developers who can make it a thriving, useful tool. If Wave can ever dethrone email as the default form of communication, it will be because of these for things: The ability for developers to extend it and make money from it, for businesses to deploy their own secure versions, and for Wave to send and receive email. Although it looks like the Google team don’t have plans to bake email support in, I am confident it will not be long before such an extension is built and available.
“…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.
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
