Asking users to download update (manifests) via an insecure connection is not
ideal, but considering most of them downloaded the original test build via an
insecure connection in the first place it might be ok
Unfortunately the detection is not perfect, so genuine TLS attacks can be
misinterpreted as the bug; completely invalid/expired/otherwise broken
certificates should be rejected though
Due to updatesAvailable being uninitialized there was a chance no error
message would be shown in case HTTPGetFile or ParseManifest returned
an error (the latter only when returning an error before setting
updatesAvailable) or the response code from HTTPGetFile was neither 200
nor 304
Requires a modified updater since the manifest structure differs
significantly
It is not recommended to publish OBS with unsecured update sources,
i.e. either implement signing for downloaded resources and/or use secure
communications for downloading (preferably both)
Made is so you can adjust mic/device audio time while streaming
updated installer script
updated some locale
got rid of audio time calculation completely
