Netizen: Open source

Showing posts with label Open source. Show all posts

Tuesday, June 23, 2009

I Did My Part

I protested. I did my part. If the protests are not going to work, and the ban on me at the Google Wave API Google Group is not going to be lifted, I move on. I guess I will have to find out other ways to spot trends in Google Wave development. I am sure there will be several good blog options. We are at the early stages of seeing blogs dedicated completely to Google Wave. Maybe some of those bloggers will do the reading for me in those Google Groups.

A great way to follow an open source project is in the very open perhaps.

Google Wave API Google Group: Got To Undo The Ban On Me

Monday, June 22, 2009

Google Wave API Google Group: Got To Undo The Ban On Me

Google Wave Protest
Google Wave API Google Group: Stalinist Mindset

Einstein was attacked by some with anti-Jewish leanings. When a pamphlet was published entitled 100 Authors Against Einstein, Einstein retorted "If I were wrong, one would be enough."

The name is clear enough: Google Wave API. It is a group about Google Wave API. So if

Image by dailylifeofmojo via Flickr

you are going to post messages about viagra ads and Nigerian dictators who need help with money transfer, then you don't belong in the group. So I am not trying to argue it is my human right to belong to the group.

The initial protest was that it was a group for hard core code talk. I respect the sentiment. But there were numerous threads about spam, t-shirts and invitations to Wave. Noone seemed to have been bothered, bothered enough to protest and ban people.

The Google Wave Developer Community Will Be Vibrant
Five Blind Men And Google Wave
A Little Trouble At The Google Wave API Google Group
Lessons From The Open Source Community For The Wave Community
Google Wave Developer Community: Asking For A Culture?
The Google Corporate Culture

The third thing I established was that code and community/culture are both on par, they are both important. You can not expect to have strictly technical conversations and still exp

Image by niallkennedy via Flickr

ect to create waves with Google Wave. And then I offered to stick my vision, culture and community talk to one out of the 300 plus threads in the group.

Then they said, it is not what you are saying, it is how you are saying it. Why do you post links to your blog posts in this group? People who don't "get" links and blogs should voluntarily walk away from a group about Google Wave development.

The slam dunk was I said but my primary interest is in code talk. That is why I joined the group in the first place. I wish to follow all the code related conversations so I can spot trends in Wave development over the coming months as we prepare to unleash Wave upon the world.

And so I am going to keep protesting until they undo the ban on me in the Google Wave API Google Group.

The Google Corporate Culture
Google Wave: Organizations Will Go Topsy Turvy
Google Wave: Enormous Buzz
Possible Google Wave Applications And Innovations
Google Wave Architecture: Designed For Mass, Massive, Global Innovation
The Google Wave Architecture
Google Wave Ripples
Is Google Wave Social Enough To Challenge Facebook, Twitter?
Of Waves And Tsunamis
Google Wave: Wave Of The Future?
Google Wave: If Email Were Invented Today

From The Google Wave Developer Blog

TwilioBot: Bringing Phone Conversations into Waves
1 Wave Sandbox, 5 Hours, 17 Awesome Demos

Image by niallkennedy via Flickr

The Making of the Sudoku Gadget
Google Wave API Office Hours
Google Wave team heads to Google Developer Days in Asia
Introducing the Google Wave APIs: what can you build?

From The Official Google Blog

Went Walkabout. Brought back Google Wave

Monday, June 15, 2009

A Little Trouble At The Google Wave API Google Group

Needed: A Culture For Wave Developers
By paramendra - 9:25am - 6 authors - 9 replies

Brain. Or maybe you should just go ahead and ban me since looks like you deleted my past three or four posts.

I started this thread that in its title very clearly says this particular thread is about the community aspects, not the code aspects. So those developers who are only interested in the code aspects will not even bother clicking on this thread. I thought t-h-a-t was fair enough.

I have been in the process of establishing the fact that code and community are both important. That has been true for Google Corporate, and the open source communities. That is going to be true for the Google Wave Developer community as well. Google Corporate is 20,000 strong, about 50 out of 20,000 devoted to Wave. The Wave developer community on its own is going to be larger than 20,000. And you are going to tell me talking about code is enough?

