On how Google Wave surprisingly changed my life
maxklein.posterous.com
maxklein.posterous.com
Also the UI around threading in Wave is awful from a usability perspective. It's nearly impossible to tell if you're creating a sibling or a child until you've done a lot of experimentation. The affordances are extremely unclear.
And without email notification or other kinds of client support, Wave has become yet another site I have to check every day.. I got sucked into a wave planning a family reunion and I forgot to check it for a few weeks, and I missed all kinds of activity. Even then it was a jumble since all the users had difficulty grasping the concepts, and missing replies to earlier threads.
As you point out, Wave's UI is horrible for chat. That's why we're building http://shoptalkapp.com; it's similar to Campfire. We use it every day and couldn't live without it. It's like a virtual office.
I actually wonder, on a highly trafficked Wave with many subthreads, if the OP doesn't have trouble figuring out which parts are relevant and need to be promoted or flagged as a more authoritative/final artifact of a discussion, and which are just unproductive tangents? (especially since Wave doesn't let you reparent your comment if you've accidentally put it at the wrong hierarchy level. It also doesn't let you delete comments! wtf?)
I'm sorry but couldn't he have achieved the same with a threaded email client?
It sounds like Wave just helped him smooth over a lot of poor email practices - perhaps on the other end of the conversation as well, but still.
Wave allows you to rearrange and drop messages so that you can restructure a conversation to make it easier to follow, kind of like I think rebasing in git is supposed to work.
If all the participants in an email conversation adhere to a strict bottom-quote and trim discipline, then you can keep everything organized in a threaded email reader. However, wave makes it easier to not include all the quoted cruft and keep replies in order for those people who haven't been initiated to "proper" email conversational etiquette (which is probably most of the internet).
You also don't have to leave things in your inbox to keep them current, though that might be a bad email habit of mine. A wave is "heavier" than a conversation but "lighter" than a label/ folder.
So my email habits were bad, as where those of the others. Wave naturally guided us to a different way of communicating.
I would agree... but I've yet to see an email client that never breaks threading when handling emails between X number of other email clients, some of which are not threaded, some of which strip attributes, and some of which rewrite attributes.
Emails need a better, unified threading control, and clients need better, more powerful organization tools. Once that's done, sure, a proper email client would do the same thing, though with significantly increased duplication (5 replies == 5 emails to each person in the conversation, or a single highlighted thread in Wave(-like) apps).
After two months, one of my freelancers replied my email with a screenshot. It showed his inbox, and there were about 50 unread emails from me, 10 of which where various threats about why he was not replying my emails.
Looks like there's something to it after all.
I've used Google Wave a few times and these are the issues I have with it still:
1. The feature set and jargon is overwhelming. I still have yet to use half of the buttons available in the UI.
2. The marketing around it is really confusing.. Is this supposed to be a Gmail replacement/augmentation and will Gmail development slow down in favor of this new model? Hello Microsoft marketing team.
3. Real time character by character chat is weird and a little creepy. Still not used to that.
4. I'm on a fairly powerful machine yet FF or Chrome still seem pretty bogged down after moderate usage.
For this guy it seems really useful and that's great but his case also seems to be a niche one. I'm involved in 2 startups and my current setup with Google docs and Gmail suit my needs for collaboration just fine.
I have a Google Wave account and i can invite others but the invitees are not immediately accepted , so one of your collaborators does not have a Wave account , how do you collaborate with him ? So now, you have to have multiple ways of collaboration - not good.
Unless of course i am missing something obvious.
Would appreciate it! (mail is in profile here at HN)
(sorry for the off-topic to the rest)
BerntBu at GMail.
People were still doing backups before dropbox. I, for one, am just doing them better now.