Stable release

v0.9.10aHandshake

Released 2026-09-22, 24.1 MB.

Notices

Behaviour that changed underneath you. Nothing to run, but worth reading before you update.

  • infoComing from 0.9.8a: this is the first update that gives notice, so it takes longer: callers and logged-in web users get maintenance_grace_seconds (5 minutes unless changed) of warning before the BBS stops, and the update then waits for binkp sessions and jobs in progress to finish. Set a shorter grace on the Config page first if you would rather.
  • warningIf an update to 0.9.8a stopped partway (BBS stopped, board closed, the update log ending in "Unhandled 'error' event" and ECONNRESET), finish it before updating again: from the install directory run the steps it had not reached, in order, npm install --omit=dev, node src/tools/dbmigrations.js, pm2 start ecosystem.config.cjs, then node src/tools/maintenanceMode.js --off once the processes are up. Then update to this release.
  • warningComing from 0.9.7a or earlier: clear the gateway's pm2 output log (logs/production/gateway-out.log on a standard install) after updating. Every web login before 0.9.8a wrote the user's password to it in plain text; the logging is gone but the old lines are not.
  • infoComing from 0.9.7a or earlier: this update cannot warn your callers before it stops the BBS, because the processes it replaces predate maintenance mode; it carries on after about twenty seconds. If you start it from the web, you will see the maintenance page while the BBS is stopped; follow it with node src/tools/update.js --status or from the Update page afterwards.
  • warningIf an update to 0.9.7a failed at its schema step, finish it before updating again. That update stopped with "spawnSync is not defined" after it had replaced the files and installed the dependencies, then started the BBS again on 0.9.7a's code over a database that had not been brought up to date. Run node src/tools/dbmigrations.js in the install directory and restart the BBS, which completes what the update was doing, then update to this release as normal.
  • infoIf you installed 0.9.6a or 0.9.7a and were told "the install did not finish", your board is installed correctly. The final check misread a routine change npm install makes to package-lock.json as a file that had not landed. Nothing needs removing or redoing.
  • warningComing from 0.9.6a or earlier, embedded mode only (PROCESS_MODE=embedded): maintenance that has never run on your board starts running. An embedded worker recognised 7 of 33 maintenance jobs and silently completed the rest without doing them, so log purges, message and file retention, nodelist and echolist scanning, timed events and the update check have all been idle. They begin on the first daily run after you update, and clear the whole backlog at once. The part to check before updating is retention: if you ever set max_age_days or max_messages on a message or file area, it has been ignored until now and will be enforced on that first run. The Retention Preview on an area's admin page reports what a limit would remove without removing anything. Boards running the normal four-process setup are unaffected, because their worker has always run these.
  • warningComing from 0.9.6a or earlier, if you carry file echoes: expect a burst of outbound files on the first toss after updating. A file arriving from an uplink was correctly queued for your downlinks and then never sent, because nothing ran the outbound pass for file echoes. That queue has been growing for as long as you have been receiving files, so a downlink that has had nothing from you for months may receive a great deal at once. Nothing was lost and nothing needs doing; it is the volume that may surprise you and your links. To meter it, update at a quiet hour and watch the first pass on the peer page, which now shows pending, sent and failed counts per connection.
  • infoComing from 0.9.6a or earlier: this update rewrites stored message bodies. Three parts of the system had been storing text three different ways in the same database columns, which is what allowed relayed messages to be corrupted. The update normalises them automatically and asks nothing of you. On the development board that was 4,707 messages across 9 areas, all received over QWK; your figures will differ. The previous copy of every rewritten message is retained in the old column, unread, so the change is reversible. Messages already displaying incorrectly before this update are not repaired by it.

Canectic BBS v0.9.10a

Echomail you forward to your downlinks now leaves with its SEEN-BY and PATH complete and its author's timezone intact. Every board that feeds other systems should take this release.

Released 2026-09-22 (Handshake).

Highlights

Forwarded echomail no longer loses most of its SEEN-BY. A message usually arrives with several SEEN-BY lines, and only the last one was kept, so your downlinks were not told about most of the systems that already had the message. That is what SEEN-BY is for. Its PATH was also replaced with your address rather than having it added, so downlinks were told the message had come only from you. Both now go out complete, with your system added, written as several short lines the way other software writes them.

Forwarded messages keep their author's timezone. Every message you passed on carried your timezone in place of its author's, and posts made on your board carried a fixed -0600 whatever your timezone and whatever the time of year.

You are told when the release you are running is withdrawn. The update check now sends a notification, once, with the reason and the release to move to, rather than leaving it on the Update page for you to find.

Upgrading

From 0.9.9a there is nothing to do. The update applies itself, including a small database change for netmail, and asks nothing of you.

Messages you received before updating keep the SEEN-BY that was stored for them; everything tossed from now on is complete.

Coming from an earlier release? Your update skips 0.9.9a, so the upgrade notes it carried apply to you and are repeated below. Each says which boards it concerns.

Coming from 0.9.8a

  • This is the first update that gives notice, so it takes longer. Callers and logged-in web users are warned and given maintenance_grace_seconds (5 minutes unless you have changed it) before the BBS stops, and the update then waits for binkp sessions and jobs in progress to finish. Set a shorter grace on the Config page first if you would rather.
  • If an update to 0.9.8a stopped partway, finish it before updating again. The BBS is stopped, the board is closed for maintenance, and the update's log ends in Unhandled 'error' event and ECONNRESET, usually during the dependencies step. The files are 0.9.8a's; the steps after the one it stopped on did not run. From the install directory, run the ones it had not reached, in order: npm install --omit=dev, node src/tools/dbmigrations.js, pm2 start ecosystem.config.cjs, and once the processes are up, node src/tools/maintenanceMode.js --off to reopen the board. Then update to this release as normal.

