"Application" is not a registered category.
Add TerminalEmulator and Dialup categories.

  I think that > 1MB post data is supported, but the http_request.post_data
  property won't be created if the length > MAX_POST_LEN. Perhaps would just
  store the post data in a file (uh, it already is?) and expose the filename to
  JS scripts? It'd be a lot cleaner than storing the data in a file and then
  reading (or mem-mapping) the file and then copying the contents into a JS
  property.

Allow the JS http_request.post_data property to contain NULs.

open_post_file() will now open the post file (and return the FILE*) even if
  session->req.post_data is NULL, it just won't try to write to the file if the
  post_data is NULL.

mem-map the large post data files using XPMAP_WRITE (read/write) rather than
  XPMAP_READ (read-only) - without this change, this line in read_post_data()
  would cause an exception:
    session->req.post_data[session->req.post_len]=0;
  Now, we seem to have the potential of an off-by-one here (if the length
  mem-mapped is not post_len + 1), but that isn't happening. <shrug>

Fixed a couple of FILE pointer/descriptor leaks if post_to_file() failed.

Changed name of post data file to SBBS_POST.*.*.data (it's not necessarily
html).

So now, uploads > 1MB work, but questions remain:
- wouldn't PUT be a more appropriate method (than POST) for file uploads?
- how can we support post_data > MAX_POST_LEN (now 4MB) in JS?

(don't pass a NULL pointer to fwrite() which can assert or crash).

sub-board (if there was one) which pointed to the cut-sub.

(or deleted) or a group of sub-boards was deleted, and any of the deleted/cut
sub-boards belonged to a configured QWKnet hub, that QWKnet sub-board would
end-up pointing to the next sub-board in the configuration (possibly in another
message group, possibly not part of the QWKnet in question). Now, if a
QWKnet sub is deleted/cut, remove it (correctly) from any QWKnet hubs using
a common (new) function: remove_sub(). The bug was: the remaining sub-board
pointers were moved *before* the remove-sub pointer was compared against the
list of QWKnet hub subs (and NULLed), so while the effort *was* made to address
this problem, it didn't actually work in practice. Thanks for the bug report.

rather than word-wrapped lines, leaving it to the things that display messages
to perform any line-wrapping as needed.

If you want/need the old behavior, set soft_cr=true in the [fseditor] section
of your ctrl/modopts.ini file (new feature/section).

not defined" exception, just report the load() exception - whatever it was
(e.g. could not open load-file).

sbbs_t::automsg()

- 'outbox' value from echocfg/sbbsecho.ini is used for additional outbound
   files
- normal BSO directories are still searched for outbound files (too)
- 'inbox' support not added (yet)
- no node locking (.bsy file checking/creation) implemented
- requires updated load/fidocfg.js

BinkITCfg.node[] objects.

check api result for success (200) response. use var instead of const for openweathermap instance (to accomodate ircbot "reload" command)

added max_paragraph_length and max_paragraphs settings. split client output at max_paragraph_length and allow sending in chunks x max_paragraphs.

<Deuce> Yes.
<mcmlxxix> :|
<mcmlxxix> you took that as an or statement
<mcmlxxix> i hate you so much sometimes

Renamed the menuTitle property to topBorderText.  Added a bottomBorderText property, for text to be displayed in the bottom border.

Version 1.22: If the message score is 0, with upvotes and total_votes both 0, then don't show the score when using the default header ANSI.  This is what was intended, but the 0 score started showing up in more recent builds of Synchronet.

Fixed a bug that somehow crept in: Tthe check mark for selections in multi-select mode was being displayed in the wrong place when using a menu border.

Now supports a title in the top border line: Added a new property for the DDLightbarMenu object, menuTitle, which is a string that specifies the title text to write in the top border (if the border is being displayed).  It defaults to an empty string (for no title).  Synchronet attribute codes are supported.

smb_freemsgmem():
bounce() is using a strange method of copying a message header in memory
(not using smb_copymsgmem) and when it frees the message, ends up with a
double-free of the 2 new smbmsg_t members (not header fields): text_subtype
and text_charset.

Send failure emails with high-prioirty.
Use require() instead of load().

enable bright-background support (and disable blink).
Use require() instead of load(), where applicable.

- P_NOERROR
- P_PETSCII
- P_WRAP

bright-background (iCE color) support in SyncTERM/CTerm ANSI terminals.

- PetTerminalDetected (renamed from PetTermDetected)
- PetTerminalQ
- TerminalAutoDetect
- TerminalColumns
- TerminalRows
- TerminalMonochrome
- TerminalColor
- TerminalIceColor
- IceColorTerminalQ
This also moved the MsgCarbonCopyList definition to the end of the file

on PETSCII terminals.

Replaced embedded ^A chars with \x01.
Use bright-background (\x01e) for selected answer, much more readable on
PETSCII terminals.

New text.dat strings:
- PetTerminalDetected (renamed from PetTermDetected)
- PetTerminalQ
- TerminalAutoDetect
- TerminalColumns
- TerminalRows
- TerminalMonochrome
- TerminalColor
- TerminalIceColor
- IceColorTerminalQ
This also moved the MsgCarbonCopyList definition to the end of the file
for now.

- for PETSCII, this is automatic and you don't lose blink, but you do lose
  colored foreground when enabling a bright background ("reverse video")
- for ANSI, this mode is typically referred to as "iCE colors" and disables
  blinking-text support
- Ctrl-AE (^AE) is the new attribute code to enable bright-background
  (will have no effect on ANSI terminals that are not iCE color enabled)
  "E" is now valid in the ctrl/attr.cfg file and string values for JS
  console.attributes assignments, as well
- Ctrl-AI (^AI) - blink - now does nothing for ANSI/ICE color terminals
  (blinking is not supported in combination with bright-background)
- Using a new/non-standard CGA attribute bit-flag to indicate the selection of
  bright-background colors (BG_BRIGHT, bit 10), separate from BLINK.
  This change required all/most char/uchar attribute representations to be
  converted to int/uint.

New text.dat strings:
- PetTerminalDetected (renamed from PetTermDetected)
- PetTerminalQ
- TerminalAutoDetect
- TerminalColumns
- TerminalRows
- TerminalMonochrome
- TerminalColor
- TerminalIceColor
- IceColorTerminalQ
This also moved the MsgCarbonCopyList definition to the end of the file
for now.

PETSCII reverse-video attribute fix:
When a CR is sent to the terminal, the reverse-video attibute is auto-disabled
so update our "current attribute" (curatr) value to match the remote.

Support new printfile/putmsg mode flag: P_WRAP to force an ungraceful
line-wrap (splitting) to the specified column width. If no column width is
specified (0), then this mode will force an ungraceful wrap before the last
terminal column where some terminals *may* auto-wrap.

JS console.printfile() and printtail() methods now support an optional
"orig_columns" argument, similar to console.putmsg(). Must specify P_WORDWRAP
or P_WRAP for this argument to have any effect.

Much improved terminal-type selection/configuration in the user defaults
menu and abort (^C) at any of the yes/no prompts is now detected/handled much
better (to answers to the prompted questions are not saved to the user
settings).