@x00 I think we just need to agree that we disagree on what wave is. What is important is to decide what is the main target user base for wiab at the moment, and then to make decisions based on what is wave for the main target user base. So the real discussion should be about who are the usrs that we want to target with current wiab release. Or more specifically - what is the main problem for now that wiab aims to solve? If we will answer these questions, then I think we would be able to agree also on the question if wave should public or private by default.
On Dec 3, 2:52 pm, x00 <[email protected]> wrote: > It would piss people off if you were to add someone in a federation, > who doesn't represent a public group, and the service then add public. > > On creation then it is absolutely up to the service an their > interface. Or could be just a standalone client interface only. -- 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.
