Adam Turner
Friday, 09 October 2009 08:50
Opinion and Analysis
Page 3 of 4
12:39 pm
me:
That's what I want as well, but it can already be done elsewhere. Are we reinventing the wheel inside Google Wave and thus fragmenting the web?
12:40 pm
Jacob Chapel:
Well technically the web is already fragmented, Wave intends to unify a lot of separate technologies or ideas into one place.
12:41 pm
me:
but inside Google Wave and locked away from the rest of the web, in an environment that Google controls?
12:41 pm
Jacob Chapel:
You have to remember that what we are experiencing now is not the intended usage of Wave. This is just a preview to test what would be an individual installation.
12:41 pm
me:
but will wave be exposed to the wider web like Wikipedia?
12:42 pm
Jacob Chapel:
From what I gathered public facing waves will be possible by embedding or other forms of sharing. I do not know the specifics on how they plan on implementing things, but it is only locked down so they can test it properly and not have a super glut of users they cannot control.
12:43 pm
me:
It still seems like we're putting a lot of content into a walled garden of sorts, something we moved away from a long time ago
12:43 pm
Jacob Chapel:
We still face the walled garden issue with Facebook and Myspace, not to mention other major players. Even Twitter isn't the most open place to put your data.
12:44 pm
me:
yeah, but they're all "look at me" social media sites - Google Wave has the potential to be a repository of actual knowledge. Maybe I think that because the wiki/forum approach to Google Wave seems the most practical to me at this point.
12:46 pm
Jacob Chapel:
Thats the thing though, I do not see why waves couldn't be public facing. That comes with the permission controls that they need to implement. They have said that some intended usages were for instance blog comments.
CONCLUDED on Page 4
