werift-webrtc

I am so happy that WebRTC has so many implementations. Every developer thinks differently, it's good to have a implementation that matches your mindset. * https://github.com/shinyoshiaki/werift-webrtc (Typescript) * https://github.com/pion/webrtc (Golang) * https://github.com/webrtc-rs/webrtc (Rust) * https://github.com/algesten/str0m (Rust) * hhttps://github.com/sepfy/libpeer (C/Embedded) * https://webrtc.googlesource.com/src/ (C++) * https://github.com/sipsorcery-org/sipsorcery (C#) * https://github.com/paullouisageneau/libdatachannel (C++) * https://github.com/elixir-webrtc (Elixir) * https://github.com/aiortc/aiortc (Python) * GStreamer’s webrtcbin (C) See https://github.com/sipsorcery/webrtc-echoes for examples of some running against each other.

What makes something a 'blessed way'? Are you looking for community support, large corporate users etc..? Not being snarky, curious about how people see the space. Lots of implementations exist and I have used most of them for different projects, not all these projects went to production though. * https://github.com/elixir-webrtc (Elixir) * https://github.com/pion/webrtc (Golang) * https://github.com/webrtc-rs/webrtc (Rust) * https://github.com/algesten/str0m (Rust) * https://github.com/sepfy/libpeer (C/Embedded) * https://github.com/awslabs/amazon-kinesis-video-streams-webr... (C/Embedded) * https://github.com/paullouisageneau/libdatachannel (C++) * https://webrtc.googlesource.com/src/ (C++) * https://github.com/shinyoshiaki/werift-webrtc (Typescript) * https://github.com/sipsorcery-org/sipsorcery (C#) * https://github.com/aiortc/aiortc

I am really excited about https://github.com/sepfy/libpeer. It has examples ready for ESP32 etc.... When working on KVS I wasn't familiar with the embedded space at all. I saw 'heavyweight' embedded where you were running on Linux. Then you had RTOS/No OS at all. I wasn't prepared for these devices at all. If we can make WebRTC work in the embedded space I think it will really accelerate what developers are able to build! Remotely driven cars, security cameras, robots in hospitals that bring iPads to infectious patients etc... Creative people are building amazing things. The WebRTC/video space needs to work harder and support them :) ----- I love how diverse the WebRTC space is now. Outside of this implementation you have plenty of other options! * https://github.com/shinyoshiaki/werift-webrtc (Typescript) * https://github.com/pion/webrtc

What libraries have you used? There are a lot these days, maybe you haven't tried one yet that matches the way you think/code :) * https://github.com/aiortc/aiortc (Python) * GStreamer’s webrtcbin (C) * https://github.com/shinyoshiaki/werift-webrtc (Typescript) * https://github.com/pion/webrtc (Golang) * https://github.com/webrtc-rs/webrtc (Rust) * https://github.com/algesten/str0m (Rust) * https://github.com/awslabs/amazon-kinesis-video-streams-webr... (C/Embedded) * hhttps://github.com/sepfy/libpeer (C/Embedded) * https://webrtc.googlesource.com/src/ (C++) * https://github.com/sipsorcery-org/sipsorcery (C#) * https://github.com/paullouisageneau/libdatachannel (C++) * https://github.com/elixir-webrtc (Elixir) See https://github.com/sipsorcery/webrtc-echoes for examples of some running against each other.

You have more choices then that for node.js * https://github.com/shinyoshiaki/werift-webrtc * https://github.com/murat-dogan/node-datachannel If libwebrtc fits your needs you totally should use it! Alternatives have existed for years though

There's a native implementation that requires no binaries here: https://github.com/shinyoshiaki/werift-webrtc Maybe I'm missing something but how Node-WebRTC preferable?