I don't know where you stand in the Google Wave Corporate hierarchy, but the official Google Wave Developer Blog has linked to my blog posts on the importance of a culture for the developer community at the bottom of every single of their posts as of now. Go take a look. http://googlewavedev.blogspot.com

And my original Google Corporate Culture blog post that you so derided has been a hit on Twitter, and is at the bottom of all the latest 30 plus of the posts at the official Google Blog itself. http://googleblog.blogspot.com

Now can we please repost my posts at this thread that you went ahead and deleted?

And how primitive is it to suggest you can post words but not links to your blog posts? Links are what the internet is all about. How, Sir, did you miss that part? Links are the center of gravity in Google's PageRank concept. Links are what make Twitter Twitter, it is not the 140 character limit.

I have come to this Google Group with a very clear goal, which is to share in the excitement of Google Wave - the next big thing in web technology - and to help shape its developer community, especially its culture aspects, and to try and spot and popularize trends related to Wave, especially as they might sprout out from the developer community.

Your basic respect for free speech would be much appreciated.

I just went around and looked at the subject titles of many of the other threads at this forum. My thread is more on-topic than most. Most of the threads so far seem to be about wanting in on a Google Wave account. That's code talk? Come on, man.

Paramendra Bhagat
http://technbiz.blogspot.com

Google Wave Developer Community: Asking For A Culture?
The Google Corporate Culture
Google Wave: Organizations Will Go Topsy Turvy
Google Wave: Enormous Buzz
Possible Google Wave Applications And Innovations
Google Wave Architecture: Designed For Mass, Massive, Global Innovation
The Google Wave Architecture
Google Wave Ripples
Is Google Wave Social Enough To Challenge Facebook, Twitter?
Of Waves And Tsunamis
Google Wave: Wave Of The Future?
Google Wave: If Email Were Invented Today

From The Google Wave Developer Blog

1 Wave Sandbox, 5 Hours, 17 Awesome Demos
The Making of the Sudoku Gadget
Google Wave API Office Hours
Google Wave team heads to Google Developer Days in Asia
Introducing the Google Wave APIs: what can you build?

From The Official Google Blog

Went Walkabout. Brought back Google Wave.

Lessons From The Open Source Community For The Wave Community

Lessons on Community Management from the Open Source World, Angela ... Fostering the Drupal community is actually more important than managing the code base. ........ the success of healthy open source projects defies all logic. Scores of individuals from all over the world, all of whom have different skill levels, use cases, experience, native languages, and time zones, collaborate together in order to help make a project succeed. ........... How is it that all of this chaos comes together and creates something wonderful and useful? ........ a diverse, passionate, and vibrant global community. ......... Create a Great Community and Great Code Will Follow .......... the project's developers, but also to those who report bugs, review fixes, answer support requests, design interfaces, provide translations, help with marketing and evangelism, and write and edit documentation. ............. Many key individuals who are driving forces within open source projects got their start by fixing typos in documentation or answering other users' support questions. ......... A culture that values a well-written tutorial as much as a well-written application programming interface (API) is much more likely to attract and retain newcomers than a culture that values seasoned developers, or the marketing team, at the expense of everyone else. ............... the difficulty in managing a community of strongly independent individuals, each with their own motivations. .......... contributing can directly or indirectly lead to paid work which acts as another long-term retention tool. ............ people won't get the peer reviews they require to accomplish their goals by being arrogant, insulting, and demeaning towards others. ............ The sooner a frustrated user realizes that there is only a collective “we" where each contributes whatever they can to make the project better, the sooner the transformation into contributor can take place. Users then learn to channel their frustration into an effective force for change. ............ The same peer review process that lends itself to building a strong community and great software can be terrifying to newcomers. .......... The natural problem-solving methodology for perfectionists tends to be withdrawal from the community and working quietly in isolation until they believe they've achieved something that is immune to criticism. This brings with it a whole host of problems ........................ their work can get permanently trapped in "analysis paralysis" and never see the light of day. ........... Working in isolation eliminates transparency ........... In a worst-case scenario, the larger community has already developed a solution to a problem in parallel by the time the perfectionist is finished, leading the perfectionist to extreme frustration, particularly if coupled with a deep attachment to their own solution. ........................... vital to establish a strong culture of “release early, release often” ............ a lack of attachment to any one solution so that the best possible solution is found. ...... The key difference that separates healthy perfectionist contributors from unhealthy ones is the participation in a collaborative problem-solving process, rather than an introverted one. ................ Focus on the people, not the product. A team that enjoys working with one another will naturally be more productive. Take a "mental health" check of the people on your team. Is there animosity brewing between two or more groups that could be solved by them working more closely together? Is decision-making in the hands of a single individual, hampering the feeling of ownership by other, capable people? Resolving these kinds of issues should take precedence over anything else. ............. fight red tape in all of its forms. Remember that a frustrated person is often best poised to lead revolutionizing changes for the better as they have the motivation. Get the road blocks out of their way and empower them to get to work. ........... Put processes in place that help prevent perfectionists from getting trapped in their own heads, and get them working with others instead."

