With such a STUN server URL, no wonder nobody ever gets a match…
And it's kind of a nasty bug: it doesn't appear anywhere in the JS console, or in the network tab of the browser, and it's likely to work when testing locally (I haven't tested, but you should not need stun to generate local ICE candidate) so the dev could have tested in local, seen it was working and posted it on HN. Just to discover it was not working after reaching the front page… Sad day for the poor dev.
But it still doesn't work, because there should be “stun:” at the begining of the URL.
(Otherwise you get this Error “RTCPeerConnection constructor passed invalid RTCConfiguration - improper scheme” (Firefox, but you should have a similar one in any browser))
> iceServers:
> urls: ["stun:stun.l.test.com:19000"]
With such a STUN server URL, no wonder nobody ever gets a match…
And it's kind of a nasty bug: it doesn't appear anywhere in the JS console, or in the network tab of the browser, and it's likely to work when testing locally (I haven't tested, but you should not need stun to generate local ICE candidate) so the dev could have tested in local, seen it was working and posted it on HN. Just to discover it was not working after reaching the front page… Sad day for the poor dev.