Stable release

v0.9.9aHandshake

Released 2026-09-22, 24.0 MB.

Notices

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

  • infoFrom 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.9a

Replaces 0.9.8a, which is withdrawn because an update into it could stop partway if anyone had the board open in a web browser. Everything 0.9.8a and 0.9.7a brought is included.

Released 2026-09-22 (Handshake).

Highlights

0.9.8a is withdrawn, and this release replaces it. While the BBS is stopped, an update answers on the board's web port itself, and in 0.9.8a a browser tab trying to reconnect to the board could make the update stop in the middle, leaving the BBS stopped. An update always runs the updater of the release it installs, so the update into this release is not affected, from the Admin UI or from a shell. An update that fails for any other reason now records the step it stopped on and whether the BBS is down, instead of going on showing as running.

The Update page no longer offers the version you are running. It showed the result of the last check, made before your last update, until you pressed Check now.

Coming from 0.9.7a or earlier? This is the release that brings maintenance mode, updates that close the board and give callers notice, and an update progress page that keeps working while the BBS is stopped, all from 0.9.8a, along with everything in 0.9.7a. Read Upgrading before you update: the notes for both apply to you.

Also: the bootstrap will not install a withdrawn release.

Upgrading

  • 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

0.9.8a is withdrawn, so its upgrade notes belong to this release too.

  • 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. Every update after this one drains properly.
  • 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

0.9.7a was withdrawn as well, so its upgrade notes belong to this release too. Everything below happens on the first run after you update from 0.9.6a or earlier; a board already on 0.9.7a or 0.9.8a has been through it.

  • 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 now shows pending, sent and failed counts per connection.

Changes

Updates

  • Fix: an update could stop partway through if anyone had the board open in a web browser. While the BBS is stopped, the update answers on the board's web port itself, and a browser tab trying to reconnect to the board could make the update itself stop, in the middle, leaving the BBS stopped and the Update page still saying an update was running. Updates into 0.9.8a were affected. An update always runs the updater of the release it installs, so the update into this release is not.
  • An update that fails unexpectedly now says so. A visitor's browser dropping a connection is ignored and the update carries on; any other unexpected error is recorded against the step the update was on, with whether the BBS was left stopped, before the updater exits. The Update page and node src/tools/update.js --status then show it failed, where before a run that had died went on showing as running. Two quieter ways for an update to vanish without a record, both in how it starts itself, are closed as well.
  • Fix: the Update page offered the version you had just updated to. It showed the result of the last check, which ran before the update, until you pressed Check now. It now compares what that check found with what is running, and says when the check is older than the board. The update itself also refuses a release that is not newer than the one running, so a page left open cannot reinstall it, and node src/tools/update.js on a board that is up to date says so instead of reporting that it cannot move yet.

Installation

  • The bootstrap will not install a withdrawn release. Asked for one by name, it stops and says why the release was withdrawn and what replaces it. Left to choose, it takes the newest release that has not been withdrawn.

Changes in 0.9.8a

0.9.8a is withdrawn, so what it changed is listed here for boards coming from 0.9.7a or earlier. Its upgrade notes are under Upgrading above.

Maintenance Mode

  • New: close the board for maintenance, and know when it is safe to start. Admin > Maintenance, or node src/tools/maintenanceMode.js, closes the board to everyone but you for an import, work on areas, database work by hand, or anything else that needs it to itself. Callers and logged-in web users get a countdown and are then disconnected or shown a maintenance page; visitors see your reason and when you expect to be back; mail clients and binkp links are told to try later, so no mail is lost; the worker stops taking new jobs, which queue up for when you reopen. A drain table shows what each part of the board still has in flight, and says so when nothing is. --wait on the tool holds until then, for scripts. See docs/sysop/MAINTENANCE.md.
  • Follow an update from the web while the BBS is stopped. The Update button now takes you to a progress page that follows the update from start to finish, including the stretch where the BBS itself is stopped: the update answers on the board's web port in its place, showing the progress to the sysops who were logged in when it started and the maintenance page to everybody else. It uses the same port as the BBS, so it works behind a reverse proxy unchanged. See "Updating from the web" in docs/sysop/UPDATING.md.
  • Updates close the board themselves. An update warns callers and web users when it starts, waits until the board has drained before stopping it, and reopens it only once the update has checked every file it wrote. An update that fails after stopping the board leaves it closed, so nobody calls in while you find out what happened; reopen it from the Maintenance page when you are satisfied.

