Google Wave integration

I couldn't find an existing topic about his (a little surprised).  If I missed it, please delete this topic.

Google has announced it's new product/platform/protocol "Wave".  It looks like it has the potential to become a standard for internet communication and I would love to see digsby include Wave integration soon after launch.  Google has made API and protocol details available very early in their development cycle to encourage developers to create apps and integration while they finish developing the product.  It would be great if digsby could take advantage of that lead-time and be ready to integrate immediately after official launch of Wave.  I am creating a digsbies feature request to link to this topic.  Please respond with comments here and/or vote on the feature at digsbies.org.

http://code.google.com/apis/wave/ wrote:

The Google Wave API allows developers to use and enhance Google Wave through two primary types of development:
- Extensions: Build robot extensions to automate common tasks or build gadget extensions to provide a new way for users to interact
- Embed: Make your site more collaborative by dropping in a Wave

neither of those is a desktop application, so i don't foresee this happening. seems like it's still a month or two away though (at least), maybe they'll announce something new.

I can see some cool stuff happening with this.  As Mike said, the APIs don't really sound like they support anything we'd do (yet)and it's mostly a fullscreen webapp so not sure how much would be practical for us to build into Digsby. That being said, notifications and wave management could be pretty sweet.  Anyone else have any other ideas?

Approved on the wishlist, http://digsbies.org/site/content/wishli … ntegration

Go vote

Google Wave is supposedly a new email system. Looks pretty cool, though I think they went overboard by adding add-ons. It will get released around October.
If it is an email client, it should be easy to install. It will just be like adding POP3, but with a different API.

It seems this guy
http://thatsmith.com/2009/10/google-wav … or-firefox
managed to check for new waves.

Umberto wrote:

It seems this guy
http://thatsmith.com/2009/10/google-wav … or-firefox
managed to check for new waves.

he's logging into the website under the hood.  I'd much prefer an xmpp interface, you know, the wave protocol.

There are quite a few desktop clients for wave popping up. Integrating into Digsby would be no problem at all.

The protocol is open for anything from desktop, wave, mobile apps etc.

"Waver" is the first desktop client thats nearing the same usefullness as googles web client.

When adding wave functionality remember that google will not be the only one supplying a wave server. It's open for everyone to set up, run their own and join federation with other servers (such as googles). Authorization and communication should be open for other server URLs. However i think its fair to think the default one will be googles own

There is a lot more info here: http://www.waveprotocol.org/
Integrating wave into digsby has nothing to do with the wave API.
On that site theres even a very basic client/server applictaion to help development.

Bump + 1 vote for Wave features in Digsby

Just remember that Wave is a very beta product with few features at present which means dotSyntax would have to take time out from whatever they are working on everytime Google updates Wave.

I'm not sure if the protocol problem is still actual, but it's specs were 100% open the same day wave was presented to the audience for the 1st time.

http://www.waveprotocol.org/draft-protocol-specs

Does it make GoogleWave support for Digsby any closer to us?

+1 I'd like to migrate all of my chatting over to Waves. Once you get using it, you see it is way better than traditional IM. It's far easier to find your chats, it sits on the server if the person is not online (no more of that ridiculous "this message was not delivered", you can keep all of your blogs, tweets, documents, and more in one place). It's brilliant. If Digsby supported it then I could better see who is on and offline and keep most of my chats there.

@heathweaver: Google Talk also has all those features but with a more convenient chat interface. ^_^

@Crusteek: Google hasn't made the client-server protocol documentation available yet, only the server-server protocol and the Conversation Model. there is a 3rd party project to document the client-server protocol, but the protocol is still in development and may change.

It's also far to early to even tell if it's worth adding to Digsby. So far it seems to be useful for very special case discussions and team projects but not very useful for general communication. There is very little indication either way if it will get a large active user-base or not. Also it doesn't function as a IM network at all so it would require a custom UI of it's own, which would take a significant amount of development time. The other option would be to just limit Wave to notifications, but there are already plenty of solutions for that.

To sum up, we are currently taking the "wait and see" approach to this one.

A wave notifier would be sufficient - client chat isn't something that would seem feasible given the format of Wave - but a simple notifier in the taskbar would be ideal - basically something integrated into Digsby that provides functionality similar to this: http://wave-notify.sourceforge.net/index.php. I'd be infinitely happy with a solution of that nature.

what is the difference between buzz and wave?

Buzz is pretty much just posts that people can like and comment on. Buzz can also display your latest posts from various sources such as Twitter and they two can be liked and commented on.

Wave is hard to explain. Think of a big MSN conference. You can invite people, add pictures and so on. The difference in Wave is that it's always there so you can come back to it as any point and you can edit others posts.

wave is a mash up of a IM/conference client and Email all into one. With a very rich HTML 5 interface. Its still got some work to go, but its definitely the future in communication tools.