Re:Show HN: WebRTC signalling data using QR codes
by AquiGorka on Friday October 12, 2018 @12:40PM
(#18202643)
This is still WebRTC, so the same limitations apply. The QR codes are used to share the `signalling data` for the WebRTC connection.
[ Parent
| on HN ]
Re:Show HN: WebRTC signalling data using QR codes
by cjbprime on Friday October 12, 2018 @01:48PM
(#18203221)
More detail: Yes, WebRTC contains several methods for routing through NATs -- ICE, STUN by default (using your browser's default STUN server), optionally TURN.
Re:Show HN: WebRTC signalling data using QR codes
by deathanatos on Friday October 12, 2018 @03:48PM
(#18204184)
My browser manufacturer has a STUN server? Where can I find that? (e.g., for Chrome or Firefox)
Edit: AFAICT, this isn't correct. Your browser has no notion of a "default" (or any other) STUN/TURN server. The JavaScript doing WebRTC has to specify one.
That said Google runs one, at stun.l.google.com:19302; but it isn't clear if that's something third-parties could or should make use of (or if Google even permits such activity), though it seems like plenty of examples (and perhaps even real-world uses) make use of it.