Two weeks ago Philipp Hancke, lead WebRTC developer of Talky and part of the &yet‘s WebRTC consulting team, started a series of posts about detailed examinations he is doing on several major VoIP deployments to see if and how they may be using WebRTC. Please see that post on WhatsApp for some background on the series […]
Search Results for: hancke
What’s up with WhatsApp and WebRTC?
One of our first posts was a Wireshark analysis of Amazon’s Mayday service to see if it was actually using WebRTC. In the very early days of WebRTC, verifying a major deployment like this was an important milestone for the WebRTC community. More recently, Philipp Hancke – aka Fippo – did several great posts analyzing Google Hangouts and Mozilla’s […]
The Minimum Viable SDP
One evening last week, I was nerd-sniped by a question Max Ogden asked: That is quite an interesting question. I somewhat dislike using Session Description Protocol (SDP) in the signaling protocol anyway and prefer nice JSON objects for the API and ugly XML blobs on the wire to the ugly SDP blobs used by […]
How does Hangouts use WebRTC? webrtc-internals analysis
Update: Philipp continues to reverse engineer Hangouts using chrome://webrtc-internals. Please see the bottom section for new analysis he just put together in the past couple of days based on Chrome 38. As initiators and major drivers of WebRTC, Google was often given a hard time for not supporting WebRTC in its core collaboration product. This […]
About
We are WebRTC technologists and enthusiasts. Our goals in this blog are to: Provide more detailed technical explanations on how WebRTC works Identify, review, and organize the rapidly expanding WebRTC tools market Document our experiments with various WebRTC applications Serve the needs of WebRTC developers Meet the team: Chad Hart Philipp Hancke