* Generate server's keypair. And share its public key among users.
  Fact of server's public key knowledge means ability to connect to it.

    $ vors-keygen 5>pub 9>prv
    $ vors-server -prv prv -pub pub -bind [2001:db8::1]:12978

* Client uses external commands for reading from microphone and playing
  it back. By default it uses SoX'es "rec" and "play" commands.

  Pay attention that VoRS expects *ONLY* one channel, 48kHz, 16-bit
  signed little-endian audio format. Empty strings in -rec/-play options
  mean no recording/playback attempts.

  -play command is spawned for each participant.
  Your OS should mix their output together.

* Start the client, providing server's public key and our username:

    $ vors-client -srv "[2001:db8::1]:12978" -pub pub -name NAME

  Pressing F10 in server/client TUIs means quitting.
  Pressing F1 in client means "mute" toggling.
  Cycling through chat windows and peers in client is done by Tab.
  Pressing Enter on the peer silences it locally.

* -room allows you to join non-root room.
  -passwd allows you to protect it with provided password.

* -mute-toggle allows you to toggle mute by external utilities. For
  example you can use suckless minimalistic sxhkd daemon to capture X11
  key events and execute commands:
  => sxhkd

    $ mkfifo /tmp/vors-mute-toggle.fifo
    $ cat >sxhkd.cfg <<EOF
    XF86AudioMute
        herbe $(cat /tmp/vors-mute-toggle.fifo)
    EOF
    $ [run sxhkd]
    $ vors-client [...] -mute-toggle /tmp/vors-mute-toggle.fifo

  That will toggle mute on "audio mute" event and print its current
  state as a herbe notification.
  => herbe