I think Wave and Buzz are completely different things. The wave hype has worn off because it is a development version and most people don't understand that.
It is my impression that Wave targets email and in particular enterprise platforms such as MS exchange/sharepoint. Buzz on the other hand is going for twitter/facebook. Just my $0.02 Cheers, Jonas On Feb 9, 5:26 pm, dougx <[email protected]> wrote: > I very _very_ much doubt that buzz is going to free-as-in-beer the > same way wave promises to be. > > That's a pretty major difference. > > There are a few things there that look a bit familiar though, for > example:http://code.google.com/apis/buzz/documentation/#coming-soon > "Over the next several months Google Buzz will introduce an API for > developers, including full/read write support for posts with the Atom > Publishing Protocol, rich activity notification with Activity Streams, > delegated authorization with OAuth, federated comments and activities > with Salmon, distributed profile and contact information with > WebFinger, and much, much more." > > ...but if you look at the details, it's not really very wave-like; > certainly I don't see anything about conflict resolution for > collaborative editing; it's just a comment sharing tool. > > ~ > Doug. > > On Feb 10, 3:33 am, Daniel França <[email protected]> wrote: > > > I was watching the video introducing Google > > Buzzhttp://googleblog.blogspot.com/2010/02/introducing-google-buzz.html?u... > > > It has some Wave like features, doesn't? It looks like if the recent low > > entusiasm about Wave can migrate efforts to this new tool? Or am I > > completely wrong? -- You received this message because you are subscribed to the Google Groups "Google Wave API" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en.
