Most DOVE-Net subs were already configured this way, but not all.

With this change, it's important you don't try to use a newer text.dat with an
older sbbs (and perform a ;UPLOAD sysop operation).

Previously, each file's size in (k)ibibytes was displayed, which is not very
modern of us. Use the byte estimate (e.g. "1.2M") strings intead.

Because we can. :-)

Also updated some durations, lowercase unit designator, and added some
more server section comments.

whitespace changes, durations (e.g. for timeouts)

And added the other new strings.

Of course, I'm just guessing using DDG Translate, I don't actually speak
these languages with any fluency, so I could use help from those that do.

These files aren't directly used by anything yet. One could copy or symlink
them to ctrl/text.ini or dynamically load them for certain users (right now,
that'd be done via JS).

Mark them all "UNUSED"

The InactivityAlert string is sent as a warning before disconnect when a
visible alert (AreYouThere) shouldn't be sent. Defaults to 3 beeps.

Remove the content of the NodeActionMultiChat (over-rides the hard-coded
default node status) - weird that this was the only node status that reported
the user's security level in the default configuration. This has been this
way since sbbs v2.30, at least. I think it was to be sure that others could
see the age/gender of those they were chatting with. But we have other methods
of reporting that in node status now, so we don't need to use this override
string to accomplish that.

I don't think it would've even been possible to match these expressions without
the tilde.

Not sure who mispelled Synchronet in here. That's embarassing.

- New keys in [BBS] section of sbbs.ini:
  MaxLoginInactivity (default: 10 minutes)
  MaxNewUserInactivity (default: 60 minutes)
  MaxSessionInactivity (default: none/unlimited)
- Each configured external program/door in SCFG can have its own maximum inactivity setting (or else the session max inactivity is applied)
- moved node-specific sec_hangup to system-wide/shared max_getkey_inactivity (configured in SCFG->System->Advanced)
- moved node-specific sec_warn (seconds of inactivity before sending warning) to inactivity_warn (a percentage of elapsed max inactivity before sending warning), also configured in SCFG->System->Advanced and used for both socket and getkey inactivity detection
- Renamed JS console.inactivity_hangup to console.max_getkey_inactivity (old name remains as alias)
- Renamed JS console.timeout to console.last_getkey_activity (old name remains as alias)
- Removed JS console.inactivity_warning
- Added JS console.max_socket_inactivity (current input_thread inactivity threshold)
- New text.dat string: InactivityAlert (just contains 3 ^G/BELLs by default) used for non-visual inactive-user warning

The MaxLoginInactivity setting in particular solves the problem of custom scripts (e.g. animated pause prompts) that just poll indefinitely for user input and never time-out  - these will no longer cause nodes to be tied-up with inactive/bot users at login.

You may ask yourself, how did I get here? No, you may ask yourself: why configure these socket inactivity max values in sbbs.ini? The reason is consistency: sbbs.ini is where the MaxInactivity is configured for all the other TCP servers and services.

This fixes issue #534 for Krueger in #synchronet

This fixes issue #62

Reversed the order of the pwmod date and the password itself.
The number of chars of the user's password displayed depends on the
terminal width. e.g. on an 80 column terminal, 18 chars will be
displayed. If the user's password is longer than what can be displayed,
this is indicated with a trailing "..". Wider displays (e.g. 132 column)
can display all 40 chars of a user's password.

This fixes issue #442

When passwords aren't displayed (due to sysop configuration), show
"<hidden>" instead of "XXXXXXXX" to make that more clear.

They were too hard for me to read before, being all high intensity.

Include some other new key values (migrated from node.ini)

Move the pack and unpack commands to an "Advanced" sub-menu since they
are completely optional now.

Set QWKhub 'VERT' to disabled by default in a new install.

Fixes issue #506

Non-root users don't have write access to /var/run by default,
so don't use that as the default location of the pid file.

This fixes issue #516

When changes are made using SCFG on these files, a 'git diff' is now helpful and readable to
see what changed.

The order of sections and keys change as a result.

Some extraneous stuff created by upgrade_to_v320.js was removed and some numeric values change
from hex to decimal encoding.

Following the (now proper) naming introduced in commit 8e6ebec3

Resulted from upgrade_to_v320.js typo

New (optional) keys in ctrl/sbbs.ini (with defaults):
[BBS]
DefaultTermWidth=80
DefaultTermHeight=24

This fixes issue (feature request) #491

The MSS detection will set this to the best value on a per-connection
basis.  This will allow larger packets to be sent from the BBS.