Hi, I like Thomas' idea but i would add a twist there. I think there should be a similar dialog like in Gwave that asks you to add people to your wave. On top of that list should be certain groups like "World", "same Server", ..., and after these general groups there can be your friends. That would make it equally easy to make a wave public, keep it private to share it with your friends. Different clients could use different lists or set default participants.
Regards, Georg On Fri, Dec 3, 2010 at 4:51 PM, ThomasWrobel <[email protected]> wrote: > +1 for upto the client/specific use-case. Some case's public makes > sense, other private. > > But for the default web client I think it would be fine to keep it > private, as long as making things public was much more intuitive then > adding a specific user that represents the public. > Ditto for "read only" > > These should be dropdowns/tick-box's or some other really easy to > select options when you create a wave. Maybe even not have a default > at all. Just some buttons and they have to click one. (making wave > creation a two-click operation rather then one, but it would make > things crystal clear to the end user if something is just between > their family, or between the whole world). > > On Dec 3, 3:47 pm, Ian Roughley <[email protected]> wrote: > > On 12/03/2010 07:46 AM, x00 wrote: > > > > > > > > > @Vega. I think you are misunderstanding what Wiab is for. It isn't a > > > for making mini gwaves. It for other to devise their own services > > > whatever they are. So it is entirely up to them. > > > > Well, in fact it's both. > > > > As long as determining whether a wave is public or private is an > attribute and not a default in the > > model code, I think we're fine - because then it's up to the client to > decide what *they* want to > > do. Then any 3rd party can re-use this code and make their own > decisions. > > > > On the other hand, we do need to decide the target audience for WiAB. > It's got to be focused so > > people know what it's for, so they'll use it. > > > > > > > > > Private is a default becuase you don't publish anything until you are > > > ready to do so. > > > > This could also be construed as a drafts mode for the initial edit, which > has nothing to do with > > whether the wave is ultimately private or public. > > > > Also the private by default makes sense in federation > > > > > > > > > > > > > > > > > terms. Public is essentially a group permission amongst many. > > -- > 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]<wave-protocol%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/wave-protocol?hl=en. > > -- 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.
