<story><title>WebRTC is now a W3C and IETF standard</title><url>https://web.dev/webrtc-standard-announcement/</url></story><parent_chain><item><author>curtis3389</author><text>I agree that WebRTC is super exciting, but if you want to deploy it into production, you need to have a STUN server and a TURN server.&lt;p&gt;Until&amp;#x2F;unless we&amp;#x27;ve all moved to IPv6 without any NAT, we&amp;#x27;ll be stuck needing STUN and TURN to make it work.</text></item><item><author>Sean-Der</author><text>This is so exciting. WebRTC is our best hope to have video interop between platforms. I love that it works outside web browsers, compeitors like WebTransport assume a 100% browser world. Or you have protocols like RTMP&amp;#x2F;SRT... that will never make it into the browser.&lt;p&gt;WebRTC might be our best bet to establish P2P connectivity between all languages&amp;#x2F;platforms. Would love to get rid of the single point of falure in Pub&amp;#x2F;Sub systems. WebRTC also feels like a great path towards easy cloud-agnostic code. You can use lots of different languages, and not dependent on SDKs&amp;#x2F;Servers.&lt;p&gt;* &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;aiortc&amp;#x2F;aiortc&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;aiortc&amp;#x2F;aiortc&lt;/a&gt; (Python)&lt;p&gt;* GStreamer’s webrtcbin (C)&lt;p&gt;* &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;shinyoshiaki&amp;#x2F;werift-webrtc&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;shinyoshiaki&amp;#x2F;werift-webrtc&lt;/a&gt; (Typescript)&lt;p&gt;* &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;pion&amp;#x2F;webrtc&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;pion&amp;#x2F;webrtc&lt;/a&gt; (Golang)&lt;p&gt;* &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;webrtc-rs&amp;#x2F;webrtc&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;webrtc-rs&amp;#x2F;webrtc&lt;/a&gt; (Rust)&lt;p&gt;* &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;awslabs&amp;#x2F;amazon-kinesis-video-streams-webrtc-sdk-c&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;awslabs&amp;#x2F;amazon-kinesis-video-streams-webr...&lt;/a&gt; (C&amp;#x2F;Embedded)&lt;p&gt;* &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;webrtc.googlesource.com&amp;#x2F;src&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;webrtc.googlesource.com&amp;#x2F;src&amp;#x2F;&lt;/a&gt; (C++)&lt;p&gt;* &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;rawrtc&amp;#x2F;rawrtc&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;rawrtc&amp;#x2F;rawrtc&lt;/a&gt; (C++)&lt;p&gt;----&lt;p&gt;Then you have a couple that aren&amp;#x27;t Open Source. But proves it is possible for these platforms also.&lt;p&gt;* Shiguredo (Erlang)&lt;p&gt;* |pipe| (Java)&lt;p&gt;----&lt;p&gt;If you are new to WebRTC I have been working on making it more accessible &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;webrtcforthecurious.com&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;webrtcforthecurious.com&lt;/a&gt;. I am currently pretty tied up with Pion so haven&amp;#x27;t been able to make much progress lately.</text></item></parent_chain><comment><author>vorpalhex</author><text>There are several free STUN services available, and you can fix a lot of connections with just STUN. STUN is just an IP lookup effectively, so it&amp;#x27;s very cheap to deploy.&lt;p&gt;TURN is of course an entirely different beast because it&amp;#x27;s proxying all the data between clients. It&amp;#x27;s also where some more complex video stuff happens potentially. The good news is that there are solid, open source TURN servers available to run on your own hardware. The downside is that running those servers for non-trivial amounts of clients gets pretty resource intensive pretty quick.</text></comment>
<story><title>WebRTC is now a W3C and IETF standard</title><url>https://web.dev/webrtc-standard-announcement/</url></story><parent_chain><item><author>curtis3389</author><text>I agree that WebRTC is super exciting, but if you want to deploy it into production, you need to have a STUN server and a TURN server.&lt;p&gt;Until&amp;#x2F;unless we&amp;#x27;ve all moved to IPv6 without any NAT, we&amp;#x27;ll be stuck needing STUN and TURN to make it work.</text></item><item><author>Sean-Der</author><text>This is so exciting. WebRTC is our best hope to have video interop between platforms. I love that it works outside web browsers, compeitors like WebTransport assume a 100% browser world. Or you have protocols like RTMP&amp;#x2F;SRT... that will never make it into the browser.&lt;p&gt;WebRTC might be our best bet to establish P2P connectivity between all languages&amp;#x2F;platforms. Would love to get rid of the single point of falure in Pub&amp;#x2F;Sub systems. WebRTC also feels like a great path towards easy cloud-agnostic code. You can use lots of different languages, and not dependent on SDKs&amp;#x2F;Servers.&lt;p&gt;* &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;aiortc&amp;#x2F;aiortc&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;aiortc&amp;#x2F;aiortc&lt;/a&gt; (Python)&lt;p&gt;* GStreamer’s webrtcbin (C)&lt;p&gt;* &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;shinyoshiaki&amp;#x2F;werift-webrtc&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;shinyoshiaki&amp;#x2F;werift-webrtc&lt;/a&gt; (Typescript)&lt;p&gt;* &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;pion&amp;#x2F;webrtc&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;pion&amp;#x2F;webrtc&lt;/a&gt; (Golang)&lt;p&gt;* &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;webrtc-rs&amp;#x2F;webrtc&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;webrtc-rs&amp;#x2F;webrtc&lt;/a&gt; (Rust)&lt;p&gt;* &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;awslabs&amp;#x2F;amazon-kinesis-video-streams-webrtc-sdk-c&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;awslabs&amp;#x2F;amazon-kinesis-video-streams-webr...&lt;/a&gt; (C&amp;#x2F;Embedded)&lt;p&gt;* &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;webrtc.googlesource.com&amp;#x2F;src&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;webrtc.googlesource.com&amp;#x2F;src&amp;#x2F;&lt;/a&gt; (C++)&lt;p&gt;* &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;rawrtc&amp;#x2F;rawrtc&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;rawrtc&amp;#x2F;rawrtc&lt;/a&gt; (C++)&lt;p&gt;----&lt;p&gt;Then you have a couple that aren&amp;#x27;t Open Source. But proves it is possible for these platforms also.&lt;p&gt;* Shiguredo (Erlang)&lt;p&gt;* |pipe| (Java)&lt;p&gt;----&lt;p&gt;If you are new to WebRTC I have been working on making it more accessible &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;webrtcforthecurious.com&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;webrtcforthecurious.com&lt;/a&gt;. I am currently pretty tied up with Pion so haven&amp;#x27;t been able to make much progress lately.</text></item></parent_chain><comment><author>qwantim1</author><text>This is why I didn’t get really excited about WebRTC when I looked into it before.&lt;p&gt;And the problem isn’t with WebRTC, it’s with the current infrastructure of the net that prevents some clients from just communicating directly without some element of centralization. And some of it’s our own fault.&lt;p&gt;A cynical way of looking at it might be that WebRTC is being allowed because it helps scale the web while still being dependent on a central weak link of control.&lt;p&gt;But it is what it is.</text></comment>