turn

I see a couple ways to combat that. * Your TURN server should provide APIs that allow you to verify that allocations/permissions are only created for your users. * Use an auth mechanism that has an expiry time. Like [0] [0] https://github.com/pion/turn/tree/master/examples/lt-cred-ge...

> dedicated signalling For my small projects I run my HTTP + WebRTC in the same server. My signaling is one POST. Maybe I am missing the complexity, but I don't feel any additional pain compared to running any network service? > STUN Karate Mind explaining more? You don't use STUN for connecting to a world routable host. If you need it I use https://github.com/pion/turn and run my STUN server embedded in my HTTP server. I do do anything but point my `PeerConnection` at `my-service.com`

Are your TURN and / or STUN implementations publicly available? There are also nice existing FOSS implementations: (Golang) Pion TURN - https://github.com/pion/turn (Rust) Port of Pion TURN - https://github.com/webrtc-rs/turn and https://webrtc.rs/ (Rust) TURN server and client - https://github.com/sile/rusturn (Python) TURN Server - https://github.com/m32/sturn (Javascript) Node.js TURN server - https://github.com/Atlantis-Software/node-turn (C) TURN server - https://github.com/Atlantis-Software/node-turn Additional reading if you care to refresh on WebRTC terminology like STUN, TURN, ICE, etc: https://developer.mozilla.org/en-US/docs/Web/API/WebRTC_API/... https://www.twilio.com/docs/stun-turn/faq

There is a very neat implementation of a TURN from Pion https://github.com/pion/turn

Amazing work! The WebRTC community needs something like this so bad. Not only will this push a bunch of users toward self-hosted/free software but will also inspire others to build cool things :) If/when you hit scaling challenges I would love to help! I maintain github.com/pion/turn and github.com/pion/webrtc. One of the reasons I built it was so that I could put my TURN and Signaling server in the same process. It makes it way easier to tie your auth together for signaling+TURN. Then if you do go down the SFU route lots of interesting things you could do. You can see that with how screego[0] does it. Happy to help however I can (even if not using Pion!) [0] https://github.com/screego/server/blob/e845b3d29c4b5794ed10f...

I am super happy that I invested in Go. I ended up working on TURN, WebRTC and DTLS and feel I made the right choice. The impact vs time spent was worth it. I don't think there is any other language I would have had a better experience. Either it is too niche, or it is so popular that the community is anemic. * https://github.com/pion/dtls * https://github.com/pion/webrtc * https://github.com/pion/turn Go is really great as a 'teaching language'. I have seen lots of software pop up that was inspired by reading the Pion code. I think that is great, it is much harder to read and learn from other languages. Also really great for contributions. I get so many people making their first Open Source commit. The languages simplicitly really makes it easy. The most frustrating thing about Go isn't even the language, it is the community for me. It i