It should be noted that the API and its browser support only recently stabilized.
Also, while using WebRTC for direct peer-to-peer-connections is rather easy, adding more peers is where the problems start.
Otherwise, it's a pretty great addition to the web tech stack, allowing a great deal of flexibility for sharing various streams of any format and content.
Does building a STUN server should be easy?
How to build a simple TURN server?
I am interested to see the role of 'servers' vs the role of the 'clients'
I'm not sure how easy or difficult it is to build a STUN or TURN server from scratch on our own since I haven't tried it.
For my previous WebRTC project, I used an open source TURN/STUN implementation called COTURN and hosted it on a DigitalOcean instance.
Also, there are multiple publicly available STUN servers that you can use.
tinyurl.com/y3345yop (All STUN servers in this list may not be live)
The task of STUN seems simple, which is telling you your IP, this is why I asked about the complexity of building one.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.