Updates

  • Fix: an update into 0.9.7a stopped at its schema step with spawnSync is not defined. By then the files had been replaced and the dependencies installed, which is past the point where an update puts the old files back, so the board was left on the new code over a database that had not been brought up to date. An update always runs the updater of the release it is installing, so the update into this release is not affected. See the upgrade note if your board is in that state.
  • A release can now be withdrawn after it is published, and the update check says so. A withdrawn release is no longer offered, and a board running one is told, with the reason, even before a replacement exists. This works from this release onwards: a board on 0.9.7a checks with 0.9.7a's code, which offers this release as an ordinary update without mentioning the withdrawal.
  • An installed board now keeps the signature of the release it runs (MANIFEST.asc) beside its MANIFEST. Installs never received it, so a board kept whatever it was first installed with, or nothing. Updating to an unsigned development build removes the old one rather than leaving a signature over the previous release in place.
  • Fix: every install and update reported failure at its very last step, after everything had worked. The last step checks that every file landed as released, and npm install, which runs just before it, rewrites package-lock.json as a matter of course. A fresh install was told it had not finished and that removing it and starting again was safe; an update was left closed for maintenance. The check now compares the lockfile by what it actually pins, which npm does not change, and names any file that genuinely did not land. If you installed 0.9.6a or 0.9.7a and saw "the install did not finish" at the verify step, your board was installed correctly.
  • update_require_signature now does what it says. It was read by nothing. An update now checks the release's signature against the release key your board already has before applying anything: a signature that fails is always refused, and with the setting on, so is an unsigned release (which includes every development build). See "Signatures" in docs/sysop/UPDATES.md.
  • Fix: an update started from the Admin UI stopped partway, leaving half the BBS stopped. The gateway and mail processes went down, the mailer and worker kept running, and the update itself disappeared at its "stop" step with nothing on the Update page to say why. The update was being stopped along with the BBS it was updating. It now takes itself out of the way first. Updates started from a shell were not affected. This fix travels with the new release's updater, so the update INTO this release already benefits from it, including from the Admin UI.

Security

  • The bootstrap now checks release signatures against the Canectic release key itself. It accepted a signature made by any key in your keyring. It now fetches the release key from the release directory, requires the signature to have been made by the key whose fingerprint is built into it and printed in the install guide, and stops before unpacking anything when a signature fails or comes from another key. Importing the key yourself is no longer needed.
  • Fix: web logins wrote passwords to the log. See the upgrade note above.

Networking

  • Fix: a binkp link connecting over WebSocket while your mailer was at its session limit received an empty busy message. The reason text was never copied into the frame. It now reads "System busy, try later", as it always did over TCP.
  • Fix: binkp sessions failed straight after logging in when a link presented more than one address and you had a connection for another of them with the same session password. Grouping those connections into one session, which is what the matching password is for, threw an error instead.
  • Fix: automatic echolist and filebone scanning failed for a network whose area held no archive to unpack. It logged that it was still looking for the lists, then threw instead of reporting what it had found.

Doors

  • Fix: a door using the canectic.sys drop file never started. Writing the drop file failed on the board name, so the door was never launched.

Administration

  • Fix: with no mail domain configured, the mail process restarted every few seconds until pm2 gave up on it, which read as a fault on every new board. It now waits quietly, and saving a mail domain in /admin/config starts the mail servers without a restart.
  • The Update page now counts terminal callers. It counted people on the web only, so a board with three callers in a door and nobody on the web told you nobody was online.
  • Errors in the web interface are now written to the system log. Before, a page that failed showed you an error page and recorded nothing, so if a save on an admin page did not take, the logs could not tell you whether it had failed or had never been sent. Each server error is now logged with the page it happened on and where in the code it was raised. Pages that simply do not exist (the steady stream of 404s from scanners probing for WordPress and the like) are deliberately not logged, so they cannot bury the errors that matter.

