On Wed, Feb 10, 2010 at 5:19 PM, eyalzh <eya...@gmail.com> wrote: Hoi Eyal ;]
> Try to block googleusercontent.com temporarily in your browser / hosts file > etc. > Then enter the wave and remove the gadget. > > To view the wave structure you can use antimatter15's wave reader: > http://antimatter15.com/misc/read/?googlewave.com!w%252BRvJRnrZkBZi > > Hope this helps, > Eyal. > Its not that i can save this wave, i demonstrates a deeper underlying problem, that is the lack of a permissions system that allows the owner to determine what participants can and cannot do. Bart > On Wed, Feb 10, 2010 at 6:03 PM, Bart Thate <bth...@gmail.com> wrote: >> >> Hello wavers and more hello Google Team, >> >> Today a gadget was inserted into a public wave of mine, which directed >> me on joining the wave to the following page: >> >> >> http://hosting.gmodules.com/ig/gadgets/file/100726510508187623906/wave.html >> >> this page is a phishing login page of google wave which upon >> registration logs stuff in a spreadsheet. The effect is that i cannot >> enter the wave as it instantly directs me to the html page, so i >> cannot even remove the thing ;] >> >> Obviously we need some stricter level of security in waves, now i wish >> i had something like +v in waves, so people can add txt but not insert >> gadgets etc. >> >> The wave is at: >> >> >> https://wave.google.com/wave/#restored:wave:googlewave.com!w%252BRvJRnrZkBZi >> >> Greetings, >> >> Bart -- 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.
