I like the fact that it defaults to private. It reminds of content management where it the content is in a "draft" mode until it is published to the public.
On Dec 2, 5:10 am, Vega <[email protected]> wrote: > The current default wave mode is "private", i.e. whenever a new wave > is created, it can be accessed only by the owner and then by > participants added by owner. > I think that this concept is not something that is obvious. It seems > to me that it evolved this way since originally, Wave was created as > email replacement. However, as we see, Wave is a lot more. It is a > platform for collaboration, and as such it should embrace its users to > share the content, not to hide it. Off course, if someone wants to > create private wave, or change the default settings - it should be > supported. > The official reason for Google Wave development discontinuation was > "lack of traction". I think the main reason for this - there's was > very little public content. Because in Google Wave everything is > private/limited until stated otherwise. Why not change it? Why not > make everything public until stated otherwise? > It may be a small change that makes a lot of difference. > For example, I guess everybody knows the Flckr service. The company > allowed users to upload images to its servers and share it. It wasn't > the only one at the time, however it was the first to make the images > public by default and it resulted in huge success. -- 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.
