Vitaly Shukela

> about reporting stats, maybe that could be interesting? There is Prometheus mode (mostly untested and not activated by default) that has some stats. Easier counter/stats overlay can be added...

> I don't want to use the handshake, just plain ws. Use `ws-lowlevel-client:` overlay instead of `ws://` URL. This would just get WebSocket framing without WebSocket handshake. websocat -t -...

> What about how to test file transfers? websocat -ub readfile:myfile.txt ws://... websocat -ub ws://... writefile:downloaded.dat websocat -ub --async-stdio ws://... > output_file websocat -Ub --async-stdio ws://... < input_file and so...

Currently `SSLKEYLOGFILE` is not recognized neither in Websocat1 nor in Websocat4. I'll consider adding `SSLKEYLOGFILE` support in Websocat4 when I'll be extending TLS features in it. --- Currently as a...

There is some native support of rustls in Websocat4 (not by default). You can build it with appropriate Cargo features and try.

Websocat1 features that are actually used by users are a priority for porting to Websocat4. You can put reactions in #276 to vote feature you use to be available in...

Quickly added `SSLKEYLOGFILE` support to Websocat4's rustls connector: ``` websocat4$ SSLKEYLOGFILE=abcde cargo run --no-default-features -F rustls -- --enable-sslkeylog wss://ws.vi-server.org/mirror/ Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.12s Running `target/debug/websocat...

There are may be subtle differences between Websocat1 and Websocat4 even with features that are supported in Websocat4 already. You can post here what combinations of features you use and...

> `--ping-interval 10` Outgoing pings are not yet implemented in Websocat4. And Websocat1's implementation have some issues when there is a lot of traffic / congestion. It that can lead...

> logout + disconnect ... when some particular commands are detected Note: if this is a security feature then it may be not well-designed; It should allow specific commands, not...