Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

We sure are! We are using WebRTC in order to make it accessible on a large number of devices, but we are not using a public STUN/TURN server in order to keep our platform as secure as possible.


I am very curious about this approach. What kind of hardware/software. How much of a learning curve for the two of you as already-web developers?


I have only played with webrtc before, but what is the problem with public stun and turn?


I was going to say there aren't any, but here is a list: https://gist.github.com/sagivo/3a4b2f2c7ac6e1b5267c2f1f59ac6...


Thanks for posting this :)


There is no real problem with using a public STUN server. We are using our own STUN/TURN server just to ensure reliability and up time.


What kind of a stack are you running WebRTC on?


We're using React for our client app and bridging the connection using websockets.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: