As i said before - if someone would like to create "private" wave - it should be supported. Also, it seems that because of wave ambiguity, everybody think about something else when they hear "wave". I arrive to conclusion that STenyaK is right and the default behavior should be dependent on context. If someone wants to use Wave as blog - then public should be default, however in context of email it probably should be private...
On Dec 2, 10:49 pm, "Gamer_Z." <[email protected]> wrote: > Except wave is not a social network or micro-blogging site (although > it could be integrated into one). It is also used for e-mail-type > conversations IM-type conversations, and document creation. Imagine > if every time you created a document in Gdocs, MS Word, Pages, or > OpenOffice it was public. What about if every Gtalk or AIM > conversation were public? What about if every single e-mail you sent > or received were public. See the problem there? And even in your > example, Facebook and Twitter posts remain private until you click the > "Share" or "Tweet" button. It is much better for every wave to start > and remain private until the user wants to add participants or make it > public. > > On Dec 2, 3:19 pm, Vega <[email protected]> wrote: > > > > > > > > > Hmm, let's imagine that Twitter would be "private" by default, i.e. > > every twit would be private so only people that you explicitly > > specified would see the contents of the twit - do you think that would > > be help it to become something like it is now? Or if Facebook would be > > private by default... Wave is the collaboration platform where things > > are shared openly. Of course if someone wants to change the settings - > > it should be supported. > > > On Dec 2, 7:33 pm, Bertine van Hövell <[email protected]> wrote: > > > > I prefer to keep private as the default. If you accidentally keep > > > confidential content private, the only loss is to you. If you > > > accidentally leave confidential content public, you'll have a much > > > larger problem at hand. > > > > To give an example. I use google docs often, but in my main list I > > > often see a few documents popping up of which I'm sure the person > > > didn't mean to share it with *everyone*, and that's even in a medium > > > when you have to choose to share. Imagine what would happen if gdocs > > > would be public by default. > > > > Seeing as Wave is a safe way to be able to share private information > > > (and in some cases is the reason why people continue to use it until > > > now), I prefer to keep 'private' as default. > > > > On Dec 2, 12:10 pm, 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.
