Subscribe

Google Wave Pulse – Permissions

11/19/2009 | By Fernando Fonseca
Google Wave Pulse - Permissions
1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)
Loading ... Loading ...

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)

More Articles By Fernando Fonseca

Author: Fernando Fonseca

Co-head of PublicSpaces, a company and netlabel based in Barcelona, Spain, Fernando is a serious Douglas Adams fan, cook, tech and gadget geek, strategist as well as an experimental musician. Lover of red wine , gin tonic, sushi, Monty Python and Karaoke, Fernando is involved in many new-media art related projects, (h)activism, and GoogleWave. Send him a tweet in klingon at @fjfonseca: you will make his day.


11 Comments

Jon

November 19th, 2009

I think openly public waves (and the resulting planned permissions) are redundant. Blogs are a much better platform.

[Reply]

Fernando Fonseca

November 19th, 2009

Hello Jon, thank you for your comment.

I think that what we are seeing are users trying to “import” old paradigms into a new one. I do hope that the levels of control become much more sophisticated to reflect what real life relations and interactions are. I can’t agree with you when you say that “blogs are a much better platform”. The level of interaction that you can have in real time on a Wave can’t be implemented in a blog.

[Reply]

[...] the whole story here: Fernando Fonseca aggregated by [...]

Ray

November 19th, 2009

Although at the present, I agree with Jon that Blogs are better to present information, I suspect that concept may be changing.
Until the waves are universally accessible (meaning a majority of the web users have accounts or other means of access), I don’t see the point of creating new data for a wave.
When they do become more visible, then permissions are essential. Hopefully, blogs can be merged with waves effectively to present info to all.

[Reply]

haydar

November 19th, 2009

ı need to googlewave invite for my haydaryildirim@aol.com address

[Reply]

Kerri

November 20th, 2009

The public waves are an interesting way to watch and have a conversation. I see them as more collaborative than blogs.

[Reply]

Marc B. Poblet

November 23rd, 2009

This is interesting.
So, say, will I be able to make a wave, add public@a.gwave.com with ‘commenter permissions’, have everyone able to comment on the wave without editing my content, and then be able to ‘upgrade’ users I deem trustworthy enough to editor level?
That would be neat…
(Also, would be great for the HelpDesk… while the FAQ would have read-only permissions by default… hmmm…)

[Reply]

Fernando Fonseca

November 23rd, 2009

Hey Marc! Yes that is exactly the plan and we sure could use this *right now* at the Wave HelpDesk and Wave FAQ. The only trouble is that we have to wait for it to be implemented. cross your fingers.

[Reply]

Marc B. Poblet

November 23rd, 2009

The question is: what will happen with existing waves (will all users retain editor permissions)?
Also, will user permission levels be ‘downgradable’ (that is to say: what I can give, I can take away)? If that is so, will all ‘editors’ have the same power, or will ’seniority’ rule?
Would all that be good? Or bad?
Ah, questions, questions, only practice will tell…
(Can’t wait…)

[Reply]

Stanto

November 25th, 2009

I’m surprised to see Google Wave being solely compared with blogs in the comments here and not broadened to being used in conjunction with, or replacement for other social media tools we currently have.

For myself I see it as a gradual update and incorporation of the following concepts:
- Newsgroups
- Forums
- Twitter
- E-Mail
- Potentially, instant messaging, but the interface would need to be changed or cut down.

However, for ‘blogs’? No. Not as a replacement; consider it a supplement. There’s already the ability to link it with ‘Blogger’ and would add an element of dynamic content.

Regarding the permissions system that’s being implemented. It’s about time, and these type of abilities are common across forums referring to ‘guests’ or ‘registered users’ being able to post, edit and alter others’ posts.

[Reply]

Stephen Tsirtsoni

December 2nd, 2009

Hi,

I am experimenting with public waves as an alliterative to comments and have my first test one published at http://www.involvednews.com/Global-News/Asia/Iraq/iraq-enquiry.html.

The primary issue i have for taking this site wide is the fact that people can add bots to the wave, I can’t ban people if they leave indecent content, cant stop them from deleting stuff, embedding stuff.

The interactivity that google Wave could bring to my site is immense, however the lack of control that comes with that is also significant

Do you know if these issues will be address or should I stick with Friend connect for now?

Regards,

Steve.

[Reply]

Leave a Reply

Anti-Spam Protection by WP-SpamFree

Related Posts

Check out some more great tutorials and articles that you might like.