Open Sourced Google Wave demo site. Run from a single server
waveinabox.net
waveinabox.net
I just checked my wave account on the news it was sunsetting. I had four new unread waves from friends that were at least four months old. How was I supposed to know they were there? mean, I used Google products daily!
2) You could turn on email notifications. I suspect this wasn't done by default because for people like me who had waves constantly being updated and changed, the notifications would have flooded my inbox. The integration definitely could have used some work, but there were ways for you to be notified.
Wave was meant to replace a certain way in which we use email, which is a subtle but important difference. It was supposed to replace the emailing of versions of documents around, or the long email threads to organize simple things like getting lunch or dinner. These are things where email still to this day falls flat, and Wave solves completely.
There is ample room for startups to be disruptive using nothing more than the open source Apache Wave software.
However i still find it hard to place wave. It feels too rigid to be used as a chat solution, and too confusing to be used as a messageboard. If anything it feels like an overly elaborate version of etherpad.
Imagine you were in a globally distributed organization of over 10,000 geeks. And all of these geeks are producing documents at warp speed. Based on need it could be text formats in SVN, Google Docs, or graphics. Everybody gets hundreds, even thousands of emails a day, and uses IM obsessively.
And there's a strong need for extreme openness with other teams, but also an occasional need for extreme secrecy.
All these things are archived, but in different places. How do you know what the latest design is? Well, you can check recent email threads, or your chat logs, or the wiki, or your product documents, or...
So the theory here is to end the madness of all these competing formats by making one format that has (potentially) all of their attributes. Your one format can handle any media type you can represent in HTML. All commentary is inline, and you can even develop the comments into full blown documents. You get IM that has history like a wiki, or, wiki collaboration as instant as IM. And all of this could be subject to access control.
Unfortunately that makes it all very amorphous to the average person.
I assume not, if they're canning it. But I'd love to know why not, if it didn't.
It was cancelled because the number of external users didn't meet google's expectations, not because of how it was used internally.
2) It looks different (similar, but a cut down GUI)
3) It's far more performant than the old Wave GUI
2) Not a huge fan of this
3) Disagree. It's far more performant than Wave when it launched, but this new GUI is on par or worse than the current Wave experience. At least for me, I guess your mileage may vary.
That can transform typically suggested alternatives into non-alternatives for some.
What I most like is the old Google style on the login page. Even after months(?) of using G's new layout, I still dislike it.
BTW: What is a "cancel" button doing on the signup form?
Incidentally, browser incompatibility with Opera also stopped me from using Quora.
Granted, as a disclaimer, I didn't sign up. I'm making an analysis from what the homepage says.
Question - in Stypi, live typing can be overwritten by anyone else who is in the same room. Does this work the same way? Because that is a huge flaw - but then, I don't think there should be live typing at all.
Edit: I had to kill a unit test to get it to work, testWaveletNotification in org.waveprotocol.box.server.waveserver.WaveServerTest.