Is this Google's response to MS purchasing skype? Seems like the classic strategy of commoditizing your competitor's business (and they get a 2-for-1 deal since Apple is also wielding FaceTime).
Hm, I don't think so. This post is dated May 3rd, which predates the Skype deal's announcement by 7 days. Also, the WhatWG group for RTC's mailing list was first posted to April 12, 2011. So that potentially indicates this was in the works beforehand. Since Google purportedly put in a bid for Skype they no-doubt knew Skype was on the market, though.
I would guess this is more likely a response to FaceTime. Apple's core business is around getting people to buy iPhones, and FaceTime is exclusive to the iPhone and other Apple products.
Just found the slide listing the "standards" FaceTime uses [1]: H.264, AAC, SIP, STUN, TURN, ICE, RTP and SRTP. From the list, the only thing left for someone else to integrate with FT would be friend management and presence (online status). Something like Jabber could probably handle this bit pretty well.
I remember the facetime announcement including that they were going to publish it as an open standard, and I'm not the only one:
"The company said it plans to make FaceTime an open industry standard, potentially allowing
communication with other devices."
-- http://www.appleinsider.com/articles/10/06/07/apple_announces_open_standard_facetime_video_chat_for_iphone_4.html
and it's not just AppleInsider - that's just the first non-wikipedia hit for the search "facetime open standard". That said, they never (to my knowledge) delivered, which is a shame. At least now there's something, though it's a pity that FT users will likely be left out.
Isn't that about survival of the fittest? Why use a browser that don't support shit when there is a few that does. Might work for now, but not in the future.
Yep, sorry about that. You can still use the old code under the old license, but you can also use it under the new (and more permissive and favorable) license.
From the FAQ:
Builds on the strength of the web browser: WebRTC abstracts signaling by offering a signaling state machine that maps directly to PeerConnection. Web developers can therefore choose the protocol of choice for their usage scenario (for example, but not limited to: SIP, XMPP/Jingle, etc...).
One way to decimate adversaries is to open-source your entire competitive advantage. Unfortunately that only works when you’re the market leader.
So nobody cares about open-sourcing WebRTC. Something that would be actually noticeable in this field right now would be Microsoft that open-sources Skype and gives everything away under the BSD license.
Except the people that would want to use it?
Think of Chatroulette.
Something that would be actually noticeable in this
field right now would be Microsoft that open-sources
Skype
Noticeable yes, but useful, not really.
What would be useful is for Skype to become a standard that allows interoperability with other services and protocols, such that you could build a client, like a website, that would allow users with a GTalk account to video-call Skype users. Now that would be something.
Actually the GTalk update that was released with 2.3.4 uses Neon-specific code rather than the actual video API that Google wrote themselves. It makes no sense and it's the reason that GTalk doesn't have video chat on other Gingerbread phones.
