On: A simple C implementation to stream H.264 to brows...

[chin123]

I've seen a few WebRTC server implementations pop up recently but the only clients I have seen are web browsers. Does anyone know of any WebRTC client implementations apart from the browser? Or am I misunderstanding the WebRTC architecture completely?

[Sean-Der → chin123]

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

[chapelierfou → Sean-Der]

Just a nitpick: RAWRTC is actually written in C (also I think it focuses on data channels only).

[EGreg → Sean-Der]

What about Node.js clients??

To record meetings without sacrificing end to end encryption

[nsteel → chin123]

Gstreamer. Example at https://github.com/centricular/gstwebrtc-demos/tree/master/s...

[ajb → chin123]

At a low level, webrtc interoperates with VoIP. But because webrtc doesn't mandate a signalling protocol and VoIP uses SIP, generally you need a browser to run whatever proprietary signalling the site decided to implement in JS.

[superdisk → ajb]

Matrix can also function as a signaling layer for WebRTC.

[SahAssar → superdisk]

Anything can function as the signaling layer since all you need is to exchange pieces of text. I think the point was that most sites choose to implement it using JS and browser API's like ajax, websocket or SSE.

[phipleg → chin123]

The Python library aiortc, https://github.com/aiortc/aiortc, enables client and server side communication via WebRTC.

[pjmlp → chin123]

Windows, https://github.com/microsoft/winrtc

[rapsey → chin123]

The official one, pion (go) and webrtc-rs (rust) can all be used on both sides.

[nsteel → rapsey]

Is webrtc-rs usable? There are ticks missing for Media or DataChannel and PeerConnection. Aren't these required to do anything useful?

[chapelierfou → nsteel]

I think webrtc-rs is still in early development. libdatachannel has Rust bindings though: https://github.com/lerouxrgd/datachannel-rs

[chapelierfou → rapsey]

libdatachannel (C/C++) can also be used on both sides: https://github.com/paullouisageneau/libdatachannel

[tapirl → rapsey]

pion link: https://github.com/pion/webrtc

[the_only_law → chin123]

I believe that clients are available for most native MobileMe platforms as well.

https://webrtc.github.io/webrtc-org/native-code/android/

https://webrtc.github.io/webrtc-org/native-code/ios/

[albertoCaroM → chin123]

If you are interested in desktop implementations, you can access the telegram desktop source code, which also uses WebRTC: https://github.com/telegramdesktop/tdesktop/blob/a506e9b9eb7...

[bodegajed → chin123]

Because webrtc came from the chromium source code so you got it installed already on your browser. Then Google took it out there and made it stand alone library so you can use it on apps. I see webrtc projects occasionally here on Show HN threads

[SahAssar → chin123]

A lot of video call applications use WebRTC, I'm pretty sure slack uses it (although not in P2P mode, they use a SFU).