CP437 would've made a bit more sense here, but we're HTML entity-encoding those
chars where needed.

JS scripts using system.temp_dir to store files get a sensible value (and not
the hard-coded default of just "temp").
This should fix the creation of ctrl/tempftelnet.url files.

- Export all FIDOCTRL (other FTN kludge lines) to the QWK HEADERS.DAT file.
  These should already be imported if they exist, but were never added during
  export, so untested/new behavior. The control paragraph (kludge line) of
  specific interest here is the "CHRS" (charset) kludge we need for UTF-8.

- Don't use the QWK "newline" character (0xE3) when the message is UTF-8.
  Use bare-LF's instead. This is pretty untested at this point as I will need
  another QWKnet board to post or receive UTF-8 encoded messages to test,
  getting the code into CVS is the first step. At least for now, there's no
  opt-in/out for this behavior. If your BBS has UTF-8 encoded messages, some
  QWK nodes or offline readers may have trouble with packets which include
  those messages. Or they may work fine (but likely display garbage CP437
  chars in-place of the proper Unicode codepoint glyph).

- The beginning of UTF-8 input support in getstr() - which needs more work,
  particularly around character and word deletion and insertion.
- The internal message editor now supports UTF-8 messages and kind of somewhat
  supports inputting UTF-8 characters in message text.

New put/print text flag: P_AUTO_UTF8 which can auto-detect UTF8 strings and
do the "right thing" for the user's terminal. New associated sbbs_t method:
auto_utf8() which automatically sets P_UTF8 for any stirng that begins with
a UTF-8 BOM (ZWNBSP). Else, if the P_AUTO_UTF8 mode flag is set, then
it checks to see if the string contains invalid US-ASCII chars but valid UTF-8
sequences and then sets P_UTF8 accordingly. Used by putmsg() and bputs().

There's a new permuation of bprintf() which accepts a mode argument
(i.e. for P_UTF8) and passes it on to the new mode-capable bputs().

Since sockwrap.h #Includes winsock2.h, let's #include it before any other
header files (e.g. genwrap.h)

Since sockwrap.h #Includes winsock2.h, let's #include it before any other
header files (e.g. genwrap.h)

InterlockedCompareExchange() expects a long*, not a uint32_t*.

genwrap.h, when needed.

Only about 4 million more to go. :-)

linked nodes: UseOutboxes (default: true)

BinkIT will continue to outboxes even when this option is set to false, but
SBBSecho won't place any mail files in the outboxes when this option is set to
true.

For PSI-Jack who was surprised that SBBSecho put mail files into outboxes.
Since it appears BinkD supports both outboxes and normal outbound directories
for linked nodes and BinkIT does as well, this shouldn't really make any
difference - just a sysop preference.

characters as the buffer width terminated by a linefeed would cause an
extra blank line to be inserted due to incorrect end-of-line detection.

The number of lines to allocate was calculated correctly, so this resulted
in writing past the last line in the screen buffer, corrupting memory after
the allocation.  Glibc detected this condition and crashed with a double-
free or corruption message.

doesn't actually *use* the password for anything, EchoCfg uses the nodecfg_t
definition from here (which includes the 'ticpwd') and the SBBSecho AreaManager
allows remote changes of the TicPwd by linked-nodes. For PSI-Jack.

Now supports changing the message subject (with Ctrl-S).  Ctrl-S was previously for text search, which has now been changed to Ctrl-W (word/text serach).  Updated the version to 1.67.  Changing the subject requires a Synchronet development build from July 21, 2019 or newer (that build added support for RESULT.ED even for

Use GraphicsConverter to display files in 999-bullshit.xjs for now.
Stop using bullshit.ssjs.  Use settings in 999-bullshit.xjs.

editor even if the editor was configured for QuickBBS/MSGINF drop files.
Don't use the subject line from RESULT.ED when the read-only subject mode
is used.

particularly salvageable here.  I have a work in progress to replace
these, however this may not end up being necessary.  Well, "necessary".

EventEmitter a la node.js, with an inheritance helper for adding it to
your Object. Same API as in node except:
- No concept of MaxListeners
- No prependListener/prependOnceListener
(These can be added later if they're needed. Too much hassle tonight.)
Currently a legacy-style library and should maybe be updated for newer
return-style load/require type use.

Ignore the _ though.

for ports where any incoming packet calls it.