I have been part of a conversation at the Google Wave API Google Group where I have been trying to suggest community is as important as code, and so there has to be talk of the culture of the Wave developer community. Many have disagreed saying code is all that matters. Some have said community also matters but maybe you don't know enough to be talking community either. I don't know what I don't know. But vision and group dynamics are specialties all their own.

The last suggestion I made was, let's have 100 threads on purely technical issues, and I hope to develop my technical chops along the way, but let's have one thread where we talk about fluffy issues like vision and community. Code and community do belong at the same forum.

Once it is established that both code and community are important, we can then move on to studying the lessons of the open source communities past so as to distill from their best practices, because the Wave developer community, culturally speaking, has more in common with the open source communities than any of the corporate ones.

Building a community of developers is not just about code.

I am not trying to lead or follow. I am just trying to be part of the conversation, to learn from the conversation, to contribute to the conversation.

Google Wave Developer Community: Asking For A Culture?
The Google Corporate Culture
Google Wave: Organizations Will Go Topsy Turvy
Google Wave: Enormous Buzz
Possible Google Wave Applications And Innovations
Google Wave Architecture: Designed For Mass, Massive, Global Innovation
The Google Wave Architecture
Google Wave Ripples
Is Google Wave Social Enough To Challenge Facebook, Twitter?
Of Waves And Tsunamis
Google Wave: Wave Of The Future?
Google Wave: If Email Were Invented Today

From The Google Blogs

1 Wave Sandbox, 5 Hours, 17 Awesome Demos
The Making of the Sudoku Gadget
Google Wave API Office Hours
Google Wave team heads to Google Developer Days in Asia
Introducing the Google Wave APIs: what can you build?
Went Walkabout. Brought back Google Wave.

Sunday, June 14, 2009

Google Wave Developer Community: Asking For A Culture?

Google is about to get a vibrant developer community around Wave. This is a first for Google in terms of how big one can expect it to be. I guess the Android developer community also counts. The two can be considered the first among equals. But a mobile operating system was not something fundamentally new, Wave is.

There are about 20,000 people working for Google, many of them coders. Google has some of the smartest coders in the world. But not all of the smartest coders in the world work for Google. Most don't. It is a numbers game. Google is not big enough to house all the smartest coders in the world. Many of the smartest are soloists, or small group types who gutturally abhor anything corporate. The open source community appeals to many of them.

Image via CrunchBase

The Wave community will be a great platform for them. The top developers will make mega bucks. They will make much more than the late coming engineers at Google.

So if the Wave developer community is going to be larger than Google Corporate, and if many members of that developer community will make mega bucks, you have to ask, does that developer community need a culture? A codified value system? Will that evolve on its own? Or will each small group within that community have a slightly distinct culture and value system of its own?

