Thanks for the reply. I'll just wait for the new API then. - Stephen
On Sun, Feb 14, 2010 at 9:16 PM, cmdskp <[email protected]> wrote: > Hi Stephen, > > Last I checked a couple months ago, a robot can't remove any > participants (including itself). The reason being that Google are > still considering how this will work in practice. The only 'robot' > that can remove other robots being Bouncy which is actually more than > a standard robot and is using behind-the-scenes tie-ins with the > server (that non-Google robots can't access) to allow it to remove > other robots. > > Still, new API coming out soon, they hope, I wonder if that might > allow the removal of the robots by themselves? > > Back to proxying, I also tested this out and anything after the + in a > proxy-for email address is ignored by Wave and treated like an email > address without it. So, you can invite: > [email protected]<myrobot%[email protected]> > and [email protected] <myrobot%[email protected]> to a wave > (either from your robot or > manually) and they both refer to and work like the normal: > [email protected] > > Any robot can then substring out the stuff after the + to pickup clues > as to why they were added, for example. You can't proxy for a > different user/robot though, like > [email protected]<myrobot%[email protected]> > , > it's just a method for filtering or providing multiple addresses for > one email address, AFAIK. > > AFAIK, you also can't change or remove the creator of a wave after > it's been made, so it will always be the robot in your case. > > Hope that helps clear things up a little anyway! And maybe things > will change in the new API soon...who knows...we'll need to wait and > see! :D > > On Feb 11, 12:38 am, Stephen Gigante <[email protected]> wrote: > > I made a robot that will on a blip-based trigger, create a new wave, and > > then remove itself from both the old and the new. Apparently, (for both > me > > as a user, and the robot programmatically), A robot cannot be removed > when > > it's the creator of a wave(let?). > > > > I don't want my robot to be forced to listen to the waves once it has > done > > it's task in them, but it seems that it is unable to remove itself under > the > > circumstances it's put itself in. > > > > My question is: Can I make use of 'Proxying for' (I've heard about it, > but > > don't really understand it) to make the creator of it's new wave as the > > creator of the triggering blip? > > > > - Stephen > > -- > 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.
