According to  Lupine Furmen (FURFOL):
It says in the help that the field is used for both the Newsgroup name AND the
Fido Echo-tag.

These really should be 2 different fields.

Now, the echo/area tag is usually configured in the area file (areas.bbs) and so does not need to match *any* string configured in SCFG. But since an area file *can* be generated from SCFG (Export Areas option) and its possible to use SBBSecho withOUT an area file at all, then it's possible someone would like to have their FidoNet-style area tags configured different from any other strings related to a sub-board (e.g. newsgroup name) - why? I'm not clear, but there it is: another string that  a sysop can set (or not).

Since I'd recently added an area tag field per directory for use by hatchit.js, this does create some logical symmetry. And there were enough free bytes per-sub in the msgs.cnf, so why not.

Especially now that now all files even have descriptions (e.g. when super long filenames suffice).

Save the user's "misc" flags to the userbase when they use the 'T' command from the batch flagging prompt. Without this change, the option would automatically revert if/when the user record was re-read (which can happen at any time).

e.g. file.cpp line 239 (removefile) removing "filename.zip" access=-203 info=smb_freemsgdat reading allocation record at offset 1108

Also, if there is an error removing the original file from the filebase, don't proceed to move the actual file (and log a successful move).

Display the batch flag letter with the same color as the filename, but inverted intensity. The batch flag shouldn't stand-out (be bright) anyway, but the main reason is because I'm changing the default file description attribute to be lightgray instead of dark green.

CID 33567

CID 33320 and 333321

This looks like a 20-year-old copy/paste bug. CID 33168.

Fixes CID 33724.

Fixes CID 33498

This is pretty convenient and handy (rather than having to use &E or the equivalent command from the file xfer menu and then re-list files).

Fixes the link failure when sauce.o didn't need to be rebuilt.

Inspired by Blocktronics (and other ANSI art group) packs' FILE_ID.DIZ/ANS files:
* Support (and prioritize) FILE_ID.ANS
* Convert ANSI color/attribute sequences in DIZ files to Ctrl-A equivalent (uses SAUCE width and ICE color, if specified)
* Don't treat DIZ as a series of lines, they're not always nowadays.
* New putmsg() mode: P_INDENT to print files indented by current column
* Display full (up to 64-char) filenames in lists when using 132+ column terminal.
* Use the Author, Group, and Title fields from the SAUCE if present/non-blank
* 2 new text.dat strings: 301 (FiAuthor) and 302 (FiGroup)
* Also fix bug with repeated Cost header field on bulk-uploaded files.

I know this'll break the *nix build (sauce.c dependency), but I'll fix that next.

Also added -normal option to use save/normal/restore attr sequence for conditional-newlines. This is helpful for narrow ANSIs (e.g. 44-column FILE_ID.ANS) that depend on the viewer to read/use the SAUCE info.

"startup" was being deref'd after the caller free'd it because these thread functions were calling thread_down() before calling mail_close_socket(), which deref's startup which was subject to a race condition.

It Ctrl-A encodes a possibly ANSI-encoded string, supporting on color/attribute sequences and stripping all others.

This caused an issue for the soon to be committed P_INDENT support in putmsg().

To match the Remove file command sequence (for consistency).

This resolves errors when setting these properties to values > 2147483647
example:
!JavaScript  /sbbs/exec/load/sauce_lib.js line 69: Error: can't convert
2430770157 to an integer

That means you can now seek around (set position) within files > 2GB, truncate
or extend a file > 2GB, or set a file's date to > Jan-19-2038.

Increase total extended description length from 1024 to 4000 characters. Perhaps this should be configurable?

Log an info-level message instead.
Raise the log level severity of duplicate votes from Debug to Info too.

Extracting a file_id.diz would fail if the file contained any disallowed filenames before the DIZ, e.g.:
 Error: disallowed filename '_blockmen_res[v]olution.ans' (after extracting 0 items successfully)

This variable tracks the time that jsdoor was started.

There was a bug with reloading the configuration files in sbbsctrl where the sound button no longer reflected the truth and the sysop's previous click-state of the button was lost. Rather than going through writing the OPT_MUTE flag to the Options fields of all the sections of the sbbs.ini and then re-loading that file as a result, just do like we did with the sysop chat availability: use a semfile. So much simpler.

If anyone ever needs instance-specific muting, we can create/check instance/host-specific mute semfiles then. Doubt that'll happen though.

Also, removed the old sysavail control methods of ntsvcs too.

For files with names > 64 chars.