Lots of other WebRTC implementation exist (in many languages). Happy to help if you have any questions * https://github.com/aiortc/aiortc (Python) * GStreamer’s webrtcbin (C) * https://github.com/shinyoshiaki/werift-webrtc (Typescript) * https://github.com/pion/webrtc (Golang) * https://github.com/webrtc-rs/webrtc (Rust) * https://github.com/awslabs/amazon-kinesis-video-streams-webr... (C/Embedded) * https://webrtc.googlesource.com/src/ (C++) * https://github.com/rawrtc/rawrtc (C++) * https://github.com/sipsorcery-org/sipsorcery (C#) * https://github.com/paullouisageneau/libdatachannel (C++) See https://github.com/sipsorcery/webrtc-echoes for examples of all of them running against each other.

I am a big fan of https://github.com/shinyoshiaki/werift-webrtc it is pure Typescript. Will be easier to debug/deploy. Lots of other great WebRTC implementations also exist. Check out https://github.com/sipsorcery/webrtc-echoes for all the other implementations if you are open to non node.js

There are lots of implementations now! Here are the ones I know about. * https://github.com/aiortc/aiortc (Python) * GStreamer’s webrtcbin (C) * https://github.com/shinyoshiaki/werift-webrtc (Typescript) * https://github.com/pion/webrtc (Golang) * https://github.com/webrtc-rs/webrtc (Rust) * https://github.com/awslabs/amazon-kinesis-video-streams-webr... (C/Embedded) * https://webrtc.googlesource.com/src/ (C++) * https://github.com/rawrtc/rawrtc (C++) * https://github.com/sipsorcery-org/sipsorcery (C#) * https://github.com/paullouisageneau/libdatachannel (C++) Also check out https://github.com/sipsorcery/webrtc-echoes for how they work together

Hey HN, I am so excited to share webrtc-echoes. This repository contains a test suite that asserts that many different WebRTC implementations can communicate with each other. It also asserts that these WebRTC implementations work with WebRTC servers. My personal goal is that someday WebRTC is as easy as HTTP. You don't worry about what implementation/tools you use, you just start the project in your favorite language. WebRTC-echoes is important for a few reasons * Ensure that things connect, and prevents regressions. It makes all the implementations more robust. * Great for learning. Developers see all the options available and can try different software. * Builds community. With all of us working together it will help good ideas spread faster. ----------- This is what is implemented today. * aiortc: WebRTC and ORTC implementation for P

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/SRT... that will never make it into the browser. WebRTC might be our best bet to establish P2P connectivity between all languages/platforms. Would love to get rid of the single point of falure in Pub/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/Servers. * https://github.com/aiortc/aiortc (Python) * GStreamer’s webrtcbin (C) * https://github.com/shinyoshiaki/werift-webrtc (Typescript) * https://github.com/pion/webrtc (Golang) * https://github.com/webrtc-rs/webrtc (Rust) * https://github.com/awslabs/amazon-kinesis-video-st

The project I work on is https://github.com/pion/webrtc. https://github.com/pion/awesome-pion is a list of interesting projects that use it, my favorite thing to share :) For other WebRTC implementations check out. * https://github.com/aiortc/aiortc * https://github.com/shinyoshiaki/werift-webrtc * https://github.com/rawrtc/rawrtc * https://gstreamer.freedesktop.org/documentation/webrtc/index... There is also https://github.com/node-webrtc/node-webrtc this takes Google's WebRTC implementation (used in Chromium) and throws a node.js API on top of it!

One thing to note is that this is an issue in Google’s implementation of WebRTC. I wish the marketing gimmicks would stop and they would acknowledge outside efforts. Stuff like this hurts the perception of WebRTC which is a shame. We are seeing more and more memory safe implementations of WebRTC. So I really think there is light at the end of the tunnel! * https://github.com/pion/webrtc * https://github.com/shinyoshiaki/werift-webrtc Chromium itself sees constant CVEs so I don’t think this is a WebRTC specific issue. Documents like https://www.chromium.org/Home/chromium-security/memory-safet... give me hope.