Author is not always monitoring this room. In case of no replies create a Github issue.
websocat -s 1234
accept only one simultaneous connection?
reuse-raw:
mode it may stop reading from a WebSocket (which in turn makes Chromium stop writing to WebSocket) if there are no connection clients.
reuse-broadcast:
mode messages simply got dropped when nobody is connected.
timeout
with websocat
a top of usual timeout
's trickiness.