Linked by Thom Holwerda on Wed 28th Aug 2013 15:43 UTC
Google

Noticed any differences when using Google's Hangouts video chat lately? If you did, then you may be one of the lucky users who has already received an upgrade to 720p HD video. The company quietly started to roll out HD for Hangouts to a subset of its users in the last few weeks and hopes to complete the rollout soon. But the change isn't just a quality upgrade - it's part of a bigger move towards open standards that will eventually bring us video chat in the browser without the need for any plugins.

To enable HD, and prepare for this plugin-free future, Google quietly started to transition Hangouts from the H.264 video codec to VP8, an open and royalty-free video codec the company released back in 2010. Google's Vice President of Engineering Chee Chew told me during a recent interview that the switchover from H.264 to VP8 should be more or less invisible to consumers, with some possibly noticing a little less choppiness. "It will be cleaner, better video," Chew said.

Good move.

On a related note, whatever happened to Apple's promise to make FaceTime an open standard?

Thread beginning with comment 570810
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[6]: Comment by shmerl
by Moochman on Wed 28th Aug 2013 18:31 UTC in reply to "RE[5]: Comment by shmerl"
Moochman
Member since:
2005-07-06

Yes, but how do you *find* the other users to chat with? Do you really expect everyone to send each other their current IP addresses and fire up their own hacked-together JavaScript pages at pre-appointed times to chat with each other? The API does not include presence notification, "ringing up" other people, chatting, etc. No one except extreme nerds are going to actually use the API in its "pure" form. This is why something like tying WebRTC together with XMPP would make a lot of sense...

Reply Parent Score: 4

RE[7]: Comment by shmerl
by lucas_maximus on Wed 28th Aug 2013 18:37 in reply to "RE[6]: Comment by shmerl"
lucas_maximus Member since:
2009-08-18

All it requires is a webpage and the appropriate server side technology

http://www.html5rocks.com/en/tutorials/webrtc/basics/

Reply Parent Score: 2

RE[8]: Comment by shmerl
by shmerl on Wed 28th Aug 2013 18:38 in reply to "RE[7]: Comment by shmerl"
shmerl Member since:
2010-06-08

You don't need webpages for communication. You are missing some important points here. You need protocols for them.

Communicating through the browser would require a web page since that's how the browser works of course. WebRTC is not limited to browsers though.

Edited 2013-08-28 18:39 UTC

Reply Parent Score: 2

RE[7]: Comment by shmerl
by Nelson on Wed 28th Aug 2013 18:44 in reply to "RE[6]: Comment by shmerl"
Nelson Member since:
2005-11-29

If you support SSO via Twitter/FB you can use the tokens to enumerate the users friends. Probably will take some persisted state to cross reference between friends on those networks and friends on the service to see which are participants.

Reply Parent Score: 4