Microsoft has had a developer community around Windows for as long as Windows has been around. The budding Wave community will be similar, only much, much bigger.

I take it for granted that a value system will emerge, just like a market will emerge. It will not be top down. It will not be something dictated by Google Corporate. It will be grassroots. It will likely be diverse. But it will emerge. It will have more in common with the unregulated, uncorporate open source community than Google Corporate. But that is no harbinger of clashes. The two cultures can create a happy symbiosis. That is precisely why just like it has been important to articulate the Google corporate culture, (The Google Corporate Culture) I think it is important to try and articulate the developer community culture.

Members of this developer community are more likely to show up for their local Wave MeetUps than jamborees at Googleplex, if only because the community will be global and scattered. Much of the community action will be online.

The Google Corporate Culture
Google Wave: Organizations Will Go Topsy Turvy
Google Wave: Enormous Buzz
Possible Google Wave Applications And Innovations
Google Wave Architecture: Designed For Mass, Massive, Global Innovation
The Google Wave Architecture
Google Wave Ripples
Is Google Wave Social Enough To Challenge Facebook, Twitter?
Of Waves And Tsunamis
Google Wave: Wave Of The Future?
Google Wave: If Email Were Invented Today

From The Google Blogs

1 Wave Sandbox, 5 Hours, 17 Awesome Demos
The Making of the Sudoku Gadget
Google Wave API Office Hours
Google Wave team heads to Google Developer Days in Asia
Introducing the Google Wave APIs: what can you build?
Went Walkabout. Brought back Google Wave.

Thursday, June 04, 2009

Google Wave Architecture: Designed For Mass, Massive, Global Innovation

The technologies behind Google Wave have been designed to bring desktop like experiences into the browser paradigm, but end up doing more than that. The shift and growth are so sure and certain soon we will be missing browser like experiences while on the desktop. Why can't I don this with a desktop client?

The browser is about to take off. The richness will only grow. The speeds will only get faster. The bandwidths will go way up. The masses of people involved will go up both on the production and the consumption sides, and there will be not be any distinct boundary between the two.

The desktop was designed for one person. The browser was always meant for the masses, for crowds. Finally the promise is catching up with capabilities.

This is barely the beginning. Google Wave is three things: a tool, a platform and a protocol. There are many ways to use Google Wave as it exists today. There can be much innovation in how it gets applied. It is the difference between Blogger the service and all sorts of wonderful blogs you end up with. And then there are the platform and protocol aspects. Get geared for major technological leapfrogs. Here it is the difference between the iPhone and all its many applications, it is the difference between Hotmail and Gmail.

The Google Wave Architecture
17 Suggestions To Blogger
Square Search
Google Wave Ripples
Is Google Wave Social Enough To Challenge Facebook, Twitter?
Blogger Search Gadget: What Took You So Long?
Of Waves And Tsunamis
Google Wave: Wave Of The Future?
Google Wave: If Email Were Invented Today

From The Google Blogs

Google Wave team heads to Google Developer Days in Asia
Introducing the Google Wave APIs: what can you build?
Went Walkabout. Brought back Google Wave.

On The Web

