fix instructions (#161)

README.md

@@ -21,19 +21,23 @@ Technically you could run this with a single computer, but it is more fun if you
 
 ## Steps
 
-1. Open chrome://flags on all the computers that you want to use to test the tele-conferencing system, add the ip of the computer that you will use as the server to the Insecure origins treated as secure list.
-<img width="1728" alt="Screen Shot 2022-10-30 at 10 00 43 PM" src="https://user-images.githubusercontent.com/1176339/198916116-e85bd52a-02b3-40ed-9764-d08fd3df8487.png">
+1. Start the servers on the computer that you intend to use as the server using `ACTIX_UI_BACKEND_URL=ws://<server-ip>:8080 make up` (requires docker).
 
-2. Start the servers on the computer that you intend to use as the server using `ACTIX_UI_BACKEND_URL=ws://<server-ip>:8080 make up` (requires docker).
+2. Enable WebTransport Developer Mode:
+   - Go to `chrome://flags/#enable-webtransport-dev-mode`
+   - Enable the flag
+   - Close chrome
 
-3. If your server computer is behind a firewall, make sure that TCP ports 80 and 8080 are open
+3. Open chrome using the `launch_chrome.sh` script, this will allow you to use webtransport locally.
 
-4. Connect all computers to `http://<server-ip>/meeting/<username>/<meeting-id>`
+4. If your server computer is behind a firewall, make sure that TCP ports 80 and 8080 are open
 
-5. Make sure that you "allow" access to your mic and camera:
+5. Connect all computers to `http://<server-ip>/meeting/<username>/<meeting-id>`
+
+6. Make sure that you "allow" access to your mic and camera:
 <img width="1840" alt="Screen Shot 2022-10-24 at 8 23 50 AM" src="https://user-images.githubusercontent.com/1176339/197536159-61f0d9c8-c8fa-454c-8f40-404ed52dca98.png">
 
-6. Click connect on both browsers, and enjoy:
+7. Click connect on both browsers, and enjoy:
 
 ![Oct-24-2022 08-37-09](https://user-images.githubusercontent.com/1176339/197853024-171e0dcc-2098-4780-b3be-bfc3cb5adb43.gif)
 

videocall-client/start_chrome.sh

@@ -0,0 +1,26 @@
+#!/bin/bash
+
+set -e
+
+SCRIPTPATH="$( cd -- "$(dirname "$0")" >/dev/null 2>&1 ; pwd -P )"
+
+# generate certificate
+
+#openssl req -x509 -newkey rsa:2048 -keyout $SCRIPTPATH/certs/localhost.key -out $SCRIPTPATH/certs/localhost.pem -days 365 -nodes -subj "/CN=127.0.0.1"
+
+#openssl x509 -in $SCRIPTPATH/certs/localhost.pem -outform der -out $SCRIPTPATH/certs/localhost.der
+
+#openssl rsa -in $SCRIPTPATH/certs/localhost.key -outform DER -out $SCRIPTPATH/certs/localhost_key.der
+
+SPKI=`openssl x509 -inform der -in $SCRIPTPATH/actix-api/certs/localhost.der -pubkey -noout | openssl pkey -pubin -outform der | openssl dgst -sha256 -binary | openssl enc -base64`
+
+echo "Got cert key $SPKI"
+
+echo "Opening google chrome"
+
+case `uname` in
+    (*Linux*)  google-chrome --origin-to-force-quic-on=127.0.0.1:4433 --ignore-certificate-errors-spki-list=$SPKI --enable-logging --v=1 ;;
+    (*Darwin*)  open -a "Google Chrome" --args --origin-to-force-quic-on=127.0.0.1:4433 --ignore-certificate-errors-spki-list=$SPKI --enable-logging --v=1 ;;
+esac
+
+## Logs are stored to ~/Library/Application Support/Google/Chrome/chrome_debug.log