Why not ask the user upon signup / first login if he wants his waves public by default? This could be a changeable preference setting. So every user can choose.
I also like the GWave idea of having pre-defined wave types. So you could click on "new public wave", "new private wave" (or later "new group wave"). Greetz Martin On Dec 3, 10:29 am, STenyaK <[email protected]> wrote: > I think there's not enough data to correlate public/private setting > with Google Wave project success. Unless someone has some insider info > on A/B tests about this issue in Google Wave, it is pure speculation. > Making it public default may help WiaB succeed, or it may not. > Selected third party examples like Flickr (public) or GMail (private) > add no meaningful information to the discussion. > > Regardless of that, I'd personally vote for making WiaB Client create > public waves by default, and have this behaviour modifiable by either > the specific WiaB Client install administrator, by each WiaB Client > end-user, or by both. I will surely turn public off as soon as I > install my WiaB client; but for rushed trial-test installs by geeks > who hear about this "hey let's test this apache wave thingy that this > tech blog mentioned", it'll be simpler than having to guess that they > needed to manually add "pub...@can't-remember-my-domain-name.org" or > other magic procedure. > > > > > > > > > > On Fri, Dec 3, 2010 at 09:55, Vega <[email protected]> wrote: > > > On Dec 3, 1:23 am, James Purser <[email protected]> wrote: > >> Actually I'm more than willing to bet that most enterprise setups will be > >> gun shy about having waves be automatically public, as will many users. > > >> Personally I like the model GWave has at the moment: > > > I just want to add that: > > 1) GWave failed to gain traction regardless of being really > > revolutionary product. Therefore it might make sense to try to do some > > basic things differently or at least provide support for this. > > 2) Many agree that GWave was good at many things, but failed to be the > > best at anything. Of course Wiab cannot provide multiple skins out of > > the box, but maybe it would be useful to define a set of purposes and > > then prioritize them, so whenever a question of default behavior would > > emerge - it can be evaluated against this set as to allow consistency. > > It also means that main target user base should be defined. Is it > > private users? Small businesses? Enterprises? Trying to satisfy > > everybody will result in repeating Gwave mistake i.e. - in satisfying > > no one. > > > -- > > 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 > > athttp://groups.google.com/group/wave-protocol?hl=en. > > -- > Saludos, > Bruno González > > _______________________________________________ > Jabber: stenyak AT gmail.comhttp://www.stenyak.com -- 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.
