Building real systems on WebRTC is hard.
Mesh networking is chaos. SFUs help — but most miss the sweet spot.
So I built PulseBeam:
• Single-binary SFU
• Rust-based
• Built to scale
A little crazy in 2025? Probably 😄
Building real systems on WebRTC is hard.
Mesh networking is chaos. SFUs help — but most miss the sweet spot.
So I built PulseBeam:
• Single-binary SFU
• Rust-based
• Built to scale
A little crazy in 2025? Probably 😄
Create real-time video/audio/data without WebRTC headache. pulsebeam.dev helps in managing your states. Your server can stay serverless!
Since the browser blocks only media AFAIK, mocking the getUserMedia has been my go-to solution for this github.com/theopenwebjp....
I don't typically self-promote, but pulsebeam.dev makes this process easier:
1. [client] go to a specific URL
2. [server] authenticate and return a JWT token that only allows client from step 1.
3. [client] connects to the other phone
Alternatively, peerJS or DIY WebRTC with QRCode
Nice work and logo :D. Did you end up using data channel and drawing the cursor separately?
Ideally, Macbook Air with M3 but without the OS bloat and more storage.
TIL: Reduce those annoying CORS preflight requests with a simple header tweak! 🚀
Access-Control-Max-Age: 86400
Boom! Your browser now caches preflight responses for 24 hours. Less overhead, faster API calls. 🔥 #webdev #codingtips