Ever wish there was a helpdesk that you could use to get feedback on the problems you are having with Google Wave. Well, there is. Fernando Fonseca started one and it works pretty slick. You go to the HelpDesk Wave, post your problem or concern and the folks there get back to you. Here is the description of the Wave that they give:
Wave Helpdesk – Wavers Helping Wavers
Please enter your help question below as a reply or look at unanswered questions to provide answers and to collaborate.
This wave is moderated.
Please refer to Moderating Your Waves to understand the guidelines for moderation.
Your question may be answered already at WAVE FAQ – check it out first.
Please use Spam and Abuse reports – Wave User Black List to report any spam and wave abuse (phishing/trolls).
In order to keep this wave manageable Q&As will be removed periodically.
New and relevant Q&As will be added to the FAQ.
For informal discussions or orientation on Wave features, please go here to chat with others: Newbies Chat Room (to be updated soon)
This wave is in no way supported by or associated with Gooogle, and is maintained by voluntary users.
The only problem with this Wave that I wish the owners would fix would be to archive some of the questions that have been listed rather then just removing them. Removing them is good, it keeps the Wave clean and fresh and ready for you to ask your questions. But, sometimes you may not have a problem and are just interested in reading some of the past concerns folks had.
One thing that has been happening with too much regularity lately on Google Wave is trolls and spammers doing damage to Waves. At the Wave Helpdesk they provide a link on how protect your Wave from these a**holes. Here are their instructions:
To protect your public content and also allow public participation, follow these instructions.
A troll/spammer’s actions may then break or destroy the public participation, but will leave the protected content unaffected, and the damaged discussion can be deleted leaving the wave clean and tidy to start again without having to abandon the entire wave.
- Create a new wave.
- Add the initial content (optional).
- Add only trusted participants to the main wavelet with full access.
- Add Public (public@a.gwave.com) to the main wavelet with read-only access.
If you want to allow open participation,
- Add a reply, then whilst editing the reply add a private reply (using the blip’s dropdown menu “Private reply” option).
- In the newly created private reply add Public (public@a.gwave.com). By default it has full access. That’s required.
Note: An inline reply could be used instead of a reply.
In case that the private reply including Public with full access be spamed or victim of abuse then:
- Change the access of the spammer/abusive user to read-only
- Delete the unwanted content or use Playback/Restore
In case that the private reply become broken (for example by a troll or spammer) then:
- Take note of the username used to spam or broke the private reply.
- Delete the blip containing this private reply and add a new one.
NOTE: When the blip is deleted, a refresh or re-open of the wave is needed, as the deleted wavelet will still look like it has not been deleted.
- Add the offending username and change its access to read-only immediately.
Visit the Wave for more other information and links that they also offer on this subject.
Have you used the Wave HelpDesk? Leave us a comment and tell us how they helped you.
No related posts.
Related posts brought to you by Yet Another Related Posts Plugin.






















