Daniel, I agree that it's difficult to remove a robot from a wave of over 200 participants.
I like to use [email protected] in that situation to avoid having to sift through the list. Glad that you were able to resolve it and save your exhausted bot. On Dec 1, 5:44 am, Daniel Faust <[email protected]> wrote: > I'm in a ugly situation. > > Due to a 3rd party gadget in a wave which has my robot as a > participant, the bot is depleting it's Incoming Bandwidth quota after > only 4 hours. > > That gadget -- judging from the bot's logs > it'shttp://www.razorcam.com/seconds_spent_by_everyone_reading.xml-- > causes an OnBlipSubmitted every second. > > This means that every second the entire context is being pushed into > the robot. > > I tried looking at the participant list in the wave through the normal > wave client, but the list is huge (1000+), and there is no way to > scroll through it, so that I can't find my bot to remove it from > there. (Ok, fixed that, got a computer with a bigger screen and used > the ctrl- to make the page smaller) > > I've seen a removeSelf or something similar in the API which allows a > bot to remove itself from a wave, but at that time, about a month ago, > it was not implemented. > > Maybe there should be a place where we can submit robots/gadgets that > should be blacklisted due to unfair behaviour, and maybe the docs > should mention the side effects of implementing a highly active > extension. > > Or maybe an extra element in the capabilities.xml file which defines > which waves, or submissions from certain robots or gadgets should be > excluded from being processed. > > I truely doubt that razorcam.com had bad intentions, so I'm not angry > at all. -- 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.
