Vitaly Shukela

Implemented `--separator-inline` option to make it preserve the `\n`s.

1.5.0 is rather old version. I'll probably just remove that part; @tim77 may resubmit the Fedora section for README when it working again.

> If an endpoint receives a Close frame and did not previously send a Close frame, the endpoint MUST send a Close frame in response. Websocat expects close frame to...

Quickly implemented proper shutdown in `-E` mode in `websocat4` branch. When using `echo | websocat ws://127.0.0.1:1234` as client and `websocat4 -E -s 1234 --log-traffic` as server, I get ``` READ...

Because non-`-E` mode already closed the writer properly (i.e. with an attempt to send the close frame). But without `-E` that closing is only triggered by a writer to the...

Currently no. Windows builds are mostly provided because of it is easy to do so; I don't typically test them. Is it easy to set up a cross-compilation from Linux...

Here are some sample executables (hello-world and a Websocat4 build). Do they work for you? [aarch64-pc-windows-gnullvm_sample.zip](https://github.com/user-attachments/files/17299345/aarch64-pc-windows-gnullvm_sample.zip)

Maybe it's time to upload apk as a 1.32 Github release?

Websocat1 can print a line on stdout when a listening port is ready to accept a connection. Example: ``` $ /opt/websocat --stdout-announce-listening-ports -bE ws-l:127.0.0.1:1234 mirror: LISTEN proto=tcp,ip=127.0.0.1,port=1234 ``` **Implemented** in...

Websocat1 can use stdin/stdout in nonblocking mode, providing simpler code path and increased efficiency in some scenarios at the cost of increased probability of some bugs. This is especially useful...