This fixes issue #629

I'll add detailed docs to http://wiki.synchro.net/custom:atcodes soon, but the
list is:

- TERMTYPE
- TERMROWS
- TERMCOLS
- AUTOTERM
- ANSI
- ASCII
- COLOR
- ICE
- RIP
- PETSCII
- SWAPDEL
- UTF8
- MOUSE
- UPAUSE
- SPIN
- PAUSESPIN
- EXPERT
- HOTKEYS
- MSGCLS
- REMSUBS
- FILEDESC
- FILEFLAG
- AUTOHANG
- AUTOLOGON
- QUIET
- ASKNSCAN
- ASKSSCAN
- ANFSCAN
- EDITOR
- SHELL

This should (at least mostly) address the issue #629

Apparently if you call mosquitto_publish_v5() with a non-NULL properties
pointer, it'll only publish via protocol v5 and doesn't work if you're using
protocol v3 connection.

Thanks Ree.

... regardless of the configured MQTT protocol version (v5 or v3.x).

Also include an MQTT v5 user-property ("time") with the message's origination
time/date stamp in ISO-8601 format in all log messages (to both topics).

This will at least double the amount of MQTT log traffic to the broker. When
MQTT v5 is used, the additional user-properties will increase it even a little
more.

Is this what you were suggesting Ree?

This should effectively turn script-terminating errors into just warnings and
thus at least working-around issue #397: the exceptions will be logged as
warnings intead of errors, but still logged.

The request from Nightfox and Accession via DOVE-Net was to be able to set
a user's external editor even if there's no user logged-in.

These 2 user class properties in the JS object model were a bit special in
that they *only* wrote to the user database and did not immediately modify
the in-memory copy of the user_t structure, depending on the re-reading of
the user.dat/tab file to re-populate the current user_t structure when needed.
This didn't work if the current user is user #0 (no user).

So, set the current user_t.xedit and user_t.shell accordingly whenever those
JS properties are assigned a value (a string, the appropriate internal code).

This should fix issue #626

The node message should be terminated with a newline character.

e.g.
$ echo "Hey you" | mosquitto_pub -s -t sbbs/VERT/node/1/msg

I'm considering the ability to send user message (telegrams) via MQTT too.

Add support for binary frames to websocket service

See merge request !330

Update node action display on web

See merge request !329

The reported issue didnt mention JSexec, but I assume that's what was meant
by "from the command line". (?)

I honestly forgot this script even existed. It's using the old deprecated
SMTP SOML command to send a telegram to a user. There are much better ways
to do that for the local system (e.g. calling system.put_telegram), but I
suspect this script existed since before the JS object model had support
for sending user telegrams.

Anyway, this was a simple change to fix issue #623, but really this
script should probably be rewritten or removed from the repo (we use
MSP for sending inter-BBS instant messages these days instead of SMTP/SOML).

sd_notify() is called from other threads (PIDs), so we've been getting
syslog warnings abouts this and I hadn't noticed:

systemd[1]: sbbs.service: Got notification message from PID 2555007, but reception only permitted for main PID which is currently not known

As pointed out by Accession (PHARCYDE) on DOVE-Net.

Just make the list argument a void* and assign to a void** local
var inside the function. No functional changes.

Fixes issue #621

Fix return value when p->peeked is true

See merge request !328

To be more consistent with the paste key behavior elsewhere in SCFG,
make the file options (Viewable Files, Testable Files, Download Events,
Extractable Files, Compressible Files, and Transfer Protocols) menus handle
paste (Ctrl-V, F6) key by inserting the copied or cut item above the current
selection rather than overwriting the current selection.

Fixes issue #616

Speed up file transfers.

See merge request !327

DDFileLister: Fix for the lightbar interface: When erasing the file info window, the file date is not shown on a duplicate line if the file date is already showing in the description area (i.e., for a 1-line file description). The veresion is now 2.14

See merge request !326

1. Resolve the "hidden symbol 'atexit' ... being referenced by DSO" error
   by using the -shared option (link against shared objects, not static libs)
2. The path to the xpdev output directory (where to find libxpdev.a) is just
   wrong. Hard-coded the machine architecuture portion (.x64) as a hack for
   now. Also, since this is use the LD macro, you need to pass "LD=gcc" on the
   make command-line. Not sure how this worked before.

Fixes (or at least works-around) issues reported by Ryan Fantus (1:218/820)

DDFileLister: Fix for the lightbar interface: When erasing the file info window, the file date is not shown on a duplicate line if the file date is already showing in the description area (i.e., for a 1-line file description). The veresion is now 2.14

Fixes issue #611

Fix for js.time_limit stuck at 0

See merge request !325

Fix timeout in mrc client and connector to avoid endless loop issue

See merge request !324

<nelgin> Remind me why you can't show the ip address on node status? :)

Using the new '-v[key]' option, a sysop can view one, some, or all of the
key/value pairs from the nodes with a connected client. For nodes without
a connected client, the client.ini file values aren't particularly useful, but
if someone wants an option to show those values for non-client-connected nodes
I can do that too.

When using '-v', all the client.ini key/value pairs will be displayed for all
the node records requested with currently connected clients. By specifying
'-v[key]' the sysop can specify a key to display (rather than all of them)
e.g. 'node list -vaddr' to list nodes with remote client IP addresses.
This option can be used multiple times on the command-line to view multiple
keys. See node*/client.ini for the list of supported keys.

This feature only works for nodes whose directory paths are ../node#/
relative to the ctrl directory. Since the node utility doesn't read any
configuration files, this is a limitation. If you have different node
directory names/parents and need to use this feature, let me know and I'll
see about adding support for reading/parsing main.ini file to discover those
non-standard/default node directory paths automatically.

The version number displayed is now taken from the sbbs version (sbbsdefs.h).
The maximum ctrl directory path is now extended from 40 chars to MAX_PATH.
More readable help/usage output (using indentation).

A follow-up to commit 81d4575e

Although I was not able to successfully reproduce the problem that Ree
reported with his commit (even when changing the SCFG->Networks->MQTT->Publish
QOS to 1: At least once) on Windows, I do see how this problem could
theoretically happen. And like Ree said in the follow-up comment on the MR
"maybe these two lines should have stayed in mqtt_startup", they don't really
belong in the connection callback.

The "client" topics only needs to be cleared upon startup or recycle (by
publishing a null message) and it would be bad to clear these topics whenever
the broker was reconnected (the server's clients didn't magically disconnect).
So these "client" topic-clearing publishes are now only done during startup
(again).

The "recycle" topics don't really need to be published to here at all. I
think I only did this for cases where someone published a non-null message to
the topic and its stale message would remain afterward, appearing in MQTT
browsers (like MQTT explorer) long after the server had recycled. The real
solution to this cosmetic issue is to only publish null (0-length) messages to
the "recycle" topics in the first place.

DDMsgReader: Bug fix for going to a specific message in the message list...

See merge request !323

Wasn't opening the sbbs.ini file for modify access.

As reported via DOVE-Net by Accession (PHARCYDE)

DDMsgReader: When saving a message on the local BBS PC without all the headers, the date is now included

See merge request !322

DDMsgReader: When saving a message on the local BBS PC without all the headers, the date is now included

DD Message Reader: Including all message headers when saving a message (sysop...

See merge request !319