On 10 Feb 2010, at 11:23, Bart Thate wrote: > 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.
And for that matter, the creator/owner's ability to remove something out of a wave as if it had never existed in the first place, or has that ability been snuck in below my radar? Last I checked there was no permanent removal, so if you'd do a history playback you might still end up there again... There have been discussions here before on the type of security levels, which allow moderated threads, cooperative threads, etc. which exhibit different mechanisms of control over access and deletion. The issue of things embedded in Waves is one that is disturbing, however, in much the same way as html e-mail: the moment you have "rich" content, it allows for masquerading of things as things they aren't, and thus for all sorts of social engineering approaches for hacking and phishing. I would thus also much prefer that when I create a wave I can specify that it must be plain-text only, just like I avoid HTML e-mail like the plague. Allowing specific content should have to be a conscious, deliberate choice. It should also be possible for the wave creator to decide the set of gadgets, bots, etc. that are permissible in a wave, because with these things proliferating, you will at some point be hard pressed to know what they do and where your information goes behind your back. Ronald -- 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.
