[Google Wave APIs] Re: Strange treatment of wave titles
I have now submitted this issue:
http://code.google.com/p/google-wave-resources/issues/detail?id=793
On Jun 15, 7:11 pm, Joe Gregorio wrote:
> That does sound like a bug. Please log it in the issue tracker, with example
> code if possible.
>
> Thanks,
> -joe
>
> --
> Joe Gregorio
> Developer Relations, Google Wave
>
> On Tue, Jun 15, 2010 at 1:47 AM, Anders wrote:
> > And an even stranger example is when I tried to change the title:
>
> > Koreas meet with U.N. over ship's sinking
>
> > To:
>
> > Yahoo! and Microsoft to launch Internet collaboration tool
>
> > And the resulting title:
>
> > Yahoo!
>
> > Not only that. The complete result displayed in the Google Wave inbox:
>
> > Yahoo! – over ship's sinking
>
> > That's almost funny, and surely looks like a bug.
>
> > On Jun 15, 7:13 am, Anders wrote:
> >> I tested detecting changes of wave titles. The results were very
> >> confusing, but then I discovered that wave titles are treated not just
> >> as being the first text until end of line ('\n'). Instead other
> >> characters can also cause the title to end. For example, consider the
> >> wave title:
>
> >> Koreas meet with U.N. over ship's sinking
>
> >> The correct interpretation imo is to consider the whole text as a wave
> >> title. What happens in reality however is that the wave title becomes:
>
> >> Koreas meet with U.N.
>
> >> The title gets truncated at the last dot. Is there a reason for this,
> >> or is it a bug?
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Google Wave API" group.
> > To post to this group, send email to google-wave-...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > google-wave-api+unsubscr...@googlegroups.com.
> > For more options, visit this group
> > athttp://groups.google.com/group/google-wave-api?hl=en.
--
You received this message because you are subscribed to the Google Groups
"Google Wave API" group.
To post to this group, send email to google-wave-...@googlegroups.com.
To unsubscribe from this group, send email to
google-wave-api+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-wave-api?hl=en.
[Google Wave APIs] Re: Strange treatment of wave titles
And an even stranger example is when I tried to change the title:
Koreas meet with U.N. over ship's sinking
To:
Yahoo! and Microsoft to launch Internet collaboration tool
And the resulting title:
Yahoo!
Not only that. The complete result displayed in the Google Wave inbox:
Yahoo! – over ship's sinking
That's almost funny, and surely looks like a bug.
On Jun 15, 7:13 am, Anders wrote:
> I tested detecting changes of wave titles. The results were very
> confusing, but then I discovered that wave titles are treated not just
> as being the first text until end of line ('\n'). Instead other
> characters can also cause the title to end. For example, consider the
> wave title:
>
> Koreas meet with U.N. over ship's sinking
>
> The correct interpretation imo is to consider the whole text as a wave
> title. What happens in reality however is that the wave title becomes:
>
> Koreas meet with U.N.
>
> The title gets truncated at the last dot. Is there a reason for this,
> or is it a bug?
--
You received this message because you are subscribed to the Google Groups
"Google Wave API" group.
To post to this group, send email to google-wave-...@googlegroups.com.
To unsubscribe from this group, send email to
google-wave-api+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-wave-api?hl=en.
[Google Wave APIs] Strange treatment of wave titles
I tested detecting changes of wave titles. The results were very
confusing, but then I discovered that wave titles are treated not just
as being the first text until end of line ('\n'). Instead other
characters can also cause the title to end. For example, consider the
wave title:
Koreas meet with U.N. over ship's sinking
The correct interpretation imo is to consider the whole text as a wave
title. What happens in reality however is that the wave title becomes:
Koreas meet with U.N.
The title gets truncated at the last dot. Is there a reason for this,
or is it a bug?
--
You received this message because you are subscribed to the Google Groups
"Google Wave API" group.
To post to this group, send email to google-wave-...@googlegroups.com.
To unsubscribe from this group, send email to
google-wave-api+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-wave-api?hl=en.
[Google Wave APIs] Re: Public waves can be made non-public by anyone
Here is the application I was talking about: http://www.wavelot.com/ I just released a 'beta' version. -- You received this message because you are subscribed to the Google Groups "Google Wave API" group. To post to this group, send email to google-wave-...@googlegroups.com. To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en.
[Google Wave APIs] Re: Public waves can be made non-public by anyone
Ok, yeah only two participants that are needed for my application to work. Maybe a few more in the future, but I will try to keep the number of needed default robots at a minimum. Basically the idea is to have the application be like a container for public waves sorted into predefined topics, similar to a general Internet forum. And only have restrictions when they are really needed. For example, in addition to re-adding the two participants it will have a captcha for creating new waves. Otherwise spammers etc could heavily abuse the automatic wave creation functionality. Yikes! On Jun 11, 5:18 pm, Nathanael Abbotts wrote: > That's what I'm saying - people should be allowed to remove themselves - but > I didn't realise that your robot only kept two robots in the wave. > > On 11 June 2010 08:11, Anders wrote: > > > But participants may want to be able to remove themselves. So my robot > > only re-adds two robots at the moment (that are needed for my > > application to function correctly). > > > On Jun 11, 8:41 am, Nathanael Abbotts > > wrote: > > > One test you should include - check if the person removed themselves (for > > i > > > in event.participants_removed: if i != event.modified_by: add(i) ) > > > > On 10 June 2010 22:42, Anders wrote: > > > > > I have written a robot that re-adds participants. It works really > > > > great! When one of the participants that gets re-added is removed by a > > > > user the robot instantly adds it back again. Within a fraction of a > > > > second. This hopefully solves the problem with keeping the waves > > > > public. An improvement would be to be able to set a filter so that my > > > > robot only gets called for those particular robots (only two at the > > > > moment) that I want to re-add. Because as it is now my robot of course > > > > gets called every time a participant is added or removed. That's a > > > > minor problem and will only become a larger problem if lots of people > > > > would use my application. > > > > > -- > > > > You received this message because you are subscribed to the Google > > Groups > > > > "Google Wave API" group. > > > > To post to this group, send email to google-wave-...@googlegroups.com. > > > > To unsubscribe from this group, send email to > > > > google-wave-api+unsubscr...@googlegroups.com > > > > > > > . > > > > For more options, visit this group at > > > >http://groups.google.com/group/google-wave-api?hl=en. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google Wave API" group. > > To post to this group, send email to google-wave-...@googlegroups.com. > > To unsubscribe from this group, send email to > > google-wave-api+unsubscr...@googlegroups.com > > . > > For more options, visit this group at > >http://groups.google.com/group/google-wave-api?hl=en. -- You received this message because you are subscribed to the Google Groups "Google Wave API" group. To post to this group, send email to google-wave-...@googlegroups.com. To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en.
[Google Wave APIs] Re: WaveletTitleChanged event not working
Ha. I solved it by using a blip event instead. But I have changed my mind. Instead of my robot changing the title of waves it will instead change the title in the datastore. In that way users are still free to change wave titles and by updating the datastore the titles can remain consistent along with any changes made to the titles. -- You received this message because you are subscribed to the Google Groups "Google Wave API" group. To post to this group, send email to google-wave-...@googlegroups.com. To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en.
[Google Wave APIs] Re: Public waves can be made non-public by anyone
But participants may want to be able to remove themselves. So my robot only re-adds two robots at the moment (that are needed for my application to function correctly). On Jun 11, 8:41 am, Nathanael Abbotts wrote: > One test you should include - check if the person removed themselves (for i > in event.participants_removed: if i != event.modified_by: add(i) ) > > On 10 June 2010 22:42, Anders wrote: > > > I have written a robot that re-adds participants. It works really > > great! When one of the participants that gets re-added is removed by a > > user the robot instantly adds it back again. Within a fraction of a > > second. This hopefully solves the problem with keeping the waves > > public. An improvement would be to be able to set a filter so that my > > robot only gets called for those particular robots (only two at the > > moment) that I want to re-add. Because as it is now my robot of course > > gets called every time a participant is added or removed. That's a > > minor problem and will only become a larger problem if lots of people > > would use my application. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google Wave API" group. > > To post to this group, send email to google-wave-...@googlegroups.com. > > To unsubscribe from this group, send email to > > google-wave-api+unsubscr...@googlegroups.com > > . > > For more options, visit this group at > >http://groups.google.com/group/google-wave-api?hl=en. -- You received this message because you are subscribed to the Google Groups "Google Wave API" group. To post to this group, send email to google-wave-...@googlegroups.com. To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en.
[Google Wave APIs] Re: WaveletTitleChanged event not working
The idea was to prevent users from changing the titles of the waves. Because I save the title of each wave created in my application in the GAE datastore, and if users start changing the titles in the waves then there will be a mismatch between the title stored and the actual title in a wave. But maybe such mismatch is not really a problem. And perhaps it's even better to allow the titles of the waves to be modified, which is the correct Google Wave behavior instead of having my robot policing every wave all the time. -- You received this message because you are subscribed to the Google Groups "Google Wave API" group. To post to this group, send email to google-wave-...@googlegroups.com. To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en.
[Google Wave APIs] WaveletTitleChanged event not working
My capabilities.xml says that my robot is listening for WaveletTitleChanged events, yet the listener method is never called when the title of a wave where my robot is added is changed. I have spent many hours trying to fix the problem. And I have seen other people mentioning similar problems, but not found any functioning solution. -- You received this message because you are subscribed to the Google Groups "Google Wave API" group. To post to this group, send email to google-wave-...@googlegroups.com. To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en.
[Google Wave APIs] Re: Public waves can be made non-public by anyone
I have written a robot that re-adds participants. It works really great! When one of the participants that gets re-added is removed by a user the robot instantly adds it back again. Within a fraction of a second. This hopefully solves the problem with keeping the waves public. An improvement would be to be able to set a filter so that my robot only gets called for those particular robots (only two at the moment) that I want to re-add. Because as it is now my robot of course gets called every time a participant is added or removed. That's a minor problem and will only become a larger problem if lots of people would use my application. -- You received this message because you are subscribed to the Google Groups "Google Wave API" group. To post to this group, send email to google-wave-...@googlegroups.com. To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en.
[Google Wave APIs] Re: Public waves can be made non-public by anyone
As I have planned it at the moment there will be no need for the robot to remove participants. All waves in my application will be public. Including the possibility for public users to add all kinds of robots and gadgets to the waves. That will be very powerful but I hope it will not cause too much problems and mess. On Jun 10, 8:19 am, RAVINDER MAAN wrote: > An other point which may relate to this is that at present robot can not > remove participant.Any thought to deal with this issue? > > > > On Thu, Jun 10, 2010 at 6:10 AM, Anders wrote: > > I was thinking of having one robot creating all the waves in my > > application, and each time a wave is created the robot adds the public > > participant to the wave plus one or a few robots to provide default > > functionality (such as support for emoticons). > > > So when a user creates a wave in my application, it's the one robot > > that always is the creator of the wave. And each time a participant > > tries to remove the public participant or any of the default robots in > > a wave, then the robot who created the wave gets informed about that > > through WaveletParticipantsChanged() and immediately re-adds the robot > > that was removed from the wave. > > > Anyone can remove all the other participants in any of the waves in my > > application, but since the public participant is always re-added > > immediately, nobody is blocked from any of the waves and I thought it > > would be nice to allow anyone to add or remove their own robots to the > > waves which would potentially provide for powerful capabilities in the > > waves. > > > I haven't checked if all these things are possible in practice but > > that's my plan at the moment. And I don't know all the details yet. > > For example is it possible to catch an event and then consume it > > before any action has taken place? Or when a robot receives an event, > > then the action has already happened. > > > On Jun 9, 8:05 pm, Nathanael Abbotts > > wrote: > > > Yes - but the robot adding public would be able to be removed also, > > unless > > > it created the wave. > > > > On 8 June 2010 23:53, Anders wrote: > > > > > Oh, now I discovered this: > > > > > class WaveletParticipantsChanged(Event): > > > > """Event triggered when the participants on a wave change. > > > > > I assume that it can be used for catching all cases when participants > > > > are removed from waves. That would be good enough. At least until more > > > > fine-grained control has been implemented which I saw is planned for > > > > the wave roadmap. > > > > > On Jun 8, 10:44 pm, Nathanael Abbotts > > > > wrote: > > > > > If it helps - I'm working on a robot that you can use to create waves > > for > > > > > you, and it will re-add anyone that was removed, unless they remove > > > > > themselves. (This robot would have created the wave, so it cannot be > > > > > removed). > > > > > > On 8 June 2010 21:00, Anders wrote: > > > > > > > I have started developing a wave application with public waves. One > > > > > > problem is that the Public participant pub...@a.gwave.com can be > > > > > > removed by anyone, and then the wave is no longer public! Not good. > > > > > > > Another problem is that anyone can remove robots from a public > > wave, > > > > > > which also is a problem. > > > > > > > I would like to have the waves public when it comes to writing to > > the > > > > > > wave, but not public when it comes to removing participants, such > > as > > > > > > the Public participant and robots. > > > > > > > -- > > > > > > You received this message because you are subscribed to the Google > > > > Groups > > > > > > "Google Wave API" group. > > > > > > To post to this group, send email to > > google-wave-...@googlegroups.com. > > > > > > To unsubscribe from this group, send email to > > > > > > google-wave-api+unsubscr...@googlegroups.com > > > > > > > > > > > > > > > > . > > > > > > For more options, visit this group at > > > > > >http://groups.google.com/group/google-wave-api?hl=en. > > > > > -- > > > > You received this message because you are subscribed to the Google > > Gr
[Google Wave APIs] Re: Public waves can be made non-public by anyone
I was thinking of having one robot creating all the waves in my application, and each time a wave is created the robot adds the public participant to the wave plus one or a few robots to provide default functionality (such as support for emoticons). So when a user creates a wave in my application, it's the one robot that always is the creator of the wave. And each time a participant tries to remove the public participant or any of the default robots in a wave, then the robot who created the wave gets informed about that through WaveletParticipantsChanged() and immediately re-adds the robot that was removed from the wave. Anyone can remove all the other participants in any of the waves in my application, but since the public participant is always re-added immediately, nobody is blocked from any of the waves and I thought it would be nice to allow anyone to add or remove their own robots to the waves which would potentially provide for powerful capabilities in the waves. I haven't checked if all these things are possible in practice but that's my plan at the moment. And I don't know all the details yet. For example is it possible to catch an event and then consume it before any action has taken place? Or when a robot receives an event, then the action has already happened. On Jun 9, 8:05 pm, Nathanael Abbotts wrote: > Yes - but the robot adding public would be able to be removed also, unless > it created the wave. > > On 8 June 2010 23:53, Anders wrote: > > > Oh, now I discovered this: > > > class WaveletParticipantsChanged(Event): > > """Event triggered when the participants on a wave change. > > > I assume that it can be used for catching all cases when participants > > are removed from waves. That would be good enough. At least until more > > fine-grained control has been implemented which I saw is planned for > > the wave roadmap. > > > On Jun 8, 10:44 pm, Nathanael Abbotts > > wrote: > > > If it helps - I'm working on a robot that you can use to create waves for > > > you, and it will re-add anyone that was removed, unless they remove > > > themselves. (This robot would have created the wave, so it cannot be > > > removed). > > > > On 8 June 2010 21:00, Anders wrote: > > > > > I have started developing a wave application with public waves. One > > > > problem is that the Public participant pub...@a.gwave.com can be > > > > removed by anyone, and then the wave is no longer public! Not good. > > > > > Another problem is that anyone can remove robots from a public wave, > > > > which also is a problem. > > > > > I would like to have the waves public when it comes to writing to the > > > > wave, but not public when it comes to removing participants, such as > > > > the Public participant and robots. > > > > > -- > > > > You received this message because you are subscribed to the Google > > Groups > > > > "Google Wave API" group. > > > > To post to this group, send email to google-wave-...@googlegroups.com. > > > > To unsubscribe from this group, send email to > > > > google-wave-api+unsubscr...@googlegroups.com > > > > > > > . > > > > For more options, visit this group at > > > >http://groups.google.com/group/google-wave-api?hl=en. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google Wave API" group. > > To post to this group, send email to google-wave-...@googlegroups.com. > > To unsubscribe from this group, send email to > > google-wave-api+unsubscr...@googlegroups.com > > . > > For more options, visit this group at > >http://groups.google.com/group/google-wave-api?hl=en. -- You received this message because you are subscribed to the Google Groups "Google Wave API" group. To post to this group, send email to google-wave-...@googlegroups.com. To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en.
[Google Wave APIs] Re: Use of Google Wave logo
Hmm... I just finished the layout for the index page of my wave application. There is no place left for any extra image like that. So it's not on the top of my agenda at the moment. -- You received this message because you are subscribed to the Google Groups "Google Wave API" group. To post to this group, send email to google-wave-...@googlegroups.com. To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en.
[Google Wave APIs] Use of Google Wave logo
Copyright issues can sometimes be tricky. Is it ok for anyone to use the Google Wave logo on their site if they have some Google Wave functionality? Google App Engine has special images that can be used by app engine users. For example, I was thinking about using: http://google-wave-api.googlegroups.com/web/google_wave_logo.jpg?gda=eURxxEYAAABeaWIcNAi3mQDrCRs8PZYJCp9Hjca7AmksM-K4Bqfj0mUA2uQCMHmXUn1ZZRee4fVZJHP4N61vT0LAp83YGA48E-Ea7GxYMt0t6nY0uV5FIQ And scale it to make it smaller and remove the shadow. -- You received this message because you are subscribed to the Google Groups "Google Wave API" group. To post to this group, send email to google-wave-...@googlegroups.com. To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en.
[Google Wave APIs] Re: Public waves can be made non-public by anyone
Oh, now I discovered this: class WaveletParticipantsChanged(Event): """Event triggered when the participants on a wave change. I assume that it can be used for catching all cases when participants are removed from waves. That would be good enough. At least until more fine-grained control has been implemented which I saw is planned for the wave roadmap. On Jun 8, 10:44 pm, Nathanael Abbotts wrote: > If it helps - I'm working on a robot that you can use to create waves for > you, and it will re-add anyone that was removed, unless they remove > themselves. (This robot would have created the wave, so it cannot be > removed). > > On 8 June 2010 21:00, Anders wrote: > > > I have started developing a wave application with public waves. One > > problem is that the Public participant pub...@a.gwave.com can be > > removed by anyone, and then the wave is no longer public! Not good. > > > Another problem is that anyone can remove robots from a public wave, > > which also is a problem. > > > I would like to have the waves public when it comes to writing to the > > wave, but not public when it comes to removing participants, such as > > the Public participant and robots. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google Wave API" group. > > To post to this group, send email to google-wave-...@googlegroups.com. > > To unsubscribe from this group, send email to > > google-wave-api+unsubscr...@googlegroups.com > > . > > For more options, visit this group at > >http://groups.google.com/group/google-wave-api?hl=en. -- You received this message because you are subscribed to the Google Groups "Google Wave API" group. To post to this group, send email to google-wave-...@googlegroups.com. To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en.
[Google Wave APIs] Re: Public waves can be made non-public by anyone
Another problem is that someone could use a kind of terminator robot that automatically removes participants from my public waves. And then there would be a kind of war between my robot re-adding participants and some 'denial of service' robot frequently removing participants (such as the Public participant and robots) from my waves. So a re-adding solution would perhaps not be fully satisfying. And there is also a potential timing problem, because even human participants can remove the Public participant at any time from my waves and my robot would not be able to fully protect against some users suddenly not being able to use the waves because they no longer are public. I would like to have the option to mark some participants, such as the Public participant and robots as being permanent to the waves, i.e. they can not be removed by anyone else than the participant who created the waves. It's a strange kind of logic to have a public wave that anyone suddenly can make non-public. -- You received this message because you are subscribed to the Google Groups "Google Wave API" group. To post to this group, send email to google-wave-...@googlegroups.com. To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en.
[Google Wave APIs] Re: Public waves can be made non-public by anyone
I just posted a comment about that! The re-add solution might work. I think I will implement the robot myself, but it would be good to see some example code for how it can be done (I'm new to Google Wave). On Jun 8, 10:44 pm, Nathanael Abbotts wrote: > If it helps - I'm working on a robot that you can use to create waves for > you, and it will re-add anyone that was removed, unless they remove > themselves. (This robot would have created the wave, so it cannot be > removed). > > On 8 June 2010 21:00, Anders wrote: > > > I have started developing a wave application with public waves. One > > problem is that the Public participant pub...@a.gwave.com can be > > removed by anyone, and then the wave is no longer public! Not good. > > > Another problem is that anyone can remove robots from a public wave, > > which also is a problem. > > > I would like to have the waves public when it comes to writing to the > > wave, but not public when it comes to removing participants, such as > > the Public participant and robots. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google Wave API" group. > > To post to this group, send email to google-wave-...@googlegroups.com. > > To unsubscribe from this group, send email to > > google-wave-api+unsubscr...@googlegroups.com > > . > > For more options, visit this group at > >http://groups.google.com/group/google-wave-api?hl=en. -- You received this message because you are subscribed to the Google Groups "Google Wave API" group. To post to this group, send email to google-wave-...@googlegroups.com. To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en.
[Google Wave APIs] Re: Public waves can be made non-public by anyone
One solution could perhaps be to have a robot adding the Public participant and the needed robots each time a user opens a wave in my application. I'm new to Google Wave but I read that robots can add participants (and perhaps even check if a participant is added to a wave or not). I don't know though if that extra check and adding of participants when missing would create too much of an overhead. -- You received this message because you are subscribed to the Google Groups "Google Wave API" group. To post to this group, send email to google-wave-...@googlegroups.com. To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en.
[Google Wave APIs] Public waves can be made non-public by anyone
I have started developing a wave application with public waves. One problem is that the Public participant pub...@a.gwave.com can be removed by anyone, and then the wave is no longer public! Not good. Another problem is that anyone can remove robots from a public wave, which also is a problem. I would like to have the waves public when it comes to writing to the wave, but not public when it comes to removing participants, such as the Public participant and robots. -- You received this message because you are subscribed to the Google Groups "Google Wave API" group. To post to this group, send email to google-wave-...@googlegroups.com. To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en.
