How does this play with WebRTC? Are they complementary technologies?
Google switches GTalk's VOIP protocol to Jingle
41–50 of 50 posts
Re: Google switches GTalk's VOIP protocol to Jingle
#42Earlier quoted context omitted.
The official client never got video chat support either. It's received very little love over the past couple of years. Personally I think the only native client they are interested in anymore is Gmail in Chrome...
Has it received _any_ love over the years? My impression is that the program came as a freebie with some acquisition and they've never touched it since. Opening up googletalk-setup.exe in Archive Manager (aka file-roller), it seems like the lastmodify date on the most recent files is January 1, 2007.
The Google Talk Windows client application was developed by Google engineers at Google. It has not been updated in years as you have noted.
Re: Google switches GTalk's VOIP protocol to Jingle
#43Earlier quoted context omitted.
I'm curious as to why the windows Google Talk product has stalled - I always thought Google planned to improve it to make it a worthy competitor to Skype, but it seems to have stalled. And now this news indicates that it appears to be AbandonWare. Which is a real pity.
I guess for Google the browser is the platform. No need to make dedicated Windows/Linux/OSX programs.
I agree. They likely still have intentions of making it a Skype competitor, but it will be in the browser rather than on the desktop.
Re: Google switches GTalk's VOIP protocol to Jingle
#44Earlier quoted context omitted.
I guess for Google the browser is the platform. No need to make dedicated Windows/Linux/OSX programs.
I agree. They likely still have intentions of making it a Skype competitor, but it will be in the browser rather than on the desktop.
The latest inclusion of voice and video protocols in Chrome agrees with you.
Re: Google switches GTalk's VOIP protocol to Jingle
#45Google Translate integrated with Jingle could/will be a joy to use. I would love to talk to a college student in Greece about the local economic sentiment over VoIP.
Check out http://babelverse.com/
A startup coming out of Greece btw :)
Re: Google switches GTalk's VOIP protocol to Jingle
#46Earlier quoted context omitted.
What about people who don't like or use the Gmail web UI (I use it over IMAP) but would still like to use Google Talk to stay in touch with friends? Is my only option to use third-party clients? I like Google Talk but dislike Gmail, and tying the two together doesn't really work out in my favour.
"What about people who don't like or use the Gmail web UI" Well there is always http://talkgadget.google.com/talkgadget/client Opening a webbrowser window with that and you are set. No Gmail UI, and you get video chat.
I wonder why the gadget doesn't have an option for calling normal phone lines like the Gmail UI does.
Re: Google switches GTalk's VOIP protocol to Jingle
#47Earlier quoted context omitted.
If this had happened for email, we would have had to deal with a myriad of different clients, servers and 'interworking' gateways. That was the networking prior to the wide adoption of IP and SMTP. There were DECnet mail clients, and clients for various other networking protocols, and users needed to know explicit bang-path routes and gateways. Seeing this churn and this fragmentation is unpleasant, but it also means…
I hadn't looked at it from this perspective, thank you for the enlightenment. I'm just too impatient. What irks me is that the IETF keeps banging away at protocols to solve issues like the transition from PSTN to IP (e.g. ENUM), or IM interoperability, but then nobody really implements them, or as in the case of ENUM, the incumbent telcos, at least in the USA, sit on it forever. Or some startup cooks up their own sol…
I'm far too impatient as well, I suppose. It seems to me (from the armchair where I quarterback) that IM interoperability isn't happening not because companies prefer the advantages of their chosen protocol, but because they simply want to "be the platform." I can't imagine a better advantage than actually being able to talk with any of my friends on any other client.
If email hasn't proven a standard can be beneficial to everyone, I don't know what would.
Re: Google switches GTalk's VOIP protocol to Jingle
#48How does this play with WebRTC? Are they complementary technologies?
Yes, complimentary. You could use WebRTC to implement a Jingle client.
Re: Google switches GTalk's VOIP protocol to Jingle
#49Earlier quoted context omitted.
We care about gmail on all browsers :).
If you guys abandon the Windows client, why not make it open source and let the community maintain it? A slim native Windows XMPP client program is vey rare. Some of us choose native program over Web app for a reason and I believe there are many like me would stick with it.
Absolutely. Of all different IM programs, GTalk is the only one which has a simple, useful and non-bloated GUI. And of all GTalk incarnations, Windows client is somehow the only one which is usable. IM client which runs in browser simply sucks as a concept.
Re: Google switches GTalk's VOIP protocol to Jingle
#50Anyone know if this update applies to Google Voice? And whether it will now be possible to initiate a standard RTP stream via XMPP? That would make SIP interoperability with Google Voice practical. At the moment it's held back by the fact that Google Voice requires some custom ICE packets to be exchanged on the RTP sockets before it will commence sending RTP. Which means there are no SIP clients that can talk RTP with Google Voice when the call is initiated over XMPP :(.