Release Archives

  • A release's FILE_ID.DIZ now describes the software and nothing else. It carried the first sentence of each upgrade warning, which is not what a BBS listing is for and not where a sysop reads them. Upgrade notes are in the release notes and the release's metadata.

Changes in 0.9.7a

0.9.7a is withdrawn, so what it changed is listed here for boards coming from 0.9.6a or earlier. Its upgrade notes are under Upgrading above.

Messages

  • Message bodies are now stored one way regardless of where they came from. Three importers had been storing text three different ways in the same two database columns, which is what allowed messages relayed between networks to be corrupted. An automatic migration rewrites the affected rows when you update: on the development board it touched 4,707 messages across 9 areas, all of them QWK-sourced. Nothing is asked of you and nothing needs checking afterwards. The older column is deliberately left in place for this release, unread, so the rewrite can be reversed if it ever needs to be.

  • Fix: messages received over NNTP displayed as mojibake on a UTF-8 terminal. The reader converted them a second time, from a character set they were never in.

  • Fix: messages relayed between networks were corrupted on the way out. The QWK packer decided how to read a stored message body from which database column was populated, and that test is only correct for messages that arrived over QWK. A message that came in over FTN and went out in a QWK packet had every extended character replaced with rubbish. NNTP had the same fault in a different form: outgoing articles declared no character set at all and were written in a way that discarded anything outside plain Latin-1, and incoming UTF-8 articles were stored mangled because they were never properly decoded. Outgoing NNTP articles now declare UTF-8, encode their headers correctly, and carry their text intact.

  • Fix: every message this system sent carried the wrong character encoding. FTN assumes CP437 unless a message says otherwise, and Canectic was writing UTF-8 bytes while saying nothing. Receivers followed the convention, decoded UTF-8 through the CP437 table, and got mojibake: a block of ANSI art becomes a wall of Γûê, an accented name comes out wrong, a subject line looks corrupted. It affected names, subjects and message bodies alike; art simply makes it obvious, being entirely extended characters. Outbound mail is now encoded properly and declares what it carries with a CHRS kludge.

  • Message areas have an Outbound Character Set setting, and message groups carry a default for it. Automatic (the default) sends CP437 whenever the message fits it, which is nearly all traffic, and switches to UTF-8 only for content CP437 cannot represent, where the alternative was replacing those characters with ?. An area can also be pinned to Always CP437 for an echo whose members run software that ignores charset declarations, or Always UTF-8 for a modern network that has agreed on it. Set it once on a group and every area created in it inherits it, with Push Group Defaults available for areas that already exist (unticked by default, since it replaces a per-area choice); an explicit choice on an area always wins. The setting is per area rather than per link because the encoding of an echo is something everyone carrying it agrees on, not a property of any one link.

  • Inbound messages are now decoded by what they declare rather than always as CP437, so mail from a system that correctly announces UTF-8 no longer arrives mangled. An undeclared message is still treated as CP437, which is the network default.

  • Fix: kludge lines were destroyed on every message this system relayed. Stored control lines were being read back in the wrong form, so each one was written out as undefined: with its name and contents gone. A single captured packet carried 772 of them across 157 messages. The visible effects were charset declarations vanishing (which is what made relayed art unreadable) and reply linkage being lost, so downstream systems could not thread the messages. Already-damaged lines are now discarded rather than passed on.

  • Fix: ANSI art drawn with block characters was flattened into a single line. Paragraph reflow joins consecutive lines that are close to the full width, which is how text from a wider editor gets reassembled, but every row of 78-to-80 column art looks exactly like that. Two faults combined: art detection only recognised art that moves the cursor, so art drawn as colour plus block characters read as ordinary text, and on the web the reflow ran before anything asked whether the body was art at all. Three rows of art became one line, and since the web copy of a message is rendered once when it arrives, nothing later could put the breaks back. Art detection now also recognises block-drawn art, and the web asks before it reflows rather than after, which is what the terminal already did.

    Fixing this does not repair messages already stored. Run node src/tools/maintenance.js --regen-html --area <SHORTCODE> on an affected area, and note that it can only recover art whose plain-text copy survived import intact.

    One deliberate trade: a message that is ordinary prose but carries two or more full-width rules now reads as art and will not be reflowed. Nothing about its shape distinguishes it from a drawing, and reflow was previously merging such a rule onto the end of the sentence above it, so leaving it alone is not obviously the worse outcome.

  • Thread mode can now be set on a message group. It was per area only, so a sysop wanting a whole network to read flat had to set every area by hand and set each new one again afterwards. The group carries a default that new areas inherit, an explicit choice on the area form still wins, and Push Group Defaults gained a Thread Mode tickbox for applying it to areas that already exist. It is unticked by default, like Retention, because pushing it replaces whatever each area was set to. Existing groups default to Standard, so nothing changes until you set one.