Coming from 0.9.7a or earlier

  • WARNING: clear your gateway's log after updating. Until 0.9.8a, every login on the web wrote the user's name and password, in plain text, to the gateway's pm2 output log (logs/production/gateway-out.log on a standard install). The logging is gone, but the log still holds whatever was written before. Empty it or delete it once you have updated, and treat any copies or backups of it the same way.
  • This update cannot give your callers notice; later ones will. The processes this update replaces predate maintenance mode, so they cannot be asked to drain: after about twenty seconds the update carries on and stops the BBS as updates always have. Update at a quiet hour. For the same reason, if you start this update from the web, the progress page cannot recognise you while the BBS is stopped and you will see the maintenance page like everybody else; follow it from the Update page once the BBS is back, or with node src/tools/update.js --status.
  • If an update to 0.9.7a failed at its schema step, finish it before updating again. That update stopped with spawnSync is not defined after it had replaced the files and installed the dependencies, then started the BBS again on 0.9.7a's code over a database that had not been brought up to date. Run node src/tools/dbmigrations.js in the install directory and restart the BBS, which completes what the update was doing, then update to this release as normal.
  • If you installed 0.9.6a or 0.9.7a and were told "the install did not finish", your board is installed correctly. The final check misread a routine change npm install makes to package-lock.json as a file that had not landed. Nothing needs removing or redoing.

Coming from 0.9.6a or earlier

Everything below happens on the first run after you update.

  • Embedded mode only (PROCESS_MODE=embedded): maintenance that has never run starts running. The embedded worker recognised 7 of 33 maintenance jobs and silently completed the rest without doing them, so log purges, message and file retention, nodelist and echolist scanning, timed events and the update check have all been idle. They begin on the first daily run after you update, and clear the whole backlog at once. The part to check before updating is retention: if you ever set max_age_days or max_messages on a message or file area, it has been ignored until now and will be enforced on that first run. The Retention Preview on an area's admin page reports what a limit would remove without removing anything. Boards on the normal four-process setup are unaffected, because their worker has always run these.
  • This update rewrites stored message bodies. Three parts of the system had been storing text three different ways in the same database columns, which is what allowed relayed messages to be corrupted. The update normalises them, automatically, asking nothing of you. On the development board that was 4,707 messages across 9 areas, all received over QWK; your figures will differ. The previous copy of every rewritten message is retained in the old column, unread, so the change is reversible. Messages already displaying incorrectly before this update are not repaired by it.
  • If you carry file echoes, expect a burst of outbound files on the first toss after updating. A file arriving from an uplink was correctly queued for your downlinks and then never sent, because nothing ran the outbound pass for file echoes. That queue has been growing for as long as you have been receiving files, so a downlink that has had nothing from you for months may receive a great deal at once. Nothing was lost and nothing needs doing; it is the volume that may surprise you and your links. To meter it, update at a quiet hour and watch the first pass on the peer page, which shows pending, sent and failed counts per connection.

What those releases changed is in the 0.9.9a release notes, https://canectic.tranqsoft.com/releases/0.9.9a/notes, which also cover 0.9.8a and 0.9.7a.

Changes

Networking

  • Fix: echomail forwarded to your downlinks lost most of its SEEN-BY. A message usually carries several SEEN-BY lines, and only the last one was kept, so downlinks were not told about most of the systems that already had the message, and could pass it to a system that already had it. Every line is now kept, your system is added, and the list goes out as several short lines, as other software writes it.
  • Fix: forwarded echomail told downlinks it had come only from you. Its PATH was replaced with your address instead of having it added, and the original PATH was sent as well, at the top of the message where software reading the last PATH line ignored it.
  • Fix: every message you forwarded carried your timezone instead of its author's, and posts made on the board carried a fixed -0600 whatever your timezone and whatever the time of year. The author's timezone now passes through untouched, and posts made here carry your system's real offset for the date.
  • Fix: forwarded echomail gained a second tear line after its Origin line, which showed as a stray --- at the end of the message on every system downstream.
  • Your tosser now names itself with its real version in the TID line, where it said Canectic Tosser v0.1.

Updates

  • The update check notifies you when the release you are running has been withdrawn, once per release, with the reason and what to move to. The Update page says so too, at the top. Before, nothing showed it, and a board on a pulled release looked exactly like one that was up to date.
  • Fix: a withdrawn release could name a replacement that had been withdrawn too. 0.9.7a names 0.9.8a, which was withdrawn two days later, so a board on 0.9.7a was told to move to a release it would be refused. The Update page, the notification, the update tool and the bootstrap now name the newest release still listed.
  • An update now tells you about a one-off repair it left for you. A few database repairs are too slow to run without asking, so the update reports them and leaves them to you, and until now that report was only in the update's log: an update could say COMPLETE with one still waiting. It is now a warning on the run, shown on the Update page and by node src/tools/update.js --status, with the commands to run. The one boards set up before this spring are most likely to see is the MSGID split: node src/tools/maintenance.js --fix-msgids --dry-run to see what it would change, then without --dry-run to do it.
  • Fix: an update on a board installed before releases carried a MANIFEST warned that "every changed data file was kept as yours" when none had been. It now says so only when a data file really was kept, with how many; each one is also named, as before.
Version
0.9.10a
Channel
Stable
Node
22.0.0 or later
Upgrades from
0.9.0a or later
Migrations
0001-menu-layout0002-msgid-tuple-split0003-qwk-conference-blocks0004-settings-provenance0005-refresh-stale-version0006-normalise-body-text0007-netmail-seenby-text
SHA-256
887f27ecfba8e94b02b0ce01e1548f79b994ec62be23c20589643d2488ceb8f2
Files
metadata·manifest