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]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
