<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>moron4hire</author><text>&amp;gt; Step 9 · failure. Just log the error to console and call it a day.&lt;p&gt;There is not a single WebRTC guide that says anything else on the matter of error handling. There is zero guidance on how to handle fail over, what parts are recoverable, how to sequence multiple users joining a session at the same time, what to do if the signal process hangs--basically anything other the default one-to-one successful scenario. All we ever get is the same rehashing of the signalling process, for the last 5 years now. It&amp;#x27;s ridiculously bad.&lt;p&gt;I think once you understand the handshake, it make a lot of sense. But the success case is just one. And we don&amp;#x27;t need 20 guides on it with 0 on any error cases.&lt;p&gt;I&amp;#x27;ve probably read 90% of the available literature, including several full length books. They pad their length with code listings, like people copy code out of books anymore. You are on your own if you are trying to develop a good app using WebRTC.</text><parent_chain></parent_chain></comment><story><title>Untangling the WebRTC Flow</title><url>https://www.pkcsecurity.com/untangling-webrtc-flow.html</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>bhouston</author><text>One thing I could use is a Node.JS library for streaming MP4s and other vidoe streams to WebRTC directly.  Basically use WebRTC as a low latency streaming video means.</text><parent_chain></parent_chain></comment><story><title>Untangling the WebRTC Flow</title><url>https://www.pkcsecurity.com/untangling-webrtc-flow.html</url></story>