array. These correlate with the lines in ctrl/attr.cfg and are used for
setting console attributes in places where text.dat strings perhaps didn't
make sense. These values are used like this (e.g. to set the current
console attributes configured for filenaems):
	console.attributes = console.color_list[ATTR_FILENAME];

("sysop" and "The Guru") - fixing the simple node listing apps, like the
echicken web UI.
If your node lister wants to do something more fancy (e.g. display the name
of the sysop or the guru engine), you'll have to handle that yourself.

NodeConnection[] // lowercase
NodeConnectionProper[] // propercase

If the node.connection value is in these "arrays", use that value to print
node's connection type/protocol. If it's not, it's a modem connection and
the node.connection value is the DCE rate (in bps).

WITH_SDL are not defined. This should fix JSDCOS builds for those without
libsdl1.2-dev installed - but really, you want SDL installed to get the
full docs, I think.

warning: ISO C++ forbids converting a string constant to 'char*'
and comparision between signed/unsigned int.
This does *not* address the reported build issue:
In function `_start':
(.text+0x20): undefined reference to `main'

Added support for optional modopts.ini [xtrn_sec] keys:
- eval_before_exec
- eval_after_exec
These may be set to JavaScript expressions to be evaluated (executed)
before and/or after any program is executed from this module.
Also fixed a bug where a door-custom font may not be loaded if the door
was the only one available in a section.

this should fix the missing/misaligned 'bbs' property descriptions in
jsobjs.html

TypeError: bp.remote_addrs is undefined

in callout stats (stored in binkstats.ini).

.connect_host
.connect_port
.connect_error
Allows the application (binkit.js) to log detailed BinkP.connect() failures.

when a host-name lookup (getaddrinfo call) failed.

ctrl_a_to_mirc(str) returns converted str.

Creates/updates a data/binkstats.ini file which tracks BinkIT/BinkP session
statistics:
- inbound successes/failures (per node)
- callout successes/failures (per node)
- totals (per node)

It's a human-readable data file (in .ini file format), so it's pretty
self-explanatory.
The [callout success: <address>] sections provide details about the last
successful outbound BinkP session with the specified node.
Similarly, the [callout failure: <address>] sections provide details about the
last *failed* outbound BinkP session with the specified node.
And there are very similar sections for successful and failed *inbound*
sessions as well.
The [totals: <address>] sections track running totals for each node as well.

.remote_operator (the value of the 'ZYZ' message, if received)
.remote_capabilities (the value of the 'NDL' message, if received)
.remote_info[], an associative array of any/all *other* M_NUL BinkP
 commands/messages (e.g. bp.remote_info['TIME'] contains the remote TIME
 message arguments, if such a message was received).

Use 'dt' value of API response to determine whether to update cache, rather than time since last fetch.  New data may appear sooner.

Output needs some prettying up.
You gots to get you an OpenWeatherMap API key to use this mkay?
RIP in peace, Weather Underground.

Instead of one large cache file, one file per endpoint + param set.

Cache and rate limiting is useless right now unless calling script is long-lived.

system for v3.17b on Jan-2-2019.

- Enabling JavaScript "strict" mode and resolved the resulting errors
  (mostly in Merlin's "findfile" modification)
- Enabled the use of a [fingerservice] section in ctrl/modopts.ini:
  include_age_gender (default is true)
  include_read_name (default is true)
  findfile (default is true)
  bbslist (default is false)
- New optional "?bbslist" query to return the names in the local sbbslist.json
  Also "?bbs:<name>" to return the JSON representation of a specific BBS entry
- Work-around xtrn_area.prog[] bug where array items could be a non-object
  (e.g. just 'true' in this case) if the user (no user in this case) did not
  meet the configured access requirements for the external program in question
  so the action value in the node/active-user reports would say
  "running undefined" - just display the internal code instead of the full
  name if this the xtrn_area.prog[code] is undefined (bug fixed in v3.17c).
- The ?active-users.json response now includes the numeric node 'action'
  value (for possibly localization in the future), the 'xtrn' name, when
  appropriate, and the current node.aux value. These fields are not currently
  used by the client (sbbsimsg*.js), but may in the future, mainly for
  localization/translation or beautification purposes.

if the current user did not meet the access requirements, the corresponding
element if these associative arrays would be a random JS value, not the
actual program/section object.

(i.e. *nix) - I guess nobody really uses this utility.
Incremented version to 1.02.

<useron alias>, so we need to include it in the log message here if we
want the current user's alias included in event related log messages
(e.g. unpacking QWK-REP packages).

error messages.

251 response which was made optional in RFC2821 - to address privacy
concerns.

Removed the 'beta' status from the version to (1.17), now that Synchronet 3.17b has been officially released.