I would like to argue to leave things as they are. Currently, the user can specify:

--use-server - the client uses avahi to find a suitable server on the local network.

--use-server=HOSTNAME - the client uses avahi to find a suitable server on the named host only

--use-server=HOSTNAME:PORT - the client contacts the specified server. Avahi is not required.

An IP address may be specified for HOSTNAME. 

The above applies to --use-server in conjunction with --list-servers and to --use-server when compiling a script (or both simultaneously).

--use-server=HOSTNAME is also useful in conjunction with --trust-servers for adding|removing trust in servers on a particular host.

When avahi is not present both --use-server and use-server=HOSTNAME will fail to find servers on the network, but could still find server certificates in NSS databases related to that host (useful when removing trust).

I see no reason to disable this useful functionality.

> [...]
> --use-server=HOSTNAME - the client uses avahi to find a suitable server on the
> named host only
> [...]

Note that I was only talking about the non-avahi case.

> When avahi is not present both --use-server and use-server=HOSTNAME will fail
> to find servers on the network [...]

Definitely or only usually?  If the former, OK, let's leave it alone.

> > When avahi is not present both --use-server and use-server=HOSTNAME will fail
> > to find servers on the network [...]
> 
> Definitely or only usually?  If the former, OK, let's leave it alone.

ping

(In reply to comment #2)
> > [...]
> > --use-server=HOSTNAME - the client uses avahi to find a suitable server on the
> > named host only
> > [...]
> 
> Note that I was only talking about the non-avahi case.
> 
> > When avahi is not present both --use-server and use-server=HOSTNAME will fail
> > to find servers on the network [...]
> 
> Definitely or only usually?  If the former, OK, let's leave it alone.

Sorry. The answer is Definitely. OK to close>

Thanks for the explanation.