superglaze writes "Google has unveiled a distributed, P2P-based collaboration and conversation platform called Wave. Developers are being invited to join an open source project that has been formed to create a Google Wave Federation Protocol, which will underlie the system. Anyone will be able to create a 'wave,' which is a type of hosted conversation, Google has said. Waves will essentially incorporate real-time dialogue, photos, videos, maps, documents and other information forms within a single, shared communications space. Developers can also work on embedding waves into websites, or creating multimedia robots and gadgets that can be incorporated within the Google Wave client." Jamie points out this more informative link.
I know it sounds funny, but I have a friend who has been working on a homebrew system for Jane Austin PnP RPGs. Narrativist RPGs actually lend themselves rather well to this kind of thing, especially if the emphasis is on storytelling and social maneuvering, instead of THAC0.
by Anonymous Coward
on Thursday May 28, @07:14PM (#28132549)
Actually, you did fix it.
Google tracks you online.
Google knows what you watch, what you read, what medical conditions you search on, reads the emails you send to your mom, knows where you live and what color frisbee is stuck on your roof, and soon will track every phone call you make from the gphone.
Replace "google" with "the feds" and I bet we'd all... oh, no, nevermind, I just remembered, we all trust big corporations...
I think that real-time collaboration is a flawed concept in most contexts. People are not at their best when they have to be creative, inventive, or thoughtful in real-time with an audience. Nor do people do their best analysis when they're sitting around a (virtual) whiteboard.
Asynchronous collaboration tools are always going to be more important than synchronous ones; synchronous is better for broadcast and one-to-many communication.
And, if you force people to function asynchronously, people will more likely take the effort to request only what they need. Real-time people have little impulse control and make requests because they can -- not because they should.
People are not at their best when they have to be creative, inventive, or thoughtful in real-time with an audience.
I'd be interested for you to elaborate on why you believe this. There's plenty of counter-evidence to this point in that the following practices are time-tested ways of creative thinking: - comedy writers bouncing ideas off each other to start penning a script or sketch - group brainstorming for new names of products and advertising ideas - new product ideation amongst engineers
I'm sure everyone is different, and some prefer quiet solitude to be creative, but it seems the exception rather than the rule in most organizations. I personally find that people tend to be much more cautious and defensive when they have time to craft a well thought out idea, as opposed to blurting out a potentially stupid/creative idea.
It's strange that you think that - real (actual physical) whiteboards are great for engineers and scientists. There is still a division between people who are happy thrashing ideas out on a board, and those who feel that they need to nurture something in private. I have to ask whether your comments about the environment being poor for research and insight are limited to virtual whiteboards or if they extend to their real-life counterparts?
So where do you think virtual whiteboards break down? Is it the lack
Except maybe it will be what something like Twitter, Facebook, and IM should have been from the beginning. For one thing, it sounds like it will be open and decentralized, meaning that I can set up my own Wave server, and you can set up your own Wave server, and our users can talk without any problems.
You can already do that with IM so long as we're all using Jabber, but otherwise it can get a little problematic. But I can't set up my own private facebook or twitter server, and even if I do, there's not support for my server to let people befriend and network with people on the real Facebook and Twitter.
To me, that's always been the #1 problem with social networking sites on the Internet. You can't set up your own, but instead your left to make a new account on whatever site is cool this week. Like what if instead of being able to set up my own webpage, I had to set up a webpage on whatever hosting company was trendy, and then rewrite it based on that host's protocols?
But I can't set up my own private facebook or twitter server,
Twitter -- I see no reason why this couldn't be just Jabber to some sort of broadcast channel.
Facebook -- XFN, OpenID, and friends.
even if I do, there's not support for my server to let people befriend and network with people on the real Facebook and Twitter.
That's the real problem.
There's a whole set of open standards that pretty much covers all of what social networks do for the user. But for some reason, most users are still in the gated community of Facebook, so even though the open communities could theoretically be bigger, better, and freer, right now they're smaller, because they're not Facebook.
By setting up your own you're destroying the networking aspect.
A private site for friends will never have the pull of a world-wide LOOK AT MEEEEEEEEEEEEEEEE site.
Accurate, insightful.
If that's what you want, great, go for it. But I seriously doubt that's what Google has in mind. They want all of your data, and this is just another tool for them to get at it.
Controversial point. Trying to spread fear, whether or not it's justified. The following couple of paragraphs present some interesting speculation.
Regardless of function or intention, my comment still stands (despite being modded troll by Googs) - the layout shown is hideous and provides nothing but total information overload.
If there's anything in your post to warrant a troll mod, this is it.
You post here a lot, and you don't trouble yourself to be terribly civil. Not that that's uncommon, but I think it's a shame. Your ideas seem generally worthwhile, but your attitude probably limits their discussion. Geeks and engineers are probably more likely than most to pay attention to the factual accuracy of any statement instead of the emotional context; the opposite is the rule in other circles. If I may offer some advice: if you're going to be callous, be right, and even if you are right, don't bitch about the troll mods.
I can set up my own Jabber server and talk to people on Google's GoogleTalk or Gmail chat. In fact, that's what I do except I'm using jabber.org's server. Of course, Google still gets your conversations with those people, but not if you use OTR.
This sounds like the potential that Jabber/XMPP has always had, but no one seems interested to implement.
By setting up your own you're destroying the networking aspect.
A private site for friends will never have the pull of a world-wide LOOK AT MEEEEEEEEEEEEEEEE site.
Er... no. You could set up social networking standards and protocols that would allow various sites to enable their users to build profiles which could then be shared in a manner very similar to facebook. You'd want some kind of common authentication (OpenID) if you don't want all the profiles to be public. If anything, I'd say that by keeping a private little proprietary system, they're limiting the networking aspect.
They want all of your data, and this is just another tool for them to get at it.
...except that it sounds like they're making it all pretty open. From TFA, "The code will be open source, and developers intending to build on the platform are being given access to APIs, according to a post on the official Google blog."
So you can build your own implementation, and the whole thing is going to be P2P, so Google won't necessarily have access to your data unless you're specifically using their server.
the layout shown is hideous and provides nothing but total information overload.
Well first, I don't agree that it's so awful. Second, it's pre-release and not even a public beta. Third, it's going to be open source so you can skin it or completely rewrite the interface.
So, they use SIP to chat and handle voice. There's a protocol for presentation that's rolled into some SIP servers. You guys have no idea how powerful the SIP standard is. There isn't a client that handles it all yet.
Besides the very un-special nature of the application, I'd be interested to see if the Telcos will litigate Google on their gigantic pool of obvious patents. Either that or Google's paying them a 'vig' already.
i cant wait for this app... its so hard for people on tight budgets to collaborate on projects due to the high software costs... sure one can argue that there are many free alternatives out there but there really isn't anyone that has it quite right yet. One on one collaborations are okay but it is still quite impossible to have a decent meeting on line if you have three people or more, for free...
It's this [waveprotocol.org] I find most interesting:
Subject to the terms and conditions of this License, Google and its affiliates hereby grant to you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this License) patent license for patents necessarily infringed by implementation of this specification. If you institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the implementation of the specification constitutes direct or contributory patent infringement, then any patent licenses for the specification granted to you under this License shall terminate as of the date such litigation is filed.
If I'm reading this right, it looks like patent MAD. Basically, Google is saying, "If you sue anyone for patent infringement about this spec, you give us the right to sue you. If you don't sue anyone, we're cool."
The implicit threat is, of course, that Google will own as many patents regarding this spec as anybody, but as long as nobody exercises them, it doesn't matter -- they're still allowed, for this spec.
Which is both very cool, and raises some interesting questions -- like, what if I implement the spec as part of a much larger app, and someone sues me for infringement of a different part of the app? Or, what if I want to create a modified version of the spec, or create a wholly unrelated application that infringes on patents related to this spec -- do I open myself up to lawsuits then?
This reminds me of a PhD thesis I read about a few years back. Adam Fass' Messyboard [messyboard.org]
MessyBoard is a networked bulletin board that allows people to share notes, pictures, files and other content. Everyone who looks at a MessyBoard sees exactly the same thing, and all users see changes in real time. It runs as a Java applet inside your web browser, so no software installation is necessary. Text and images from other applications can easily be posted on MessyBoard using drag-and-drop and cut-and-paste. Each board has a URL that is easy to remember, so you can access it from any computer on the Internet.
MessyBoard stores a complete history of all activity, allowing users to go back in time and recover old content simply by clicking on a slider bar.
Coincidentally, Fass now works for Google in WA state.
The decentralised nature of this system will directly threaten Facebook, Twitter et al.
The DNS system works, and scales, because everyone publishing information to the DNS is responsible for the upkeep of the nodes that publish their own records.
Facebook and Twitter, however, have scaling and financial problems. Facebook, so far as I am aware, continues to make a substantial annual loss despite its enormous success, and I have yet to hear that Twitter has managed to turn a profit.
More importantly, the privacy of everyone publishing much of their personal, private correspondence using a small number of centralized agencies is directly threatened -- and it could get particularly messy if, in a few years time, $SOCIALNETWORK fails to become profitable, goes into receivership, and the vast databases of private information are identified by the administrators as the organisation's most valuable asset.
In contrast, a Wave infrastructure, like DNS, will distribute the upkeep and storage of private information to many (hopefully) locally trustworthy systems. Because of social engineering / hacking attacks, leakage of private information can and will still occur, but the impact should hopefully be minimized if the Wave protocol and its implementations have been suitably well engineered.
Would be great if Google had added encryption into the protocol by default, it would make it so much better. Its a nice step to P2P the chat network, but its just stupid to send all the conversation unencrypted specifically in corporate situations.
I get the feeling this could blur quite a few distinctions regarding protocol-based traffic monitoring (shaping, legal persecution, etc.). What if some dastardly person occasionally put a video stream or audio stream into the workspace, for instance...
TLS sounds about right.
The protocol also provides a verification protocol (see http://waveprotocol.org/ [waveprotocol.org]), so actions performed by any participant in a hosted conversation can always be verified by other participants in that hosted conversation, regardless of their provider.
What this means for you: encryption (TLS), and your contributions can't be tampered with.
The protocol also provides a verification protocol (see http://waveprotocol.org/ [waveprotocol.org]), so actions performed by any participant in a hosted conversation can always be verified by other participants in that hosted conversation, regardless of their provider.
What this means for you: encryption (TLS), and your contributions can't be tampered with.
What about PFS and deniable encryption so things can't be used against you in the future?
yeah, with HTML5, encryption is easy. You just surround any content you want encrypted with <secure>credit card number goes here</secure> and the magic of HTML does the rest!
Well, no, it is completely different, other than having avatars and thumbnails. photophlow are flickr photos with a javascript chat. Wave are XML documents which are kept in sync via collaborative editing "protocols", and those documents can be text conversations, maps, videos, gadgets or any other thin.
They always release their software for Windows first. Will this be the same? I wonder...
Considering Wave is an online service, it would be pretty difficult for them to make it Windows-only. None of Google's other Web pages are Windows-only.
Perfect... (Score:5, Insightful)
Re:Perfect... (Score:5, Funny)
Pride 'N Prejudice RPGs? I wanna be Mr. Collins he had his choice of babes.
Parent
Re:Perfect... (Score:4, Funny)
Parent
Re: (Score:3, Interesting)
Pride 'N Prejudice RPGs?
A Pride and Prejudice and Zombies [wikipedia.org] RPG would be pretty sweet.
Re: (Score:3, Funny)
Public warning (Score:5, Funny)
Make the client Windows-only again and you'll feel my wrath!
(Reply by Google: What are you going to do, quit gmail? Ouch! )
Re:Public warning (Score:5, Funny)
Parent
Re: (Score:3, Informative)
It will be in beta for 5 years. So you have no grounds to complain about anything for a long long time.
Not necessarily [slashdot.org]!
Re:Public warning (Score:5, Informative)
Screenshot here~ [blogspot.com]
Parent
Re: (Score:3, Funny)
Make the client Windows-only again and you'll feel my wrath!
(Reply by Google: We know where you live. )
Fixed that for you.
Re:Public warning (Score:5, Funny)
There. Really fixed.
Parent
Re:Public warning (Score:5, Insightful)
Actually, you did fix it.
Google tracks you online.
Google knows what you watch, what you read, what medical conditions you search on, reads the emails you send to your mom, knows where you live and what color frisbee is stuck on your roof, and soon will track every phone call you make from the gphone.
Replace "google" with "the feds" and I bet we'd all... oh, no, nevermind, I just remembered, we all trust big corporations...
Parent
Groove ? (Score:3, Insightful)
Re:Groove ? (Score:5, Insightful)
I think that real-time collaboration is a flawed concept in most contexts. People are not at their best when they have to be creative, inventive, or thoughtful in real-time with an audience. Nor do people do their best analysis when they're sitting around a (virtual) whiteboard.
Asynchronous collaboration tools are always going to be more important than synchronous ones; synchronous is better for broadcast and one-to-many communication.
Parent
Re: (Score:3, Interesting)
Re:Groove ? (Score:5, Interesting)
People are not at their best when they have to be creative, inventive, or thoughtful in real-time with an audience.
I'd be interested for you to elaborate on why you believe this. There's plenty of counter-evidence to this point in that the following practices are time-tested ways of creative thinking:
- comedy writers bouncing ideas off each other to start penning a script or sketch
- group brainstorming for new names of products and advertising ideas
- new product ideation amongst engineers
I'm sure everyone is different, and some prefer quiet solitude to be creative, but it seems the exception rather than the rule in most organizations. I personally find that people tend to be much more cautious and defensive when they have time to craft a well thought out idea, as opposed to blurting out a potentially stupid/creative idea.
Parent
Re: (Score:3, Interesting)
It's strange that you think that - real (actual physical) whiteboards are great for engineers and scientists. There is still a division between people who are happy thrashing ideas out on a board, and those who feel that they need to nurture something in private. I have to ask whether your comments about the environment being poor for research and insight are limited to virtual whiteboards or if they extend to their real-life counterparts?
So where do you think virtual whiteboards break down? Is it the lack
Gmail (Score:2, Funny)
Ugh (Score:5, Funny)
It's like email and twitter and instant messaging and facebook all in one.
Disgusting.
Re: (Score:3, Insightful)
Re:Ugh (Score:5, Insightful)
Except maybe it will be what something like Twitter, Facebook, and IM should have been from the beginning. For one thing, it sounds like it will be open and decentralized, meaning that I can set up my own Wave server, and you can set up your own Wave server, and our users can talk without any problems.
You can already do that with IM so long as we're all using Jabber, but otherwise it can get a little problematic. But I can't set up my own private facebook or twitter server, and even if I do, there's not support for my server to let people befriend and network with people on the real Facebook and Twitter.
To me, that's always been the #1 problem with social networking sites on the Internet. You can't set up your own, but instead your left to make a new account on whatever site is cool this week. Like what if instead of being able to set up my own webpage, I had to set up a webpage on whatever hosting company was trendy, and then rewrite it based on that host's protocols?
Parent
Re: (Score:3, Interesting)
But I can't set up my own private facebook or twitter server,
Twitter -- I see no reason why this couldn't be just Jabber to some sort of broadcast channel.
Facebook -- XFN, OpenID, and friends.
even if I do, there's not support for my server to let people befriend and network with people on the real Facebook and Twitter.
That's the real problem.
There's a whole set of open standards that pretty much covers all of what social networks do for the user. But for some reason, most users are still in the gated community of Facebook, so even though the open communities could theoretically be bigger, better, and freer, right now they're smaller, because they're not Facebook.
But what makes you think this
Re:Ugh (Score:4, Interesting)
By setting up your own you're destroying the networking aspect.
A private site for friends will never have the pull of a world-wide LOOK AT MEEEEEEEEEEEEEEEE site.
Accurate, insightful.
If that's what you want, great, go for it. But I seriously doubt that's what Google has in mind. They want all of your data, and this is just another tool for them to get at it.
Controversial point. Trying to spread fear, whether or not it's justified. The following couple of paragraphs present some interesting speculation.
Regardless of function or intention, my comment still stands (despite being modded troll by Googs) - the layout shown is hideous and provides nothing but total information overload.
If there's anything in your post to warrant a troll mod, this is it.
You post here a lot, and you don't trouble yourself to be terribly civil. Not that that's uncommon, but I think it's a shame. Your ideas seem generally worthwhile, but your attitude probably limits their discussion. Geeks and engineers are probably more likely than most to pay attention to the factual accuracy of any statement instead of the emotional context; the opposite is the rule in other circles. If I may offer some advice: if you're going to be callous, be right, and even if you are right, don't bitch about the troll mods.
Respectfully yours,
-T
Parent
Re: (Score:3, Interesting)
I can set up my own Jabber server and talk to people on Google's GoogleTalk or Gmail chat. In fact, that's what I do except I'm using jabber.org's server. Of course, Google still gets your conversations with those people, but not if you use OTR.
This sounds like the potential that Jabber/XMPP has always had, but no one seems interested to implement.
Re:Ugh (Score:4, Informative)
By setting up your own you're destroying the networking aspect.
A private site for friends will never have the pull of a world-wide LOOK AT MEEEEEEEEEEEEEEEE site.
Er... no. You could set up social networking standards and protocols that would allow various sites to enable their users to build profiles which could then be shared in a manner very similar to facebook. You'd want some kind of common authentication (OpenID) if you don't want all the profiles to be public. If anything, I'd say that by keeping a private little proprietary system, they're limiting the networking aspect.
They want all of your data, and this is just another tool for them to get at it.
...except that it sounds like they're making it all pretty open. From TFA, "The code will be open source, and developers intending to build on the platform are being given access to APIs, according to a post on the official Google blog."
So you can build your own implementation, and the whole thing is going to be P2P, so Google won't necessarily have access to your data unless you're specifically using their server.
the layout shown is hideous and provides nothing but total information overload.
Well first, I don't agree that it's so awful. Second, it's pre-release and not even a public beta. Third, it's going to be open source so you can skin it or completely rewrite the interface.
Sounds good to me.
Parent
Re:Ugh (Score:5, Funny)
Parent
Re:Ugh (Score:5, Funny)
Parent
Uhhh. SIP Anyone? Anyone? (Score:4, Interesting)
So, they use SIP to chat and handle voice. There's a protocol for presentation that's rolled into some SIP servers. You guys have no idea how powerful the SIP standard is. There isn't a client that handles it all yet.
Besides the very un-special nature of the application, I'd be interested to see if the Telcos will litigate Google on their gigantic pool of obvious patents. Either that or Google's paying them a 'vig' already.
quite needed... (Score:4, Insightful)
Firefly (Score:5, Funny)
Re:Firefly (Score:5, Informative)
Here: http://www.fireflywiki.org/Firefly/CortexLexicon
Scroll down to "wave".
Parent
Patent License? (Score:5, Interesting)
It's this [waveprotocol.org] I find most interesting:
Subject to the terms and conditions of this License, Google and its affiliates hereby grant to you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this License) patent license for patents necessarily infringed by implementation of this specification. If you institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the implementation of the specification constitutes direct or contributory patent infringement, then any patent licenses for the specification granted to you under this License shall terminate as of the date such litigation is filed.
Cool. (Score:5, Insightful)
If I'm reading this right, it looks like patent MAD. Basically, Google is saying, "If you sue anyone for patent infringement about this spec, you give us the right to sue you. If you don't sue anyone, we're cool."
The implicit threat is, of course, that Google will own as many patents regarding this spec as anybody, but as long as nobody exercises them, it doesn't matter -- they're still allowed, for this spec.
Which is both very cool, and raises some interesting questions -- like, what if I implement the spec as part of a much larger app, and someone sues me for infringement of a different part of the app? Or, what if I want to create a modified version of the spec, or create a wholly unrelated application that infringes on patents related to this spec -- do I open myself up to lawsuits then?
Parent
Messyboard anyone? (Score:5, Interesting)
This reminds me of a PhD thesis I read about a few years back. Adam Fass' Messyboard [messyboard.org]
MessyBoard is a networked bulletin board that allows people to share notes, pictures, files and other content. Everyone who looks at a MessyBoard sees exactly the same thing, and all users see changes in real time. It runs as a Java applet inside your web browser, so no software installation is necessary. Text and images from other applications can easily be posted on MessyBoard using drag-and-drop and cut-and-paste. Each board has a URL that is easy to remember, so you can access it from any computer on the Internet.
MessyBoard stores a complete history of all activity, allowing users to go back in time and recover old content simply by clicking on a slider bar.
Coincidentally, Fass now works for Google in WA state.
Google is also... (Score:5, Funny)
Re:Physics humor :) (Score:5, Funny)
Traffic Cop: Mr Heisenberg, do you have any idea how fast you were driving?
Heisenberg: No, but I know exactly where I am
Parent
Sounds good for playing RPGs online (Score:3, Interesting)
This could be a cool tool for playing RPGs (of the pen and paper variant) online.
Use the chat or Skype for talking, and the Wave functions for posting maps and stuff, and clients for rolling dice and such.
Hotline all over again (Score:5, Funny)
countdown to this being used for warez and porn ... 3 ... 2 ... 1
Serious threat to Facebook, Twitter, et al (Score:5, Insightful)
The decentralised nature of this system will directly threaten Facebook, Twitter et al.
The DNS system works, and scales, because everyone publishing information to the DNS is responsible for the upkeep of the nodes that publish their own records.
Facebook and Twitter, however, have scaling and financial problems. Facebook, so far as I am aware, continues to make a substantial annual loss despite its enormous success, and I have yet to hear that Twitter has managed to turn a profit.
More importantly, the privacy of everyone publishing much of their personal, private correspondence using a small number of centralized agencies is directly threatened -- and it could get particularly messy if, in a few years time, $SOCIALNETWORK fails to become profitable, goes into receivership, and the vast databases of private information are identified by the administrators as the organisation's most valuable asset.
In contrast, a Wave infrastructure, like DNS, will distribute the upkeep and storage of private information to many (hopefully) locally trustworthy systems. Because of social engineering / hacking attacks, leakage of private information can and will still occur, but the impact should hopefully be minimized if the Wave protocol and its implementations have been suitably well engineered.
This is going to be interesting.
Please kill "One Note" (Score:4, Insightful)
If this could kill Microsoft One Note that would be so nice. :)
Re:first (Score:4, Insightful)
Would be great if Google had added encryption into the protocol by default, it would make it so much better. Its a nice step to P2P the chat network, but its just stupid to send all the conversation unencrypted specifically in corporate situations.
Parent
Muddying the waters... (Score:5, Interesting)
Parent
Re:first (Score:5, Informative)
From my reading, they're requiring TLS on the XMPP stream, which pretty well covers encryption.
Parent
Re:first (Score:5, Informative)
Parent
PFS and deniable encryption (Score:3, Interesting)
TLS sounds about right.
The protocol also provides a verification protocol (see http://waveprotocol.org/ [waveprotocol.org]), so actions performed by any participant in a hosted conversation can always be verified by other participants in that hosted conversation, regardless of their provider.
What this means for you: encryption (TLS), and your contributions can't be tampered with.
What about PFS and deniable encryption so things can't be used against you in the future?
http://en.wikipedia.org/wiki/Perfect_forward_secrecy
html 5 and encryption? (Score:3, Funny)
Re:html 5 and encryption? (Score:5, Funny)
yeah, with HTML5, encryption is easy. You just surround any content you want encrypted with <secure>credit card number goes here</secure> and the magic of HTML does the rest!
Parent
Re:html 5 and encryption? (Score:5, Informative)
Parent
Re: (Score:3, Informative)
Well, no, it is completely different, other than having avatars and thumbnails. photophlow are flickr photos with a javascript chat. Wave are XML documents which are kept in sync via collaborative editing "protocols", and those documents can be text conversations, maps, videos, gadgets or any other thin.
Re:Windows Only? (Score:5, Informative)
They always release their software for Windows first. Will this be the same? I wonder...
Considering Wave is an online service, it would be pretty difficult for them to make it Windows-only. None of Google's other Web pages are Windows-only.
Parent