From dc6297d5df43f87d1ed2ea1b5c1f5a5193ec235a Mon Sep 17 00:00:00 2001
From: "B. Watson" <urchlay@slackware.uk>
Date: Mon, 2 Mar 2026 22:03:10 -0500
Subject: Fix "nick already in use" and permutation.

---
 README.txt | 69 ++++++++++++++++++++++++++++++++++++++++----------------------
 1 file changed, 45 insertions(+), 24 deletions(-)

(limited to 'README.txt')

diff --git a/README.txt b/README.txt
index 3e27daf..a1bc0d1 100644
--- a/README.txt
+++ b/README.txt
@@ -1,33 +1,54 @@
 FujiNetChat - an IRC client for the Atari 8-bit with FujiNET.
 
-For now, this is very rudimentary. It can currently:
-
-- connect to an IRC server
-- complete the user/nick registrations process [*]
-- respond to server PINGs
-- join a channel (but only one!)
-- send/receive channel messages
-- receive private messages
+For now, this is pretty rudimentary. It can currently:
+
+- connect to an IRC server.
+
+- complete the user/nick registration process, including handling the
+  "nickname already in use" error (by adding _, 1, 2, etc to the
+  user nick).
+
+- respond to server PINGs.
+
+- handles nick changes.
+
+- multi-window display, with one screens' worth of scrollback per
+  window.
+
+- join up to 5 channels, each in its own window. more than 5 channels
+  can be joined, but the extra ones get multiplexed together in the
+  server window.
+
+- send/receive channel messages.
+
+- "highlights" channel text that contains the user's nick.
+
+- receive private messages (in a dedicated private messages window).
+
+- server window to keep the chatty server messages from cluttering up
+  the channel windows.
+
 - if you use raw IRC protocol, you can send private messages:
   /PRIVMSG <nick> :this is the message text.
 
-[*] almost: it doesn't recover gracefully from "nick already in use"
-    or "invalid nick", and if the server truncates the nick, it doesn't
-    notice.
+- input box at the bottom of the screen, allows editing and can
+  handle up to 239 characters of input.
+
+- status bar, shows the current window's number, name or channel,
+  and which other windows have new text in them. disappears (replaced
+  by the input box) when the user starts typing, and reappears when
+  the user presses Enter to send the message/command, or Shift-Clear
+  to abort it.
+
+Differences from FujiChat:
 
-I have great plans for the future:
+- FujiChat does its own TCP/IP and DNS, using SLIP. FujiNetChat offloads
+  the network stuff to the FujiNet device, freeing up memory for more
+  client features (e.g. the multi-window display).
 
-- custom display. it will support multiple screens (like linux virtual
-  consoles), one per channel or query (PM conversation). of course due
-  to limited RAM, there won't be many windows supported. On a 48K
-  machine, probably 8 windows, each with a screens' worth of scrollback,
-  which means 16K of video memory...
+- FujiChat only supports joining one channel, and has no multi-window display.
 
-- an 'input box' at the bottom of the screen, so we don't have to keep
-  redrawing the user's input as data comes in. this will require a 
-  custom display list.
+- FujiChat can be used with software 80x25 or 64x32 text modes. FujiNetChat
+  is (currently) 40 columns, using GR.0 style text mode.
 
-- a status bar that appears in place of the input box, until the user
-  starts typing (and reappears when he hits Return). it will show the
-  current window's channel or nick, and activity status for the other
-  windows.
+- FujiNetChat allows you to type the { } ` ~ characters.
-- 
cgit v1.2.3