Vitaly Shukela
Vitaly Shukela
Websocat1 contains `timestamp:` overlay that modifies messages, adding a numeric timestamp before each message.
Websocat1 can set various UDP socket options, allowing to use broadcasts, multicasts, set TTL.
`--udp-oneshot` may be less relevant for Websocat4, given it has new `udp-server:` mode, if `--one-message` gets implemented.
Instead of binding a TCP socket, Websocat1 can accept connections from an inherited file descriptor (e.g. from SystemD). **Implemented** in `4.0.0-alpha2`.
Websocat1 has explicit option to inhibit zero-length WebSocket messages, which can cause problems, e.g. an abort in a `seqpacket:` connection.
Websocat1 can base64-encode binary messages before printing (or base64-decode input messages before sending). If needed, this can extend to text messages.
Websocat1 can use SOCKS5 proxies. Note that listening for incoming connections over SOCKS5 proxy is tracked as a separate comment below.
Websocat1 has `autoreconnect:` overlay that allows to retry underlying connection without breaking upstream connection.
Actual reason is not Raspberry Pi, but new Rust version. The warning about (then future) breakage of `traitobject` dangled for a long time, but `traitobject v0.1.1` appeared only recently.
Maybe usual `m%%%%%%%" ... "%%%%%%%` (with enough per cent characters) can fill that niche (at least partially)?