What Gunnar proposes isn't feasible with wave and has never been possible with e-mail. A user cannot add themselves to a wave. Participants ae added by an existing participant. When the ACL stuff is added, a participant will only be able to add others if he/she has permission to do so.
If a, b and c wish to have a discussion that doesn't include d, then they create a separate wavelet within the wave. A wavelet is the smallest unit of control (think of it like a room in a house), either you can see all the wavelet content, or you cannot see any of it. There is no way within the current implementation to do otherwise. Like e-mail, a wave participant can copy all existing wave content, form a new wave containing that content and then add new participants. A wave server could be implemented such that a wavelet is restricted to participants from that server (think corporate wave server). But further control of content distribution is not possible without DRM. And even then, cut-and-paste is still possible unless the DRM is truly draconian. -Tad On Wed, Sep 16, 2009 at 11:30 PM, [email protected] <[email protected]> wrote: > > Hi Gunnar, > > That's an interesting thought. How does that differ from the current > access control white paper? > http://www.waveprotocol.org/whitepapers/access-control > > David > > On Sep 16, 11:04 am, Gunnar Guðvarðarson <[email protected]> wrote: >> Each client should, by default, have the option to allow or deny >> content according to the clients attached to the wave. For instance, >> if 3 people are on a wave (persons a, b, and c) and another joins (d) >> users a, b, and c should individually receive a message "do you want >> to accept content from d" and an additional message "do you want to >> allow d to see your content" or a single message with the two messages >> and a checkbox for each. Also, user d should have the option of what >> content should be seen/visible to the other users attached to the wave >> on a per user basis. This would eliminate the potential of a spammer >> or troll to abuse a wave. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Wave Protocol" 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/wave-protocol?hl=en -~----------~----~----~----~------~----~------~--~---
