vi/websocat

User friendliness TODO list

vi opened this issue · 5 comments

vi commented
  • single arg mode
  • Text and line mode by default Overhaul line and text mode options.
  • better description of options
  • Proper manual, move reference away from README.
  • Better repository description
  • Introductory examples in README
  • More pre-built versions with SSL support?
  • Github Pages site.
  • Extend examples with sample output and connection command lines
  • Manpage in deb.
  • Rename "specifier" to "address".
  • Warnings visible by default.
alkorsan commented

  • add a description to crates.io page?

  • remove the following? :

the readme says:

Replies to WebSocket pings are not tested at all

I tested with chrome websocket server interactively:
websocat ws://127.0.0.1:9222/devtools/page.....
and ping pong seems to work very well this is a wireshark screenshot showing them:
websocat ping pong

vi commented

That should happen on publish (i.e. on version 1.0.0 non-beta).

  • 👍1
vi commented

Is it Websocat sending pings and getting replies or Chrome sending pings and Websocat replies?

alkorsan commented

Chrome first send the ping then Websocat reply.

Zibri commented
  • add wrapper to command execution

I would also add an option to wrap the input/output of the executed command with another command.
An example would be for example to wrap in base64 so that the input is decoded then passed to the command then the output of the command is decoded and passed to base64 (or any other program).

So image I have a command like this:

encrypt_decript(line,pw)

if would be great to have an option to wrap socat input/ouput and websocket input/ouput with that command