InfoQ: Google Wave's Architecture Google Wave is three things: a tool, a platform and a protocol. The architecture has at its heart the Operational Transformation (OT), a theoretical framework meant to support concurrency control. ....... based on hosted XML documents (called waves) supporting concurrent modifications and low-latency updates. ...... using JavaScript and HTML5 on the client side ....... Java + Python on the server side ..... a public API and the company promises to open source the entire platform ......... modify the base code and extend it with gadgets and robots. ....... Gadgets are small programs running inside of a wave, while robots are “automated wave participants.” Wave can also be embedded in other mediums like blogs. ....... Each wave has a globally unique wave ID and consists of a set of wavelets. ...... A wavelet has an ID that is unique within its containing wave and is composed of a participant list and a set of documents. The wavelet is the entity to which Concurrency Control / Operational Transformations apply. ....... A participant may be a user, a group or a robot. ....... Documents form a tree within the wavelet. ....... the crucial part of Wave’s technology. Google Wave makes extensive use of Operational Transformations (OT) which are executed on the server. ....... Operations are sent to the server and propagated to each client on a character by character basis ......... To start communicating on a wavelet, a client sends an Open Request containing the Wave ID and the Wavelet ID to the server. The server responds with a snapshot - the serialized state of the wavelet - or a history hash of the corresponding version. ........ The Google Wave Federation Protocol allows multiple entities (wave providers) to share waves with each other.
InfoQ: Is Google Wave Going to Have an Impact on RIA/Silverlight? Wave is actually a competitor for Microsoft’s SharePoint and Exchange ....... Flash, Silverlight and Java FX ...... Some of the new features to be introduced in HTML 5 and web API proposals from W3C and WHATWG are: canvas, video, geolocation and web workers. ........ Wave which is making extensive use of HTML 5. ....... the company is “betting big on HTML 5”. ...... The Wave client is a major proof of concept (or pilot project) for HTML5. If the wave client becomes a killer app, it will have a major (negative) impact on other RIA architectures. ....... Microsoft Silverlight vs Google Wave: Why Karma Matters ........ “Microsoft just has so much bad karma in this industry that I cannot imagine a company like us trusting them on much of anything.” ........ today, it is Google which is driving web standards forward. ....... HTML5 is a working draft still. ....... people have to use those new browsers. The slowness of standards leads me to believe that RIA platforms will be around a while ....... “[Wave] is more about competition with Exchange + IM + OneNote w/Sharepoint Integration + Outlook”. ........ The primary reason we want to open source our code is actually adoption of the protocol. ....... Wave's effect on Silverlight is indirect. HTML will enter in the RIA space with HTML 5, taking a share from Flash and Silverlight. Google's heavy support for HTML 5 will contribute to that.
Google Wave Architecture | High Scalability hosted XML documents (called waves) ..... users from different wave providers can communicate and collaborate using shared waves
Google Wave Federation Architecture ‎(Google Wave Federation ... the Google Wave Federation Protocol for federating waves between wave providers on the Internet. ........ various elements of Google Wave technology - data model, operational transformation, and client-server protocol ...... The wave federation protocol enables everyone to become a wave provider and share waves with others. ....... A robot is an automated participant on a wave (see the robots API). Examples are translation robots and chess game robots. ........ A gateway translates between waves and other communication and sharing protocols such as email and IM. ....... Different wavelets of a wave can have different lists of participants. ......... there is a designated wave provider that has the definitive copy of that wavelet. We say that this particular provider is hosting that wavelet. ......... different users have different wave views for a given wave. ...... the user's read/unread state for the wave, is stored in a user-data wavelet ....... A wave is identified by a globally unique wave id, which is a pair of a domain name and an id string. ......... Like a wave id, a wavelet id is a pair of a domain name and an id string. ......... Wavelets in the same wave can be hosted by different wave providers. ........ a federation gateway and a federation proxy. ........... "local wavelet" and "remote wavelet"
Salesforce rides on Google wave : News : Software - ZDNet Asia
Google Wave Architecture
Google's move to introduce a Wave of synchronicity | Web Apps News ...

Thursday, May 28, 2009

Google Wave: If Email Were Invented Today

Stream 2.0: The Next Big Thing?

Google Wave

The browser is going 3D.
The browser is adding layers.
Email is going hyper social and real time.
Email will be rich.

The whole thing is open source. I think that is a great business model for Google to pursue.

Google Wave is in some ways more fundamental than Gmail. It could redefine the workspace.

On the other hand, connecting is not the same as thinking. Gelling a thought, the truly innovative ideas, where do they come from? But then those fall in the human realm.

Google might have missed out on Facebook and Twitter, but it has now yet again managed to find the next big thing. Bravo. There is no web company quite like Google just like there was no desktop company quite like Microsoft.

What would be a wave liberated from the keyboard? What would be an audio only version? Is that what a conference call is?

What after Wave? What would be the next big thing?

Facebook has a long way to go, in terms of a tool for not only discovering relationships, but deepening them.

Google Search has a long, long way to go. Search remains the most fundamental application on the web. Search could be so much better than it is now.

People search, what about people search?

So tell me, what is a conversation? What is a document?

This is about simplifying life. Some people don't sign on to some social networking sites saying they don't want yet another thing to have to keep up with.

Another thing to integrate into wave would be search result snapshots. These are the 10 links you get on Google News for Obama as of such and such date and time.

Cultural habits die hard.

I also feel like old email will not go away.

Google Wave is the ultimate mashup application.

It is amazing that a small, five person team worked on this to start with. But then is that not how it almost always happens?

"Never doubt that a small group of thoughtful, committed people can change the world. Indeed, it is the only thing that ever has."
- Margaret Mead.

On The Web

Google Wave Preview
Google Wave Drips With Ambition. A New Communication Platform For ... the HTML 5 standard ..... the ability to run 3D games and movies in the browser without additional plug-ins ...... born out of the idea that email and instant messaging, as successful as they still are, were both created a very long time ago ..... sleek and easy way to navigate and participate in communication on the web that makes both email and instant messaging look stale ...... your Wave inbox ....... it isn’t just about new messages, there can be any kind of new content in these waves. ......... your friend will see words as you enter them, and vice versa ...... You can also edit things wiki-style with concurrent group collaboration. ........ (”Modern” is Google’s passive aggressive way of calling out Microsoft’s Internet Explorer.) ........ Google Maps (that you can edit), games, event invitations ....... wants you to be able to use it across all sites on the web ..... you could share a wave with the public ........ Google doesn’t want Wave to be another one of its apps, it wants Wave to be a communication platform that it may have started, but flourishes all over the web in a bunch of different places. ............ Bill Gates’ early insistence on having a robust developer community as one of the keys to the success of Windows ........ emphasis on developers is helping newer platforms like Android and the iPhone grow. ...... in short order, there will be a ton of gadgets, extensions, mash-ups and interesting sites all built around the Wave concept. ........ Waves created by someone communicating with Waves created by someone else ....... Google plans to open source Wave. ...... the key fundamentals Google is focusing on with HTML 5: The canvas element, the video element, geolocation, App Cache and Database and Web Workers. ......... the Web Workers. ....... run background processes outside of the browser so it doesn’t slow to a crawl which running very rich apps — which Wave is. ........ Web Workers helps turns the browser into a more full-fledged launch pad for the next generation of web apps. ..... Wave will work with Twitter ...... a wave that can translate to other languages in real-time.
Introducing the Google Wave APIs: what can you build? Google Wave Developer Blog The Google Wave APIs come in two flavors: Embed and Extensions. With Embed, you're able to bring waves into your own site through a simple JavaScript API. For example, embedding a wave in a webpage is a good way to encourage a discussion among the visitors. With Extensions, you're able to write programs, which are packaged as Robots or Gadgets, that provide rich functionality inside the Google Wave web client.
Official Google Blog: Went Walkabout. Brought back Google Wave. We had a blast the next couple years turning Where 2's prototype mapping site into Google Maps.

Why do we have to live with divides between different types of communication — email versus chat, or conversations versus documents?
Could a single communications model span all or most of the systems in use on the web today, in one smooth continuum? How simple could we make it?
What if we tried designing a communications system that took advantage of computers' current abilities, rather than imitating non-electronic forms?

.... five-person "startup" team emerged with a prototype .... you create a wave and add people to it. Everyone on your wave can use richly formatted text, photos, gadgets, and even feeds ........ you see on your screen nearly instantly what your fellow collaborators are typing in your wave. ........ As with Android, Google Chrome, and many other Google efforts, we plan to make the code open source ....... Google Wave has three layers: the product, the platform, and the protocol:

The Google Wave product (available as a developer preview) is the web application people will use to access and edit waves. It's an HTML 5 app, built on Google Web Toolkit. It includes a rich text editor and other functions like desktop drag-and-drop (which, for example, lets you drag a set of photos right into a wave).
Google Wave can also be considered a platform with a rich set of open APIs that allow developers to embed waves in other web services, and to build new extensions that work inside waves.
The Google Wave protocol is the underlying format for storing and the means of sharing waves, and includes the "live" concurrency control, which allows edits to be reflected instantly across users and services. The protocol is designed for open federation, such that anyone's Wave services can interoperate with each other and with the Google Wave service. To encourage adoption of the protocol, we intend to open source the code behind Google Wave.

.... the Google Wave Developer blog
Google Wave ichly formatted text, photos, videos, maps ...... combine Gmail and Google Docs ...... "Back in early 2004, Google took an interest in a tiny mapping startup called Where 2 Tech, founded by my brother Jens and me. We were excited to join Google and help create what would become Google Maps. .......... richly formatted text, photos, gadgets, and even feeds from other sources on the web. ....... allows for both collaboration and communication. You can also use "playback" to rewind the wave to see how it evolved. .... Google Wave will be available later this year.
MoMB: Google Wave
Gizmodo - Google Wave Is a Frothy Collaborative Mix of Chat, IM ... a live chatroom with a spread of documents, photos and/or videos, where you can reply to any part of any message or anything that's shared, and it's all real-time. ..... free-wheeling mesh of Twitter, IM, Friendfeed really, any other kind of service presenting semi-real-time stuff in a stream ...... ultimate service for people with ADD, or enterprise looking to simulate the feeling of 10 people standing around a desk scattered with a bunch of projects, but you're all able to work on any of them simultaneously while you're also whispering to the cute girl across the table about the new sushi place around the corner
Google Wave: What Might Email Look Like If It Were Invented Today ... the power of HTML 5 to match functionality long experienced in desktop applications. ....... a profound advance in the state of the art. ...... this project, carried out secretly at Google's Sydney office over the past two years ....... messages no longer need to be sent from one place to another, but could become a conversation in the cloud ....... elements drawn from email, instant messaging, social networking, and even wikis. ....... Jens had the idea back in 2004, when Google first acquired the company that became Google Maps ........ email and instant messaging, were originally designed in the '60s to imitate analog formats — email mimicked snail mail, and IM mimicked phone calls. ....... email versus chat, or conversations versus documents ....... a single communications model ...... a communications system that took advantage of computers' current abilities, rather than imitating non-electronic forms ...... the amount and quality of participation goes up radically when comments can be interleaved at a paragraph level. ........ First generation email/IM integration let you see when someone was online, and opt to instant message someone rather than send them an email. Wave simply erases the distinction. ..... a lot of time in IM is spent waiting for the other person to press 'Done' ........ Google's relentless focus on reducing the latency of online actions is bringing the online experience closer and closer to our real world experience of face-to-face communication ....... Drop photos onto a wave and see the thumbnails appear on the other person's machine before the photos are even finished uploading ....... conversations become shared documents ....... you don't have to make the choice between discussing and collaborating ....... a document with lots of discussion and edits can become pretty messy. No problem. You can export an edited wave as a new wave, and start over. ........ "waves are tree-shaped sets of messages. You can shape a subtree, or a sub-conversation and limit the set of participants in any way you like." .......... Wave will become as ubiquitous and interoperable as email and instant messaging ...... a new fundamental service on the net. ...... web applications can not only match, but can even beat the functionality of native apps ......... commitment to the lightweight nature of the web, to real-time, to lightweight components connected by open protocols rather than to monolithic systems.
Twave: Google Wave + Twitter a potential game changer in the realm of of email, IM, and project management ..... Google Wave and Twitter are both forms of real-time communication, so why not bring them together? ....... a full stream of your Twitter feed within Google Wave. ........ you can manage them like you would email, with replies, archiving ....... Bloggy: Pushes wave content to a blog ...... Bidder: You can turn a Wave into your own eBay ....... The web is truly transforming into a real-time engine
Google Wave API - Google Code
A Sneak Peak at Google Wave

Pages