After an enthusiastic introduction it seems the frost has melted on this pumpkin. Google has not stopped rolling out the developments, with new features such as “Read only participants”, and “Restore from playback” (http://googlewave.blogspot.com/2010/01/new-features-read-only-and-restore.html) and “Waving with groups” (http://googlewave.blogspot.com/2010/01/new-features-read-only-and-restore.html); though it is not clear what happens if some of your group are not Wave users. But, it is interesting that the Wave team do not appear to replicate the Wave blog (http://googlewave.blogspot.com/) in a wave. These features seem to make Wave more like a blog (read only participation) and a wiki (version control and groups). Why not make a public wave that anyone can sign on to but not edit? Allow them to comment but not create new slugs? Well, lots of reasons I can think of, but the point is that blogs and wikis do their jobs well. As Wave converges on these applications will it do itself out of a role? The injunction to “Be bold!” (http://googlewave.blogspot.com/2010/01/be-bold.html) suggests that people aren’t, or rather, where does Wave afford boldness?