I'm a programmer and a certified tech geek, so of course I'm playing with Google Wave. I say playing, because there isn't much you can do at this point on wave except play. This is partly because there aren't enough people with access to wave yet that communication is useful. But more importantly, there simply isn't a rich enough feature set yet to commit to using it for anything important. Much has been said elsewhere about what essential features wave needs to have be ready for primetime, including :
- administrative access control - This is needed over waves so that people can leave, be removed, have their write access restricted or monitored. Essential, showstopper, I assume google is working hard on it right now.
- integration with email - Wave may want to be an email-killer but that won't be possible without connecting fully with email and showing wave is better, which it may or may not be. So complete back and forth integration with non-wavers via email is essential. If google isn't working on this, well, they are miscalculating.
- speed and stability - annoying, but wave is still in preview so this will get fixed.
All these things can't really be fixed until Google decides to do it. But there are a number of other things wave could have right now if developers put their minds to it and made some useful robots, well ok, maybe next week.
Robots in wave in simply little applications that get a user address and can be added to waves to alter the content. This may sound strange but its actually a very powerful idea. Some robots that already have been created add results from twitter to a wave, pass blips (atomic portions of a wave) back and forth to some email address or blog, add smiley faces and convert urls in the text to http links.
Robots seem to be relatively easy to program and are easy to add. Any content a user can see in a wave, the invited robots will see and they can alter it as well. I am interested in making some wavebots of my own but alas it looks like the sands of time will delay that for a while. The problem with the wavebots that exist so far is that most of them are toys and don't do anything actually useful. I have an idea or two for useful wave robots that I think would be a lot more useful. If you are so inclined and skilled please make these forthwith and let me know. If you really hadn't thought it until you read this post, consider it a gift and cite me as your inspiration. But what I really want is these bots in my contact list, yesterday!
We need a robot to highlight and alter keywords in the text so that the document can be used for notetaking and brainstorming. For example:
- TODO, MOVETO(doc), LOOKUP, address, recipe, call, -> becomes an arrow , ? becomes highlighed to denote an as yet unanwered question
- "TODO text...." could become a check box with the text following it. Hopefully even checking the box could cause a formatting change?
- the robot could create a blip at the bottom that shows all the mappings and lets the user alter them or add more
- can you save an instance of the robot as a separate contact? The emaily robot seems to imply you can. If so, then an instance of keywords mappings could be saved in the contact book and readded to later waves. You could have one annotatebot instance for psych class, another for your journal, another for recipes.
One major problem with wave right now is you can't collapse parts of a wave and see the structure or the big picture. Replay is cute but frankly its useless for document editing. Its only useful for introducing someone to the flow of a conversation. I see Wave as much more of a collaborative document editing platform. Like Social-google Docs on steroids (without the access control? sheesh). Replay will play a minor role in this view, since the current best doc is what really matter. The fact that there is no way to collapse all repsonse blips or view a timeline is a huge gap. I don't know if the API allows it, but it might be possible to create a bot that hides or removes parts of the converation below some level in the tree, or creates a summarized copy of the wave that can be perused to get the idea, with links to the full detail in the original wave. Sort of like a table of contents with hyperlinks. That should be doable.
This one would be great. I am already experimenting with using wave for a research journal. It seems ideal, it automatically timestamps each blip, lets you respond and annotate as you go. Lets you go back and edit. Again, collapsing by date would fantastic here. But a wavebot could help a lot with journalling. For example, a bot could take each new blip added at the bottom as a reply and cut and paste the text in to the first main blip so that their is a final formatted document. Each new day could be automatically titled and all new blips entered that day would be appended under that date. Edits of previous blips would not get moved and the header date wouldn't change. This gets around the limitation that the timestamp on a blip indicated the last edited time, not the creation date. Which is exactly what you want for geenral document editing. But in a journal you also want to know when it was added since edits are largely minor. Any robot that simply turns some key word into the current date or timestamp, with formatting options would be an even simpler solution to this.
The great thing about these bot ideas is they could be combined easily simply by adding each bot to the same wave. Then you could have a journal that annotes TODO comments to format them differently, keeps track of the creation date and lets you explore the document at an abstract level.
I don't know, is it just me, or wouldn't these kinds of bots be a better use of your time than developing another smiley bot or eliza-hack chatbot or voting gadget. These are productivity basics that wave needs so it can crawl as a useful tool before it flies as a social media, 21st century email killer.
Those are my ideas. If you have already made something similar, let me know. If you haven't, get working on it, before I do! If its good, then I won't have to do it myself.