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 <nat.abbo...@googlemail.com> 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 <blabl...@gmail.com> 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<google-wave-api%2bunsubscr...@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.
