Our great sponsors
ringrtc | webrtc | |
---|---|---|
6 | 40 | |
523 | 3,736 | |
1.3% | 3.0% | |
9.2 | 8.7 | |
9 days ago | about 11 hours ago | |
Rust | Rust | |
GNU Affero General Public License v3.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ringrtc
-
LiveKit – open-source, high performance WebRTC infrastructure
If you did not know, there is also https://github.com/signalapp/ringrtc by the Signal App team, which is written in Rust
-
Signal now supports group calls up to 40 people, using Rust
Huh, Signal's WebRTC implementation seems to be using Rust implementations of crypto primitives such as AES: example usage, Cargo.toml
-
WhatsApp and most alternatives share the same problem
Signal is still an improvement over other non-federated messengers in that it's open-source, so you actually can try to improve the situation, although it's notoriously difficult. As an example of more platform support: https://github.com/signalapp/ringrtc/pull/12
signal-cli is an example of a 3rd party client which is tolerated for now: https://github.com/AsamK/signal-cli
The main problem right now is that they don't have enough developers to take care of everything, but it's not specific to centralized services (no developer == no code). If you care about it, you can develop your own client using their library (à la signal-cli).
Regarding your last paragraph: I could probably list 20 features I'd like to see in Signal. That doesn't mean I want somebody implementing them with no guarantee about how securely they are implemented. One of the main goals of Signal is to provide guarantees against dragnet surveillance, and that constraint takes precedence.
-
is anyone regretting moving to signal and moving back to whatsapp?
Outside of the Android app, they had a bunch of "new developers" join, and they ported the call signalling framework to Rust: https://github.com/signalapp/ringrtc . This Rust library is now used by the other apps.
webrtc
-
Pure C WebRTC
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 (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.
- WebRTC for the Curious
-
Building WebRTC server implementation for Erlang
This is not true, there are actually multiple WebRTC implementations in different languages besides the reference library: aiortc (python), libdatachannel (C++), sipsorcery (C#),webrtc-rs (rust), werift (Typescript), and Amazon Kinesis (C)
-
Real-Time Video Processing with WebCodecs and Streams
I have opened an issue on GitHub [1], we can continue there.
-
A Rust client library for interacting with Microsoft Airsim https://github.com/Sollimann/airsim-client
webrtc
-
A Rust library for cross-platform video apps using WebRTC and LiveKit
webrtc.rs is a port of Pion (which we also use). It's a better fit for server-side use
-
WebRTC signaling server in Rust
I want to use peer-to-peer communication and data transfer for my next side project (client-server web app). I've been doing some research and WebRTC seems to be the only option for this on the client. There are a ton of libraries and product offering for facilitating STUN/TURN servers as a service, but I'm quite interested in learning more about these protocols. That being said, I'm not the best rust programmer (part of the reason of using Rust as the server is so that I can learn more), and the signalling protocols seem rather complicated. I've looked at https://github.com/webrtc-rs/webrtc and it seems promising.
-
str0m a sans I/O WebRTC library
Regarding webrtc-rs. I'm a contributor to that project. The future of str0m could very well be to roll it in under that umbrella. However in these early days, I think it's better to keep str0m separate, until such time that it covers most of webrtc-rs functionality. Discussion here: https://github.com/webrtc-rs/webrtc/issues/230
-
Adding WebRTC support to OBS
This project was really fun for me is that I got to use https://webrtc.rs webrtc.rs Rust implementation of WebRTC that is based on Pion. The performance is fantastic and it is so easy to fetch + build. I had a great experience with it. It is really impressive how far the project has come!
-
Adding WebRTC support to OBS using Rust
I'm confused, you're saying as far as you can tell webrtc-rs does everything pion can do, but also saying "when the project is ready"? Can you explain what you mean? Also it seems webrtc.rs website says it's not production ready yet? How true is that?
What are some alternatives?
aiortc - WebRTC and ORTC implementation for Python using asyncio
Pion WebRTC - Pure Go implementation of the WebRTC API
tauri - Build smaller, faster, and more secure desktop applications with a web frontend.
libdatachannel - C/C++ WebRTC network library featuring Data Channels, Media Transport, and WebSockets
opencv-python - Automated CI toolchain to produce precompiled opencv-python, opencv-python-headless, opencv-contrib-python and opencv-contrib-python-headless packages.
Homer - HOMER - 100% Open-Source SIP, VoIP, RTC Packet Capture & Monitoring
amazon-kinesis-video-streams-webr
Signal-Server - Server supporting the Signal Private Messenger applications on Android, Desktop, and iOS
livekit - End-to-end stack for WebRTC. SFU media server and SDKs.
LibreSignal - LibreSignal • The truly private and Google-Free messenger for Android.
SIPSorcery - A WebRTC, SIP and VoIP library for C# and .NET. Designed for real-time communications apps.
TextSecure - A private messenger for Android.