These have a large number of optional parameters, so these are placed in
a separate argument as an object:

ie: var s = new ConnectedSocket("synchro.net", "finger", {type:SOCK_DGRAM});
ie: var s = new ListeningSocket(["::","0.0.0.0"], "printer", "spooler", {retry_count:15});

if not unlimited.

- new @-code BPS:x (where x is 0/unlimited, 300, 600, 1200, 2400, ... 115200)
- new JS property: console.output_rate
So you can have mutliple output rate changes in a single file by using multiple
BPS @-codes.
Hopefully this doesn't do weird things with non-compliant terminals.

 -<columns> insert conditional-newlines to force wrap (e.g. -80)
 -newline   append a newline (CRLF) sequence to the output filea

The -<columns> option allows you to take "80-column ANSIs", artwork which
uses 80 columns and assumes the cursor will wrap to the next line
automatically, and insert Ctrl-A/ (conditional-newline) which allows the
file to be viewed nicely on wider terminals. Very cool.

Also added -newline (which can be used multiple times) to append one
(or more) newline sequences to the output file.

Use uppercase for Ctrl-AN and Ctrl-AL when -clear is used.

now accept an optional "count" argument (default: 1).
JS console.backspace() and carrage_return() methods now accept an optional
"count" argumnet (default: 1).

Ctrl-A/0x80+ is no longer supported in message nets (by my decree) so just
use spaces for ultimate compatibility. Synchronet's .asc/.msg file display
routines (e.g. putmsg) will still display Ctrl-A/0x80+ codes just fine.

text and quoted text. Enabled with the "-utf8" command-line option or by
setting utf8_support=true in the [fseditor] section of modopts.ini.
When UTF-8 support is enabled, the corresponding SCFG toggle option
("Support UTF-8 Encoding") should also be set to "Yes".
This is still a work-in-progress and UTF-8 character input and inserting
ASCII chars on lines that contain UTF-8 is still problematic.

editors that do not support UTF-8 (all of them, currently).

(default: No).

- bstrlen() moved to sbbs_t, accepts an option pmode argument so it can account
  for UTF-8 encoded strings correctly
- JS console.strlen() now accepts an optional pmode argument (e.g. P_UTF8)
- Renamed sbbs_t::utf8_to_cp437 to sbbs_t::print_utf8_as_cp437
- Create/use msghdr_hfield() to perform UTF-8->CP437 conversions as needed for
  printing/copying UTF-8 encoded message header fields.
- Defined XTRN_UTF8 misc setting flag. If a message editor does *not* have this
  flag, it is assumed to *not* support UTF-8. Will likely use this for UTF-8
  doors as some point too (none known to exist, yet).

new Socket(true) // creates an IPv6 TCP socket
new Socket(SOCK_STREAM, true) // creates an IPv6 TCP socket
new Socket(SOCK_DGRAM, true) // creates an IPv6 UDP socket
new Socket("myprot", true) // creates an IPv6 TCP socket named "myprot"

support to the JS API.

success. Upon failure to resolve, resolve_ip() returns null.

exit), just log the error and continue processing. Reported by wkitty42.

- Don't ever try to unpack a 0-byte file.
- Don't log anything or try delete if the file is < 24 hours old.
- Try to delete the file if it's >= 24 hours old (and log a msg, INFO-level).

I plan to convert all these to wiki-syntax eventually anyway.

show_msghdr()

contain UTF-8 characters.

The following message list formats were changed to no longer
artificially limit the length of displayed message subjects. If you have
a wide terminal (> 80 cols), show more of the message subject.
This is done by using the newly-supported bprintf(P_TRUNCATE,...)
feature, so no printf-format magic needed here.
- MailWaitingLstFmt
- MailOnSystemLstFmt
- SubMsgLstFmt

The following message list formats were changed to no longer
artificially limit the length of displayed message subjects. If you have
a wide terminal (> 80 cols), show more of the message subject.
This is done by using the newly-supported bprintf(P_TRUNCATE,...)
feature, so no printf-format magic needed here.

- Use the P_TRUNCATE pmode flag to prevent long msg subj from wrapping the
  terminal
- Use msghdr_text() to do the magic UTF-8/CP437 dance for messages with UTF-8
  header fields (e.g. to/from/subject)

This is why I assigned MSG_HFIELDS_UTF8 the same bit-flag value as P_UTF8. :-)

auto-limiting the length of printed lines to avoid  terminal line wrapping.
putmsg() already supported this pmode flag.

when decoding. Linear-white-space between regular atoms or between atoms
and encoded words is retained (as a single space character, Yoda).

flag in the message header.
When displaying message header fields containing UTF-8 using show_msghdr()
with text.dat string or with msghdr.asc and @-codes, do the "dance" to be sure
it's displayed correctly depending on the user's terminal (UTF-8 or not).

Advertise STARTTLS support (in EHLO response) when *not* already using a TLS
connection.

a message is posted to a different conference than the original sub-board with
completely different header information. I suspect this has something to do
HEADERS.DAT creation or import - not sure. So I added a "Conference"
headers.dat field for *messages* (it already existed for votes) and use that
value to confirm that the message header at the associated offset value in the
QWK packet has the same conference number as the section in the headers.dat
file. This is really just a sanity check and will only catch messages that were
mistakening cross-posted (to a different conference) - *but* it log errors and
save the bad QWK or REP file for me to examine more closely and see what's
going on - and the message won't be imported (just "lost", which is also bad).

So added more QWK import success/error checking and logging (especially for QWK
packets since REP importing already had a lot of stats covered).

Another check would be to store the original message number in the headers.dat
file as well and use that to confirm that the headers.dat section is the
correct match for the QWK message at that offset. I did not implement this
check, yet. The conference number check seems like it'll catch most of the bad
msgs and lead me to the root-cause.