Hacker News Reader

And are you going to run a dedicated signaling service and do all that STUN karate to just connect the peer to a publicly available server?

View on HN

> 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`

What I mean is that compared to, for example, WebSockets and WebTransport, WebRTC is more difficult to use (not through third-party libraries but "native" WebRTC data-channel API). But you are right and I was wrong, STUN is not necessary.

God, I wish I could find something like this for .NET.

You don't need STUN to connect to a publicly available WebRTC server.

Reply on news.ycombinator.com