File Echoes

  • Fix: files received from an uplink were never passed on to your downlinks. A TIC file arriving from a peer was filed into the local area correctly and its outbound rows were written correctly, and then nothing ever staged them. The periodic outbound sweep, which is the safety net that catches whatever was not sent on demand, covered echomail, QWK, NNTP and email but had never included file echoes; and the inbound toss did not signal an outbound one the way the design had always described. The only things that actually staged a file echo were a local upload, the admin Trigger Event button and a manual toss, so a downlink received files only when somebody on your board happened to upload one. Nothing failed and nothing was logged. Inbound tossing now signals outbound immediately, and file echoes are part of the outbound sweep, so a board with no local uploads at all still feeds its downlinks.

  • Fix: a downlink's %RESCAN for a file area replied cheerfully and sent nothing. A file rescan writes pending rows rather than rewinding a pointer, so unlike a message rescan there is nothing that picks them up on the next pass. The admin Rescan button carried the same promise. Both now signal an outbound toss once the rows are written.

  • Fix: file echoes did not work in either direction in embedded mode (PROCESS_MODE=embedded). The embedded worker had no case for the TIC jobs, so BullMQ handed each one over, the switch fell through to its default, and the job was marked complete without the work being done. Outbound email and the outbound sweep were missing for the same reason. A test now holds the two workers to the same set of job names, since a job nothing handles is indistinguishable from one that succeeded.

  • Fix: nothing stopped a file echo circulating. A file that reads as new is imported and then hatched onward to every subscribed downlink, so in a mesh a file that is not recognised does not merely get stored twice, it goes round again and each system that fails to recognise it passes it on. Two brakes now exist where there was effectively one.

    The standard FTN guard was missing entirely: a TIC carries Seenby and Path, this system stamps itself into both on the way out, and nothing checked for its own address on the way back in. That check is now the first thing done, before the file is imported or forwarded, and it matches on the bare address so a chain that writes the address with a 5D domain on one hop and without it on the next is still recognised.

    The dupe check, which was the only brake, had a hole that defeated it exactly when it mattered. It compared filenames case-sensitively and required an exact match even when the checksum matched, so a file returning from a chain that had uppercased or renamed it read as a completely new file with an identical CRC. Filenames are now compared case-insensitively, and a file whose checksum and size both match one already held is recognised whatever it has been renamed to. Size is part of that comparison deliberately: a CRC-32 on its own is not enough to reject a file over, since across a large area the odds of some pair of unrelated files colliding are around one in a hundred.

    The two guards answer different questions and both are needed. The dupe check asks whether this area holds the file now, which retention can make false; the Seenby stamp asks whether the file has been through this system before, and travels with the file rather than living in a table that gets pruned.

  • Fix: a peer subscribed to a file area that is not carried on its network collected a dead delivery row for every file, for ever. The outbound pass needs an areatag to build a TIC descriptor and looks one up by the peer's network; with no mapping it marked the transfer failed, and a failed transfer was never retried by anything. Nothing filtered the subscriber list against that, so the rows piled up invisibly and one downlink simply never received anything from that area. Such a subscriber is now left out at the point the rows are created, on all three paths that create them (inbound tossing, web upload and terminal upload), and the mismatch is logged naming the peer, the area and the network so it can be fixed rather than silently skipped.

  • A peer's file echo delivery is now visible, and failures can be retried. The peer page shows pending, sent, failed and skipped counts per connection, lists the most recent failures with the file, area, reason and attempt count, and offers a Retry Failed button that re-queues them and runs an outbound toss. Previously a failed transfer was terminal and invisible: there was no page that showed one and nothing in the system that would try it again.

  • Fix: the command line tosser never moved file echoes. node src/tools/tosser.js --ftn enqueued the echomail and netmail jobs only, though the documentation listed it as one of the triggers for TIC processing. A sysop tossing by hand moved messages, moved no files, and was told nothing had gone wrong. --ftn now covers file echoes in both directions, as it always claimed to.

