First of all, it is very well possible to do all of the malicious actions even *without* bots. We have managed to reverse-engineer parts of the wave<->web protocoll, and are able to read full wave contents of all public waves. See archive.waverz.com for implementation. Second, using that, it's fairly trivial to do full backups of wave data, which can be restored to a new wave. Third, you can build trust networks by using the Google groups solution<http://archive.waverz.com/googlewave.com!w+VJoH3a3CK/_>, along with WaveNotify<http://archive.waverz.com/googlewave.com!w+uOcHp3yOA/>(for e-mail notifications). Until permission checks are implemented, this is the best way to keep malicious intents out of your group's waves. Fourth, using a protector bot, and a known blacklist (remember: wave invites are still a precious commodity), it's fairly trivial to restore all edits done by malicious bots, or users.
>Who knows how he tracked his friends? Probably the same way all bots do: by storing participants of the waves it's been contacted by. As you can see, lots of solutions are already available, even without blowing the public-group-experiment up :) -SDr On Sun, Nov 29, 2009 at 1:20 PM, qMax <qwigly...@gmail.com> wrote: > On 29 ноя, 18:40, Brett Morgan <brett.mor...@gmail.com> wrote: > > At least back in the days of usenet, when the reaper came, he at least > had > > the decency to be offering a chance at a green card. > Usenet was at days when the world was clean and friendly :) > Yet there was no ssl even. > > > Wikipedia seems one of > > the few public systems that hasn't fallen apart, I suspect because the > > ability to undo damage is lower cost than the cost of doing the damage in > > the first place. > Do have no doubts, russian wikipedia sector had all forms of edit- > warring, with all that ban-cometee, and even debates in RL. > You know us russian barbarians :) > > > There are a bunch of technical "solutions" in this area including rate > limiting and banning bots on public waves. > Recently Lars promised some solutions for moderation and permissions > in next year. > And I'm looking for workarounds right now, 29 Nov 2009. > > > And all of that becomes moot once we federate. > What do you mean here? > > -- > > 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.
