(data/user/*.subs - in familar .ini syntax)
indexed by the sub-board internal rather than the old flat binary file using
the troublesome "pointer index" (ptridx) as an offset. The old files
(data/user/ptrs/*.ixb) will still be read in when the new file doesn't exist,
for upgrading users automatically to the new method of pointer storage.
This should resolve long-standing issues around users' new-scan pointers and
configurations getting corrupted when the sysop inserts/remove sub-boards.
However, if you change a sub-board's internal code, that invalidates the users'
pointers and scan configurations - so that may need to be addrsesed via SCFG.
The subs' ptridx values are still be used for storing QWKnet hub pointers, for
now, but that too will soon be addressed with a new file format for those ptrs
too.

stuff in binkp.js, only the protocol.  BinkIT now does the Mystic check.

increase post-count width supported from 4 to 5 digits (beautifully).

networking technology for 20 years. :-(

or not).

severity) whenever there is an SSH session establishment failure, because
some of the SSH failure errors are DEBUG level severity and won't be visible
with "Normal" (informational) log output filtering. This resolves the issue
of seing "SSH connection accepted from <ip-address> port <port>" messages
with no follow-up messages as to what happened to that connection.

messages. There's a lot of places in this script where we just send a
(somewhat explanatory) M_ERR string, but don't log anything locally unless
debug-level logging is enabled, now we'll at least log those messages with
a bit higher severity.

the binkp.js default, 32-hexchars/16-bytes). Even IRex v2.31 requires a
16-byte challenge, so experiment is over.
Log more details when a CRAM-MD5 authentication response doesn't match
(e.g. to make case-mismatch or other cause of authentication failures
potentially more obvious - still debugging the Mystic inbound CRAM-MD5
auth failure and this might help).

like a str_list_t declared in line (but the char* is fine?!).

Remember the last forced timed event setting.

- lower log level (raise severity) of "Waiting for ..." msgs from Debug to Info
- log a message when done waiting (for clients, threads, etc.)
- only one #### log line per termination event

(default is ctrl/status.sock).

return arrays rather than calling printf() directly. Also, make the ASCII
portion of the output optional (but enabled by default).

Windows, every time. For example, this resulted in the same BinkP CRAM-MD5
challenge being sent for every mailer session. Fixed by calling sbbs_srand
in the service's thread, not (just once) in the accept thread.

This shouldn't cause any functional changes since it's the outbound dirs that
matter, and they already can't have duplicates.

just don't "run outbound" for those nodes.

  Locking c:\binkd\outbound\00da02bc.bsy
  Error 2 creating c:\binkd\outbound\00da02bc.bsy
  Failed to set date in the future fdate (-1) != future (1687417603)
Also, added some debug dump of "outbound_roots" which appears to contain
duplicates, at least when the ftn_domains.ini file is not in use:
 Outbound roots: ["c:\\binkd\\outbound","c:\\binkd\\outbound"]

I got distracted by trying to wiki-syntax and then markdown and finally
uust used asc/ctrl-a format. Sorry took so long.

Missing synonym since 1.74 (over 8 years ago)

decided that CTRL-N should be page-down.  This should fix page down in quote
mode which has been broken since 1.83 three months ago (with a mention in the
log that the commit broke fseditor.js)

This patch fixes the user object process by ordering specific parts in a way
that fixes the following problems:

Post-delayed realname and handle caused realname and handle not to be set to
the user object. Moved copy_user_template_to_user to after bbs.login just
before the bbs.user_sync() solved that.

Choosing not to use the randomly generated password would fail on every
situation. Reordering user.security.password to be underneath user.number
solved this problem.

Also clear the screen and display "Returning to <bbs name>" when exiting.

in the legacy section of msgbase-exported entries.

only disconnected.

reach the configured "max size", newly added log lines would not use the
configured color/font for the msg's log-level (they'd all use the default
color/font).