removed mismatch warning

README

@@ -1,6 +1,6 @@
 tii: a Tcl-based suite for working with ii/IDEC protocol
 ========================================================
-This suite implements the client side of ii and (partially) IDEC protocols of
+This suite implements the client and server sides of the ii/IDEC protocol of
 distributed, cross-platform, text-based communication (a FIDOnet successor, so
 to speak). See ii-doc.txt for the protocol documentation.
 
@@ -20,6 +20,8 @@ The tii distribution consists of the following parts:
   posting messages to a particular station (not included in the repo)
 * tiix.tcl: the GUI ii/IDEC viewer that also leverages tiifetch and tiipost to
   provide fetching and posting functionality
+* tiid.tcl: the basic ii/IDEC node software that uses the same DB format
+* tiid-user.tcl: user management utility for the tiid node
 
 Readiness status
 ----------------
@@ -31,12 +33,12 @@ Readiness status
 * stations.txt (format): ready/tested
 * auth.txt (format): ready/tested
 * tiix.tcl: ready/testing
+* tiid.tcl: ready/testing
+* tiid-user.tcl: ready/tested
 * Overall status: basically ready, bugfixing in progress
 
-Usage
------
-This section is a work in progress and will be updated as more components are
-developed.
+Client usage
+------------
 
 ### Fetching the messages (tiifetch.tcl): ###
 
@@ -154,14 +156,49 @@ Any of the fields can be omitted, as well as the file itself.
 You can also use torsocks with any script invocation in order to fully cloak
 your originating IP address.
 
+Server usage
+------------
+This section is in progress.
 
-FAQ
----
-- Does tii implement any IDEC extensions?
+### Starting the tiid server ###
 
-Only one: fetching list.txt from the station to get the entire list of echo
-conferences served by this station. This is something that the original ii
-spec did not support.
+The tiid.tcl server accepts the following parameters:
+
+tiid.tcl [port] [nodename] [dbfile]
+
+where:
+
+* port (default 8080) is the TCP port to listen to,
+* nodename (default "tiid") is the unique node name (needed to fill the fields
+like message originating address),
+* dbfile (default "tii.db" in the script directory) is your database path.
+
+The tiid server is compatible with all existing HTTP-based clients and also
+with the clients that utilize Gopher/Nex transport, like tiifetch/tiix. It has
+automatic protocol detection, so both HTTP and Gopher/Nex clients can connect
+to the same port.
+
+Although the tii client only can post via HTTP, the tiid server also supports
+direct TCP posting with GET-like queries via Gopher/Nex protocols.
+
+### User management on the tiid server ###
+
+As of now, only manual user management is supported. The simplest way is to
+use the included tiid-user.tcl script to perform administrative tasks.
+
+Adding a user or changing its password (auth string):
+
+tiid-user.tcl dbfile user someusername auth SuperSecretAuth123 acl "*"
+
+If you don't supply the acl parameter, it will default to "*".
+
+Changing the list of echos the user can post ("*" means all, "" means none):
+
+tiid-user.tcl dbfile user someusername acl "echo.1,echo.2..."
+
+Note that you need to set up ACL every time you change a user's password.
+
+In both cases, the database file and the user field are mandatory.
 
 
 Credits