-If it is running on a different host then the server will need a
-.B listen
-directive in its configuration and the clien a matching
-.B connect
-directive. Also the client will need user passwords, either in
-.IR pkgconfdir/config. USER
-or
-.IR ~ USER /.disorder.passwd .
-.PP
-You might use commands such as the following to set up a standalone instance of
-Disobedience:
-.PP
-.RS
-.nf
-cd
-mkdir .disorder
-echo password <your password> > .disorder/passwd
-echo connect <hostname> <port> >> .disorder/passwd
-chmod 600 .disorder/passwd
-.fi
-.RE
+If it is running on a different host then the easiest way to set it up is to
+use the login details window in Disobedience.
+Enter the connection details, use Login to connect to the server, and then
+use Save to store them for future sessions.
+.PP
+The other clients read their configuration from the same location so after
+setting up with Disobedience, tools such as
+.BR disorder (1)
+should work as well.
+.SH BUGS
+Disobedience is newly introduced with DisOrder 2.0.
+There are bound to be bugs.
+Please send feedback.
+.PP
+There is no particular provision for multiple users of the same computer
+sharing a single \fBdisorder\-playrtp\fR process.
+This shouldn't be too much of a problem in practice but something could
+perhaps be done given demand.
+.PP
+Try to do remote user management when the server is configured to refuse this
+produces rather horrible error behavior.
+.SH FILES
+.TP
+.I ~/.disorder/HOSTNAME\-rtp
+Socket for communication with RTP player.
+.TP
+.I ~/.disorder/HOSTNAME\-rtp.log
+Log file for RTP player.