openwebtorrent-tracker
libdatachannel
Our great sponsors
openwebtorrent-tracker | libdatachannel | |
---|---|---|
3 | 27 | |
67 | 1,535 | |
- | - | |
1.8 | 9.3 | |
almost 3 years ago | 6 days ago | |
C++ | C++ | |
- | Mozilla Public 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.
openwebtorrent-tracker
-
aquatic_ws (WebTorrent tracker) rewritten with glommio, achieves up to 1.6 million responses a second in load tests
openwebtorrent-tracker (C++, single-threaded) reached 9 thousand responses a second
-
What trackers should I use for personal media?
I think you can find some tracker here: https://openwebtorrent.com/
-
aquatic BitTorrent tracker: WebTorrent support (1.8M responses/second); new UDP benchmarks (650k rps)
I did some benchmarks with my load testing tool and got very encouraging results: 1.8M tracker responses per second when using 14 threads, compared to a maximum of 117k responses per second for closest competitor wt-tracker. I suspect that the openwebtorrent tracker would be a lot closer in performance to aquatic, but since it only runs over TLS, I couldn’t test it, as the load tester doesn’t support it. More info on the benchmark (PDF).
libdatachannel
- VoRS: Vo(IP) Simple Alternative to Mumble
-
Simplicity of IRC
You can use https://github.com/paullouisageneau/libdatachannel for your C/C++ integration needs. It's 10k lines. So the answer is 0. Its required dependencies (I assume this as they are git submodules in deps) are more than 100k lines, though, srtp support making the bulk of it. On my machine it took 11 seconds to compile it.
Irssi is 64k lines (plus its dependencies), so I guess that makes WebRTC complicated.
Can't argue that DCC isn't simple, but perhaps the protocol deviced decades ago is a bit too simple.
-
OBS merges AV1 support for WebRTC
Most of the work happened in the libdatachannel! You can check out my PR here[0]
[0] https://github.com/paullouisageneau/libdatachannel/commit/a6...
-
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)
-
I spent two years building a desktop environment that runs in the browser, it's finally in beta!
Use any means necessary to transfer your data across devices. Could be IPFS, could be FTP, could be EventSource, WebSocket, WebTransport, Fetch, whatever. See https://github.com/guest271314/secure-file-transfer; offscreen-webrtc, https://github.com/paullouisageneau/libdatachannel.
-
Client side Rest server?
I've successfully used libdatachannel to Web pages to connect native applications and stream data to the browser.
-
Security Framework
Alternatively you can use your server as a signaling server for WebRTC (Insertable Streams ("Breakout Box"), or data channels https://github.com/paullouisageneau/libdatachannel), then users (peers) can exchange data themselves and you don't need to store anything, see True End-to-End Encryption with WebRTC Insertable Streams, A complete example for a WebRTC datachannel with manual signaling.
-
Datachannel video streaming?
there is also a c++ library that can be used to open a data channel connection, I think a number of SFU “servers?” use this library (I wish I had) https://libdatachannel.org/
What are some alternatives?
aquatic - High-performance open BitTorrent tracker (UDP, HTTP, WebTorrent)
libjuice - JUICE is a UDP Interactive Connectivity Establishment library
wt-tracker - High-performance WebTorrent tracker
Pion WebRTC - Pure Go implementation of the WebRTC API
webtorrent - ⚡️ Streaming torrent client for the web
aiortc - WebRTC and ORTC implementation for Python using asyncio
BambooTracker - YM2608 music tracker 🎍🎋
sora-unity-sdk - WebRTC SFU Sora Unity SDK
libtorrent - an efficient feature complete C++ bittorrent implementation
janus-gateway - Janus WebRTC Server
µWebSockets - Simple, secure & standards compliant web server for the most demanding of applications