Synchronet's whims. Check for falsiness instead of NET_NONE.

Just display to/from_net_addr without prefixing with to + @. Not
sure why I was doing this, but if there was a reason, I'll need
to make an per-net-type address formatting thing.

Mail wasn't being marked as read unless the user hit 'Q' from the msg view mode.
Reported by Keyop via IRC.

'darkmode_off' will still work if set, but is deprecated.
Added 'darkmode_on' setting, which defaults to false;
if set, darkmode is turned on until the user turns it off.

If your browser is from another geological epoch, I have no sympathy for you.

Previously, 403 was only returned if they existed, and 404 if they
didn't.

No need to get time() here since it's never checked.

Resolves CID 174292

Have free_paragraphs() explicitly allow paragraphs to be NULL and
have everything use the fail_return which now free()s ret.

Previously, more than 999 arguments would overrun a buffer and break
things.

Fixes CID 33313

Are you tired of getting TLS-related error log messages that you can't do anything about? e.g.
web  0139 TLS ERROR 'Received TLS alert message: Unexpected message' (-15) setting session active

The new sbbs.ini [web] TLSErrorLevel option (defaults to 0 / "Emergency") allows the sysop to set a cap (maximum severity) on TLS-related log messages in the web server (e.g. TLSErrorLevel=Warning).

x points to the terminating NUL in x64.  free()ing it would do wild
and crazy things depending on how paranoid the free() implementation
is.

free(x64) instead... at least Coverity was happy though!

The socket set allocated by xpms_create() was never freed. Found by Coverity.

Deuce said to just delete it. <shrug>

I'm not sure what echicken was trying here, but apparently it doesn't
work for nelgin.

Likely fixes #220.

I'm not sure what echicken was trying here, but apparently it doesn't
work for nelgin.

Likely fixes #220.

3rd party external doors - exitilus, jibben, jns

See merge request !110

3rd party external doors - exitilus, jibben, jns

See merge request !110

... instead of the JSON parse exception as reported via IRC:
<matjam> !finger ?bbs:Stupendous BBS@vert.synchro.net result: SyntaxError: JSON.parse