Security

  • adm-zip updated to 0.6.1, clearing two advisories against 0.6.0: extraction followed symlinks in the destination, allowing a crafted archive to overwrite files outside the target directory, and a declared uncompressed size could be used to exhaust memory. This matters here because both archive paths read files that arrive from outside the board: FILE_ID.DIZ extraction from uploaded and tossed files, and infopack scanning for echolists and filebones. The fix is a patch release inside the range already declared, so npm install picks it up with no configuration change.

Embedded Mode

  • Fix: the clean shutdown message never printed, and shutdown ended on an unhandled error instead. Both the gateway and the door server tested a bare logtoconsole when the last server stopped, but that name is a private constant inside the logger and was never in scope, so the check threw ReferenceError from inside a timer callback. The logger now exposes the setting properly.
  • Fix: an embedded board ran almost no maintenance at all. PROCESS_MODE=embedded starts the worker inside the gateway, and that in-process worker recognised 7 of the 33 maintenance jobs. Schedules are registered in both modes, so the other 26 fired on time, were handed over, matched nothing, and were marked complete. Nothing was logged at a normal log level and the queue diagnostics reported every scheduler healthy. In practice that meant no log or retention purges of any kind (bad echomail, inbound and outbound file logs, mailer sessions, notifications, relay log, tossed packets, update checks), no message or file retention limits, no periodic inbound scan, no timed events, no update check, no nodelist or echolist scanning, and admin buttons such as Rescan Area, Rethread and Batch Subscribe reporting success while doing nothing. Boards running the default four-process setup were unaffected. The maintenance jobs now live in one module both workers call, so the two cannot drift apart again, and a test holds them to the list of jobs anything can actually enqueue.

Files on the Web

  • Fix: viewing a file area did not clear its new-file badge. The area page advances your scan pointer to the newest file it listed, but it picked that file by comparing ids straight out of the database, and PostgreSQL returns them as text. After the first comparison the rest were being sorted as words rather than numbers, where "9" comes after "37", so the pointer was set to the lowest-numbered file on the page instead of the highest. Pointers only ever move forward, so the wrong value was discarded and the pointer simply stopped, leaving a count that nothing could clear. The same mistake made the terminal file browser stop marking files as new once you had opened one.
  • New files are now visible on the web, not just counted. /files has a New Files button showing the total across every area you are subscribed to, and /files/new lists those areas with a preview of what has arrived in each. Each file area has an All / New toggle, and new files are marked in the listing. The new-only listing shows the oldest unseen file first and walks forward on each visit, so a backlog larger than one page is worked through rather than skipped.
Version
0.9.9a
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-text
SHA-256
41600e1de08809fc6d088bf0139de8f5d927627d4dc8700611c6b2b45e127f1d
Files
metadata·manifest