Google Wave Pulse – Permissions
|
|
|
|
Google Wave is here and much is being (well) written about it by my fellow Bit Rebels. (Have I told everyone how honored and proud I am of being a part of this amazing team?)
But where is Google Wave heading? What trends are we seeing? What can we all expect? On a weekly basis, I will be making a roundup of all the information, gathered directly from Google’s Developers and team leaders, that point to the future of the e-mail killer.
This week I will be writing about Permissions.
Google Wave allows you to start public waves where everyone can join in and participate. To test the new service there is nothing better than this but, as with everything that is fully open to the world in general, things sometimes take a wrong turn. In the case of any public wave, a wrong turn can be very frustrating for those that have spent their time adding content into it: the content is lost and, to recover it, users have to pray to the Wave’s gods that the playback function is working properly. (It’s a preview, remember? It usually just makes the wave crash)
It didn’t take long for users to start asking for some kind of control over the Waves that they created: They wanted to be able to choose who could make what inside a Wave, they wanted to be able to turn a public wave into a private Wave, they wanted to be able to make a Wave read only, etc. At the end of the day what Wave’s creators want is the same kind of control that a blog admin has. And guess what? The Google Wave team is going to give them to you.
On a conversation with two Google Wave Development Team Leaders, in a Users Focus Group in Madrid this week, the issue was addressed and here are the plans. In the near future there will be three levels of permissions:
- read/write – What everyone has now: This user will be able to add new participants in read/write mode, commenter or read only modes
- commenter – The user will be able to add new blips, edit own blips and add new participants in commenter or read only modes
- read only – This type of user will be able to read but not modify the wave and will not be able to add new participants
As soon as these features are implemented the global Google Wave experience will change for everyone and we will see more content being added to Google Wave.
What do you think? Did this lack of control got you thinking before you produce public content? Will the future permissions be enough? What would YOU like to see implemented? Leave your comments here or come to this wave to discuss it. (Google Wave link: you need an account to be able to access it. Need an invite? Bit Rebels is giving 10 invites to the most creative of our readers and followers. Read all about it here)






