Hacker News Reader

Browsers generally will not set `navigator.mediaDevices` unless you're using a secure connection (except for localhost). This is frustrating when testing apps that use these features as you then need to use self signed certs. I understand why, though.

Yes for use WebRTC is mandatory have https either for browsers based on Chromium, Gecko and Webkit. (Chrome, Firefox, Safari).

I'm completely agree with you because I'm tried on iOS Safari and I got a poor performance over the video call.

I’m pretty sure Chrome also blocks WebRTC over HTTP, although with some of these kinds of things it can be difficult to verify.

Note, webRTC "over" http or https is not a thing. What is a thing is a page that is served over http or https initiating a webRTC connection, which goes over UDP and is peer to peer, unless there's relay servers, in which case it should still be over UDP.

Should work with localhost origin.