Google Hangout and future of gTalk video chat about digsby HOT 7 CLOSED

There doesn't seem to be any active development on Digsby since it went open source

from digsby.

Seems like it. Main Digsby.com page has redirection issues. Their twitter hasn't been updated since Sep. And the GitWiki is empty since this repo has been created.

from digsby.

The existing gTalk text chat should continue to work for the foreseeable future. At least, last I read, Google claims it should remain be a functional interface to Hangouts.

As for adding Hangout support for video, or chat in the case of them dropping XMPP chat support for that matter, it should be possible but Google hasn't publicized the API for either so the protocol would have to be reverse engineered in order to be implemented.

@darkmorpher Where are the redirection issues? After seeing this I took a look at the site but didn't have an issue.

from digsby.

@Brok3nHalo I saw what seems like partial API here

And about the redirection, I'm seeing this

from digsby.

@darkmorpher Yeah, I looked through that API the other day. Unfortunately it doesn't cover the chat protocol at all and the audio/video stuff is very limited. It's just meant to access settings like volume and stuff in plugins for the website.

The digsby.com issue is an odd one. Going to the site works fine for me in FireFox on Windows. Only things I could think is a bug in the build of FireFox you're using or some sort of issue with a certain ISP?

from digsby.

@Brok3nHalo

Update 2015: This redirecting issue still exists! Regardless of browser version.
I can load other pages/sub-domains though, (like this page - weird.)

from digsby.

Google did mention something about a full API release sometime in 2014, but the API support for a desktop client is a pipe dream.
They are pushing for more people to use Chrome based browsers, in order to use their services.

Trillian is just waiting to ditch Google Talk/Hangouts' support (partial), because of this.
They already ditched Skype, who, since Microsoft acquisition, have decided to retire their desktop API.
Imo.im already dropped the support for all third-party IM networks and become a standalone platform of their own.

I guess the age of Interoperability clients, is coming to an end...

from digsby.