lherman

4 ms·

1.
by lherman 3mo ago
PulseBeam is an open-source, lightweight WebRTC SFU server. Somewhere between LiveKit and mediasoup, written in Rust.
2.
Moving a Rust WebRTC SFU to thread-per-core: 70ms → 10ms P99.99 latency(pulsebeam.dev)
12 points by lherman 3mo ago|1 comments
3.
by lherman 1y ago
PulseBeam is an early-stage, open-source WebRTC SFU in Rust, built for simplicity. See https://pulsebeam.dev and https://github.com/pulseBeamDev/pulsebeam . Key features: Signaling: WHIP/WHEP supe
4.
Show HN: Lightweight, Opinionated WebRTC SFU in Rust(pulsebeam.dev)
4 points by lherman 1y ago|1 comments
5.
by lherman 2y ago
That would be ideal. But, I don't believe there is a strong incentive for many existing network to be upgraded without using NAT. In regards to TURN, it is used only as a fallback.
6.
by lherman 2y ago
Yes, self-host signaling server here: https://github.com/PulseBeamDev/pulsebeam-server-foss LMK if you have any issues, contributions welcome
7.
by lherman 2y ago
We don't have an example of CRDT with PulseBeam yet. But, CRDT itself is just a data structure, so you can use PulseBeam to communicate the sync ops (full or delta) with a data channel. Then, you can either use y.js or other CRDT libra
8.
by lherman 2y ago
Yeah, if WebRTC is the only communication channel, TURN will be needed, especially doing p2p. LMK your experience if you have any questions, hit me up on discord @lherman_cs
9.
by lherman 2y ago
Awesome! Yeah I have been doing WebRTC for a while and it's still always a pain to get this stuff up and manage it, I would love to hear what you're building and have you give it a try, feel free to hit me up on discord, username
10.
Show HN: PulseBeam – Simplify WebRTC by Staying Serverless(github.com)
15 points by lherman 2y ago|11 comments
11.
Analyze Robotics Data in Pure Go(github.com)
1 points by lherman 6y ago|0 comments
12.
Simple access to media input devices in Go(github.com)
1 points by lherman 6y ago|0 comments