Hi, wavers! <motivation> With current permission system in Wave, only 1 malicious user and a pair of bots is enough to destory _ALL_ public waves. And the war has begun. One bastart started to destroy popular pubic russian waves. It seems like it has not yet properly working robots, but it's a matter of time. Russian users going to completely decline using public waves anymore. </motivation>
And I'm thinking about alternative to [email protected]. A solution could be: - mirror root blip into _public_ wave, so that it could easily be found by interested people - restore the blip from changing, and preferably - synchronizing changes with root blip of original wave; - completely delete all replies, but memorize authors; - automatically adding reply authors to original wave, if they are trusted by some participants of original wave. This could avoid necessity to completely go into undeground with only private waves :) Synchronizing root blips could be tricky, but still possible. If to memorize waveId/waveletId/blipId of mirrored wave it is possible to build and send an operation to replace whole content of blip out of event context. On some office hours Austin Chau confirmed that such operation should succeed. Please, respond if someone have succeeded in this. And main problem is to maintain users relations. There is bogus groupy bot with function 'add friends of groupy' (about 2000 users). You know it if ever tried the bot (never try if not!). Who knows how he tracked his friends? Is it possible to use GContacts API to track such relations? or the bot should maintain own database of users? have someone succeeded with using datastore with bot? Answers and any ideas will be appreciated. -- 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.
