This API is no longer working in the current Firefox version (69)
There is also a similar discussion here: https://github.com/webrtc/samples/issues/302

Updating import to fix deprecation warning

Docker config changes supporting TLS (part 2). This fixes an issue with pip and some of the dependent libraries.

* Bugfix for systems that cannot generate openssl certs. Includes self-signed certs that expire in 10 years. Removed automatic cert generation from install-deps.sh. Updated create-cert.sh to manually generate 10year certs (or any custom duration).

* Docker config changes to support web demo TLS

What does this PR do?

Minimally invasive migration to TLS for the http (8000) and websocket (9000) endpoints for the real time web demo.

Where should the reviewer start?

Install the demo like a normal install. During the install-deps.sh script it will prompt for questions to generate a local self-signed cert. Anything can be entered into the cert. Start the demo as normal but connect on https://domain:http_port instead of http.

How should this PR be tested?

The first step is the cert generation (added to install-deps.sh for convenience). The second step is ensuring the two endpoints are brought up. The next step is loading the web page and accepting the self-signed cert. Reloading the web app everything should now be secure, e.g. no errors or warnings and the video works as normal.

Any background context you want to provide?

I tried to be as minimal as possible so the changes tends to follow the existing structure rather than a refactor of anything major. With that said, SimpleHTTPServer doesn't work with TLS via the -m flag so that is now a short script. I updated all the html/js files to point to https/wss. I also updated the js for Firefox's change from navigator.mozGetUserMedia to navigator.mediaDevices.getUserMedia.

What are the relevant issues?

#75

Questions:

Do the docs need to be updated?
Yes. I updated the script's docs in demos/web but didn't make any changes outside of demos/web

Does this PR add new (Python) dependencies?
I don't think so.

* Make OpenFace Python 3 compatible, retaining Python 2 compatibility.
Tests could be parameterised to test for either Python 2 or 3.
Tests currently fail due to different library calculation outcomes?

* Tiny change to remove the dependency on nosetest3.

* Dockerfile updates for OpenFace + Python3 + Dlib19.2 + OpenCV3.2

* Revert "Dockerfile updates for OpenFace + Python3 + Dlib19.2 + OpenCV3.2"

This reverts commit ec08fc92261877d8a2023ab6dc8fd0610641bd2c.

* Change for python2 backwards compatibility

* Change for python2 backwards compatibility

* Change to ensure python2 backwards compatibility

* Change to ensure python2 backwards compatibility

This looks better and is lower data 😄

* Make TorchNeuralNet a context manager.

Add __enter__/__exit__ method to kill Torch subprocess

* Update doc for the TorchNeuralNet

* Fix code snippets

* Update doc for enter/exit methods

* Format docstring for enter/exit methods

This reverts commit 882109c1.

Thanks Daniil Belkov!

`byte` was defaulting to `"float"`

* Added --multi option to infer operation to show a list of faces detected in image

* Added testing for infer --multi demo