Skip to main content

Home/ (HBSN) How to Build a Social Network/ Group items tagged gwave

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
fishead ...*∞º˙

Google Wave Versus the Rest, Feature by Feature - Google Wave - Lifehacker - 3 views

lifehacker.com/...us-the-rest-feature-by-feature

gwave

shared by fishead ...*∞º˙ on 19 Jan 10 - Cached
  • We got a great response to last week's frequently asked questions about Google Wave, and decided it's worth expanding further on the differences between Wave and the current crop of web-based collaboration offerings. Wave combines features from email, instant messenger, Google Docs, wikis, and forums and throws its own spin on things. For a quick visual of its offerings versus similar tools, check out this feature-by-feature comparison table. (Click the image below for a closer look.) You'll notice that Wave doesn't have a green yes in every cell in its column; it's still missing functionality that's holding it back from being a viable alternative in a production environment—specifically, user permissions (everyone can edit everything) and the ability to export a wave or publish it so that anyone can see its contents (not just folks logged into Wave). This table is slated to go into chapter 1 of the first edition of The Complete Guide to Google Wave, so give me a shout if you've got ideas for how to polish it up before we rev up the printers.
  • fishead ...*∞º˙ on 19 Jan 10
     
    here's a detailed look at the good and bad features of Wave...
Jack Logan

Jack (4) - Google Wave - 34 views

wave.google.com/wave

contribute vote

shared by Jack Logan on 30 Jan 10 - No Cached
frank smith liked it
  • Jack Logan on 30 Jan 10
     
    Ya'll come and give us your opinion.
  • ...11 more comments...
  • François Dongier on 30 Jan 10
     
    Sorry, can't get into that wave again... Other than that; I have the impression that Wave speed has been improving greatly in the last days. It's getting almost usable now, even on large waves.
  • Jack Logan on 30 Jan 10
     
    Try now, François!
  • François Dongier on 30 Jan 10
     
    thks Jack
  • frank smith on 30 Jan 10
     
    Thanks Jack!! For everyone, I have added new questions and some clarification sub-questions. Check back periodically to see/contribute to this document growing. Anyone who can't get in, please contact me: underbrain.industries@googlewave.com into your Wave contacts. I will add you to the poll wave. Or if you are connected with someone who is in, they can add you. I am attempting to flesh this survey out with more functionality, please add any questions that you think will add to the discussion. Peace!
  • Jack Logan on 31 Jan 10
     
    Continuing great job with this GWave, Frank. Come all and join in and tell all your preferences. The last junket of age is your preferences! lol And, ... I still have mine, ... for the moment. So, ... come on over before I lose some of mine ... lol
  • frank smith on 31 Jan 10
     
    Morning Jack!! On the subject of the survey's map, I made it public for easy access, and we have new flag from a new participant named Barney Lerten, in Bend, Oregon.....anybody know him??? Part of the little difficulties with Wave right now...public is public. Ah well....
  • Jack Logan on 31 Jan 10
     
    Morning Frank! Kurt and I talked a few days ago about this - he was concerned about locking things down at this point. I don't know Barney. Kurt?
  • François Dongier on 31 Jan 10
     
    Never heard of Barney before either. He was invited to the wave by "Public". As you say, Frank, public is public.
  • frank smith on 31 Jan 10
     
    It's a concern I share. That's why i move the stuff to Wave. we need a list of eceryone in the groups Wave IDs
  • fishead ...*∞º˙ on 31 Jan 10
     
    For my 2 sense...don't use Wave--set a private group here or somewhere else, that doesn't have the public/private issues of wave. the problem with wave is there is no central management--anyone can add anyone else to the wave, and pretty soon, ALL your content is visible. I suggest something a little bit more locked down, unless you want to be truly open-source, in which case, take Bent's lead, and move your discussions to codeshare.
  • frank smith on 31 Jan 10
     
    hey fish!! the only issue is that I was dumb and made something public. we have the same issues on Diigo. We just need a Wave group that includes all the interested people.
  • François Dongier on 31 Jan 10
     
    Agree with Frank. There is no use in letting Barney tell us where he lives, if we want to use the map gadget to choose a good place for a meatspace meeting. So this particular wave, given its intent, should have been restricted to the group. In many cases, I think it could be harmless to open a wave to the public: the crowd can contribute good things, we all know that... But I still think that, by default, wave access should be restricted to group members. It would maximize the sharing of relatively private or "sensitive" information within the group. It would also help keeping the discussions on topic (side-tracking is very easy in all forum discussions and the more people you have in the conversation the more side-tracking you get). Now of course anyone in the group can invite anyone, even "Public" into the wave: just like anyone who has access to a private document can copy it and paste it on a blog or any public place.
  • frank smith on 31 Jan 10
     
    Yes F1 (Francois, I will be F2)!! i think we can use the wave structures to keep things private and the fact that any of us can add anyone can be moderated by convention and the trust we have begun to build with each other. plus the reinforcement from the system, in that we all can see who has added whom. Plus the ability to delete participants will come along eventually. Thanks F1!!!
Kurt Laitner

Solving the Threaded/Flat problem - 1 views

forking / splitting and Perspectives come into this as well

started by Kurt Laitner on 01 Feb 10 1 follow-up, last by Kurt Laitner on 01 Feb 10
1 - 3 of 3
Showing 20▼ items per page