v1.4.7

Fixed

• Start a conversation in the browser interface when the gateway is reached over plain http on a LAN address. crypto.randomUUID carries [SecureContext] in the Web Cryptography IDL, so a browser outside a trusted origin does not carry it and naming a new session threw. The interface worked behind TLS and on localhost, which is why the failure only appeared on a deployment. The session id now comes from getRandomValues, the one member of Crypto an insecure context still offers, and falls back to a timestamp only where neither exists