| | | |
|---|
| Account roust | If you open wave.google.com signed into some other account, Wave may indicate that your account has been activated yet. Sign into the activated account at google.com/accounts, and try again. (Dr Wave seems to think everyone has only one Google Account!) | | |
| ACL-free zone. | Wave does not [yet] have a way to restrict adding participants or participant privileges within a wave. Everyone can do anything the creator can. However, access control is known to be on the release roadmap. | | |
| Auto Search | Wave does not [yet] allow launching a Saved Search automatically when new waves are first added to the Inbox. If there are Saved Searches that you would like to run routinely, you must launch them yourself. <snap/> | | |
| Command babble | The commands do not include the robot's name. If multiple robots are added to a wave, hypothetically, it may possible for two robots to recognize the same command. Caveat emptor! | | |
| Contact inconsistencies | Wave is inconsistent in its handling of Contact attributes. If you add your own picture to a contact's record, Wave will use it instead of the contact's own profile picture. (You record overrides the contact's profile.) (As of the Nov 24th release, Wave ignores other changes to your contact record, and it will always use the name from the contact's own profile. Also, Wave will not pickup a contact's website from his or her profile. You have to enter those attributes into Google Contact yourself before they appear in Wave. (Though, they may show briefly when the contact is first added.) Other Google properties, like Gmail, do pickup changes you make to the contact's record, overriding whatever is in the contact's own profile. | | |
| Disppearing public. | When you add public@ to your contacts list, Wave might indicate that “User does not have a Google Wave account.” That's OK. Hit (Enter) and Wave will let you use it anyway. (Unfortunately, Wave will also remove public@ from your contacts list the next time it loads, so you have to add it again later to create another public wave.) | | |
| Folders | Sadly, Wave does not [yet] support Gmail-style labels or Gdocs-style shared folders. (We're told a final decision has not been made. It seems that Lars likes folders, and so the team is giving them a try) | | |
| Gears not ominpresent | Gears is not available for all browsers on all operating systems, most notably Safari on Mac OS 10.4. Gears is not required for normal operation. | | |
| Group two-step | After joining a Wave-enabled Google Group, you may need to refresh or restart your browser in order to post to the group for the first time. | | |
| Hide all replies | There is a Hide all replies action, but it is not yet implemented. | | |
| Lack filter actions | While a public Wave feature roadmap is not available, hopefully, Team Wave will add many more Filter Actions, including goodies like automatically tagging waves, moving wave to folders, applying any other standard action, or maybe even exposing an event that would let a robot scan newly added waves. | | |
| Link editing | If the link is followed by a space or punctuation, and the Link button doesn't engage, press (Shift+Left Arrow) to move the selection into the text. | | |
| Lost attachments | It is easy to accidentally delete an attachment. Since there is not [yet] an Undo or Cancel action, the only recourse is to upload it again. | | |
| No Spelly options | While Wave excels in extensibility, there does not seem to be a way to add a custom dictionary to Spelly, adjust the way it works, or remove it from a wave. Likewise, there is no way to keep Linky from linking anything that looks like a website (even if you don't want it linked). | | |
| No Undo | Since there is not [yet] an Undo, Cancel, or Rollback action, once deleted, the only way to recover content is to invoke Playback and copy the content by hand. Support for Undo is known to be on the way. | | |
| One way drag. | Trying to drag a contact from the Participants panel to your Contacts doesn't work. You have to click. :( | | |
| Participant pile. | How many participant pictures can be displayed depends on your screen resolution. If all of the participants can't be displayed at your resolution, the end of the list scrolls off the screen and cannot be accessed [yet]. You may not be able to determine whether someone is already participating in a wave (without using playback to click through every revision). | | |
| Picture missing. | If you are adding a Wave participant directly to Google Contact, be sure to list the Google Account associated with his or her Wave account as the first email on the list. Likewise, if a contact's picture doesn't appear, be sure the Google/Wave account is the first listed. (Known issue.) | | |
| Picture yes, name no. | If you setup a new picture for a contact, Wave will use your selection, but it will continue using whatever name or nickname the participant uses in his or her own Google or Wave Profile. (Go figure!) | | |
| Presence (may be fixed) | Presence may be disabled or not working correctly. (Known issue.) As of Nov 24th, it is working again. | | |
| Privacy Policy. | The Privacy Policy depends on participants being able to remove themselves. (Known issue.) It also seems to be independent of moving a wave to Trash. | | |
| Profile flash. | When the contact is first added, Wave will display the website and phone number (if any) from his or her Google Profile. Later those details may disappear if they are not included in the Google Contacts record. (Confusing, ain't it?) | | |
| Remove yourself. | It is not [yet] possible to remove yourself or any participant from a wave. (Known issue.) | | |
| Remove yourself | For human participants, including your own self, the Remove action is still disabled. (Known issue.) | | |
| Requests nevers used. | Requests may come into play when other Wave servers become available. | | |
| Search / Folder name overlap | aved Searches and Folders share the same namespace: We can't use the same name for both a Folder and a Saved Search. (If you try, Wave will quietly ignore the change.) One workaround is to use naming conventions to distinguish folders and searches. For example, all searches might start with the prefix “do” and all folders might start with the prefix “my”, as in DoWaveHelp (search) or MyPinned (folder). | | |
| Trash | The Wave trash retention policy has not been defined. | | |