Vitaly Shukela

Websocat1 can decompress the data coming from a WebSocket or compress it before writing to a WebSocket. This is unrelated to `permessage-deflate`.

Websocat1 (max edition) contains a simple ad-hoc way to encrypt/obfuscate messages using a key (without IVs).

Websocat1 can set special environment variables when starting subprocesses with `exec:`/`cmd:`/`sh-c:` that depend on incoming client socket address or used request URL.

Websocat1 can turn each message into a new connection (that sends one message, possibly receives one message in reply). This includes the `--foreachmsg-wait-read` mode.

Websocat1 can turn each line like `QQQ www` into a JSON snippet like `{"jsonrpc":"2.0","id":1, "method":"QQQ", "params":[www]}`, which can provide some convenience to interact with some services like Chromium's remotely controlled...

Instead of normal operation, Websocat1 can just print a `Sec-Websocket-Key` or `Sec-Websocket-Accept` header values, to aid implementing hacky Websocket upgrades using other tools.

Websocat1 can convert packets to byte stream (and back) using binary length-prefixed format where you can specify the length of the length field. **Implemented** in `4.0.0-alpha2`.

Websocat1 contains some tricks to adjust trailing newlines in WebSocket messages.

Websocat1 can be configured to use zero byte instead of newline to separate messages in a byte stream. Websocat4 can as well with `--separator 0`, but specifically `-0` or `--null-terminated`...

Websocat4 and Websocat1 have different architectural decisions regarding to how to connect bytestream-oriented and datagram-oriented sockets (where a WebSocket counts as datagram-orinted). This makes direct port of `--no-line` impractical, but...