LoginAttemptBanDuration value. Allows short-hand multipliers: YWDHMS
(year, week, day, hour, minute, second) and fractions (e.g. "2.5H").

disconnect them (with a message) and log a notice.

of parse_byte_count() and parse_duration()) and use them in ini_file.c

size_t.

address (family and address value, ignoring ports and other fields).

By default, after 20 consecutive (unique) failed login attempts, *or*
a failed login attempt wtih a name from the name.can filter file.
The default temporary ban duration is 10 minutes.
The temporary ban thershold is configurable via LoginAttemptTempBanThreshold
in sbbs.ini and the ban duration is configurable via LoginAttemptTempBanDuration
(in seconds).

prepend the text directory).

By default, after 20 consecutive (unique) failed login attempts, *or*
a failed login attempt wtih a name from the name.can filter file.
The default temporary ban duration is 10 minutes.
The temporary ban thershold is configurable via LoginAttemptTempBanThreshold
in sbbs.ini and the ban duration is configurable via LoginAttemptTempBanDuration
(in seconds).

instead of a string argument.  They perform the send/recv themselves using
a buffer.

This allows taking advantage of non-blocking sockets (in new Synchronet
builds) to be much more responsive.

This should still be compatible with the old socket.send implementation.
The *first* send it does in blocking mode and detects if it's the new or
old socket.send implementation and sets a global variable.  Future sends
know if it's the old or new API and treats them accordingly.

This may make new ircd running on an old build slightly less responsive
when a new user joins or when a new link is established since it blocks
all other ircd activity until the entire send queue has been transmitted (or
the connection is terminated).

calling Socket.bind() with an undefined hostname parameter would result in a
getaddrinfo() failure, e.g. on Windows, WSAHOST_NOT_FOUND 11001
The ircd.js passes the value of server.interface_ip_address to socket.bind()
and when run from jsexec, this property is not defined. So you couldn't run the
ircd from jsexec or you'd get "!Error 0 binding socket to TCP port xxx".
Also now setting the socket last_error value upon getaddrinfo() failure so
if there is a failure, the error message won't include the erroneous "Error 0".

Synchronet builds).  Use multiple send()s when needed.

correctly now though.

underlying send() function is free to send a subset of the bytes, and
occasionally does (especially on non-blocking sockets).  The return value
was true if all bytes were sent or false if not all bytes were sent.

The new behaviour is to return the number of bytes sent or null on failure.

This is mostly compatible with existing code which appears to universally use
if (!sock.send(str))

Cases where it's not compatible are when a zero-length string is sent.  The
handling of errors is slightly different now too... previously, if you
retransmitted on failure, the stream would "stutter" now it will have
"holes".

1) Don't use socket.recvline() on non-blocking sockets.  Instead, have
   the recvq object parse lines and receive 64k at a time.
2) Pass all received data through the recvq object rather than attempt
   to process one command per recv().
3) Pass all data sent on established connections through the sendq
   object rather than only use it if send() fails.
4) Move client throttling completely into ircd_user.js and out of
   the queue processing function so we don't accidentally throttle
   server connections.
5) send() the entire sendq contents as a single send() rather than one
   line per main loop.
6) Parse the entire recvq each time through the main loop.  This
   requires tracking when an unregistered connection is replaced by
   either a client or a server connection.

SlyEdit version 1.49 - Bug fix: Updated the command key help screen to use the standard Synchronet pause function at the end so that Synchronet can use a custom pause script if one is configured in text.dat.

Version 1.12: Updated the way the pause prompt is shown in the help screen, in case the sysop has configured an external module (Baja/JS) to run for a pause prompt.  Also made a potential bug fix: When translating a message number to a message index, added a check to ensure the value is a number, to (hopefully) avoid a potential crash.

StrictPacketPasswords (default is "true").
If you want SBBSecho v3 to behave like SBBSecho v2 with regards to packet
passwords for linked-nodes with *no* configured packet password, set this value
to "true" in your sbbsecho.ini file. I don't recommend doing this if you care
about the "security" of your echomail, but some sysops have been bitten by the
strict enforcement of the configured password in SBBSecho v3.

I also fixed some (but not all) of the signed/unsigned value comparison
warnings reported by msvc2013. Hopefully this didn't introduce any stupid bugs.

value (instead of the hard-coded 10) to limit the number of login prompts
displayed before disconnecting the user. A failed password attempt counts as
"2 prompts".

This has been broken (did not track consecutive failed login attempts from
the same client IP address) since the IPv6 commit of Aug-2015. I only noticed
this wasn't working when I was documenting the "auto-block hackers" feature
on the Wiki and noticed that every failed login (even those from the same IP)
was listed as a separate entry in the "Failed Logins" list (e.g.
sbbsctrl->View->Login Attempts). Ugh.

value (of "SYSOP") for the DefaultRecipient key. If it's blank (nobody)
just leave it blank.

(paraphrased) encountered when performing a echomail rescan for link(s):
When a packet reaches the configured "maximum packet size", finalize the
packet immediately (terminate the packet and close the file) rather than
waiting until the very end of all SBBSecho operations.

areafix responses to %LIST and %UNLINKED requests. If the same echo tag
was listed in multiple additional echolists, it was possible it would
appear multiple times in the areafix response list.

THIS MEANS THESE SCRIPTS CAN NO LONGER BE USED ON OLDER BUILDS OF SYNCHRONET

"Older" in this case means build from sources older than this commit.  You
must either use a nightly build from after this commit, or build it yourself,
or things won't work properly and you'll get errors.

YOU HAVE BEEN WARNED!

after the load(), throw an error.

load()s filename if propname is defined in scope (scope defaults to this.

Returns null if the file is not load()ed or the return value from load()
(last value of require()d file) if it is.

and exception.

blowing up unexpectedly because of load() or a global hotkey event.

still a bit better than the alternatives... the new sematics are:
load('require.js', typeof(argv)=='undefined'?'undefined':argv, 'sockdefs.js', 'SOCK_STREAM');

from binkp.js anymore.