Bouncy was written by a Googler and has access to internal functionality for robot participant removal (not for human participant removal). Robots using the external APIs cannot remove any types of participants at this time. See: http://wave-api-faq.appspot.com/#removeparticipant
<http://wave-api-faq.appspot.com/#removeparticipant>- pamela On Sun, Dec 13, 2009 at 3:09 AM, Stephen George <[email protected]> wrote: > I too am curious how bouncy gets away with it. :) > > On Dec 12, 4:51 am, qMax <[email protected]> wrote: > > Hello. > > > > java API library has method wavelet.removeParticipant. > > pyhon lib misss it, and twas told that the method not yet supported on > > wave server. > > > > However, web-client can remove robots, and thus, protocol support such > > operation. > > On the other hand, bouncy the robot also is (or was?) able to ermove > > robots. > > At some recent OH it was told, that it is "quite not a robot" and uses > > some server-side hacks to do it's dirty work. > > > > I wonder, if those hacks are available for legitimate robots. > > And if sources of bouncy are open. > > > > P.S. > > going to develop some guardy-robots to compensate lack of native > > access control. > > -- > > You received this message because you are subscribed to the Google Groups > "Google Wave API" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-wave-api%[email protected]> > . > 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en.
