Don't corrupt UTF-8 strings with SAFECOPY() (use new SAFECOPY_UTF8).

Some terminals (notably, Windows Terminal) display zero width UNICODE chars
as a single column-wide space. <sigh> Auto-detect the zero-width "width"
(1 or 0) of the terminal during connection and UTF-8 auto-detection.

getstr() works a lot better now with UTF-8 strings with wide chars (e.g.
emojis), but likely much more to do.

This is not a completely unexpected thing to happen during ungraceful
termination

I'm surprised this didn't create a warning somewhere: treating char* as a
bool!

Which means that every time textgen was built, it was immediately out of
date (and requiring a rebuild).

(but prefer the proper/configured case, based on config in SCFG).

Works around a problem where DDMsgReader always creates QUOTES.TXT (never
quotes.txt), but SBBS tries to read in the file with the case it expects.
This wouldn't be a problem on case-insensitive file systems (Windows).

Resolves the writemsg.cpp error reported by Nelgin

Commit 75c5c9e5 was initially to address server termination (sisue #236), but
expanded in scope to include server recycling (e.g. due to semaphore/config
file touch) and that turns out to not be what most sysops want.

If you want an immediate/ungraceful recycle, do a restart (shutdown/stop and
then start) instead.

Immediate/ungraceful server shutdown/termination is still in effect however.

No change to the "server pause" feature either, so combining pause with
recycle would be effective to prevent *new* client connections while waiting
for existing clients to disconnect and allow a recycle to happen.

Commit d1182efc

(or terminating) the server.

This will allow background JS threads to terminate when recycling, so the
server doesn't just hang indefinitelyi when recycling.

Add more logging in cleanup() when waiting for children threads to terminate.

Also, eliminate the global 'terminate' variable, answering the question:
  Can this be changed to a if(ws_set!=NULL) check instead?

Yes, yes it can.

e.g. month and day reversed

Updated help text for "Support UTF-8 Encoding" for external editors.

1. Add an 8th line to MSGINF (for SlyEdit): the character set expected
   (either "CP437", the default, or "UTF-8") based on the SCFG configuration
2. Don't apply "Soft-CR" (0x8D) stripping/expansion for UTF-8 editors

*This* is the way. Oops.

This was the auto/default mode before commit 2ca1e4a0

If you really want the VGA aspect ratio, use the '-v41' option.

that we're setting all the values anymore. :(

wrong, do c_cc the stupid (but POSIXly correct) way with a billion
supporting.

Monster.

This bug caused crashes in the Windows build of sbbs when using the ;spy
sysop command with MQTT enabled.

Memory that is allocated in one DLL (e.g. sbbs.dll) must be freed in that same
DLL (e.g. sbbs.dll, not mosquitto.dll).

mosquitto_message_free() here frees the msg pointer, but we didn't allocate
it in mosquitto.dll in the first place, so that's wrong. The proper mosquitto
function to use in this case is mosquitto_message_free_contents().

Since it is possible for someone to change the add/import date of a file
after it's been added to the filebase, the natural/unsorted order might not
actually be the same as "date ascending", so let the sysop/script-author
really re-sort by date ascending if that's what they're trying to do.

I think this is addresses the issue that Nightfox and Nelgin were describing
in #synchronet.

(as a fall back to the full external program name).

... to determine/print the current external progarm being run.

This fixes issue #716

Make mqtt_putnodedat() use a 1-based node number, like the other putnodedat()
functions.

The bug (misuse of mqtt_putnodedat) was actually in js_system.c, but fixed the
API to match the common expectation.

The patch that sets the read timeout every time for getData() was
flawed, because getData() itself will sometimes set the read timeout
for the next call.

The patch was intended to ensure that the write timeout never
clobbers the read timeout, so now we track if getData() explicitly
set the timeout and if it did, we don't reset it.

It appears that if the timing is "just wrong", a large POST can
cause TLS to fail.  This has shown up as an inability to edit
pages in the wiki.

This is not a fix however, but simple a workaround until this is
root-caused.

K_CP437 changed to K_UTF8 with the inverted logic. If you have code/script
that can handle UTF-8 input, then you need to specify K_UTF8 in calls to
inkey, getkey, getstr. Or else, you're going to get a CP437 translated
version of any non-ASCII (UNICODE) UTF-8 chars, if there's a mapping
available. This only impacts UTF-8 terminals.

There are just so many places in Synchronet where UTF-8 input could cause
problems, it makes sense to translate UTF-8 to CP437 by default and make
true UNICODE/UTF-8 handling the exception.

Sorry Nightfox, you'll need to remove the K_CP437 detection/use code you
just added to SlyEdit.