Twilio just launched their Voice Insights service. One of several announcements. How does this new analytics related offering fit into the WebRTC PaaS space?
When we look at network connections of WebRTC, most of the time you’ll see people focusing on signaling but missing the WebRTC media paths. Here’s what to expect.
Using a media server with a public IP address isn’t enough to solve your WebRTC NAT traversal headaches – you need a TURN server for that.
What’s the decentralized web anyway? That’s what a group of pundits were asked, and here are my own thoughts on the subject.
Microsoft just acquired Beam for its low latency interactive live streaming platform that happens to use WebRTC. Here’s what it means and the various techniques in which WebRTC fits to this niche.
When looking at VP8 vs VP9, is the main incentive to switch lies in quality or bitrate requirements?
Need a messaging framework? Should you buy one or build your own? There’s no easy answer, but I’d lean towards buying a platform any day of the week.
When looking at a standard, make sure to check who is behind it and who is missing in action. It usually tells you the power play that is taking place. In the case of WebRTC, it all boils down to the change in hegemony over VoIP from vendors to browsers.
When it comes to WebRTC multiparty video, the most common architecture out there is SFU. The reason for it is cost and complexity. What makes it a better choice than mesh or an MCU?
WebRTC security should be the least of your worries in the face of problems we have elsewhere. You should get your priorities straight.