Stable release

v0.9.12aHandshake

Released 2026-09-27, 24.8 MB.

Notices

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

  • infoMessages already received keep trailing spaces that make the last word of a line wrap onto a line of its own at 80 columns, most of all in OTHERNETS, until they are rendered again. Run node src/tools/maintenance.js --regen-html with the worker running (add --area SHORTCODE to do one area first), even if you ran it after updating to 0.9.11a. It changes nothing but how stored messages are displayed.
  • infoQWK packets now live in one directory per link and role: qnet/<ID>.hub/ for a system that is your hub, qnet/<ID>.node/ for one that is your node. The update moves what is already in qnet/ and leaves qnet/<ID> as a link to the node directory, so a Synchronet node calling through qnet-directory.js keeps working. When you next change that node's call-out, point it at the qnet/<ID>.node path shown on its connection in the peer page.
  • warningA board with more than one QWK connection on the same network now passes messages between them: a message from one system goes to every other system on that network it has not already been through, as a Synchronet hub does. This is what a QWK hub needs, but if your board is a node of two hubs carrying the same conferences, each hub will now receive the other hub's messages. Check your QWK connections under Peers before updating.
  • infoYour board now relays QWK netmail for other systems on the same QWK network, as Synchronet does, and returns what it cannot deliver to its sender as BADADDR. To stop it, untick Relay QWK netmail on the network. Every decision is recorded in the Netmail Relay Log.
  • infoQWK IDs are now checked against Synchronet's rules. If any of your connections or networks use an ID Synchronet would not accept, or two connections share one, you get a notification after the update naming them. They keep working; see QWK IDs in docs/sysop/QWK_NETWORKING.md for what to change.

Canectic BBS v0.9.12a

QWK networking catches up with Synchronet: Canectic can be a QWK hub over the internet or FTP, routes and relays QWK netmail, carries files in packets, and exchanges UTF-8 correctly. Any board with a QWK connection should take this release.

Released 2026-09-26 (Handshake).

Highlights

Canectic can be a QWK hub. Nodes call it over HTTP, over FTP as they would a Synchronet hub, or collect from a shared directory, and a hub now passes messages between its nodes, which it never did before.

QWK netmail reaches systems you do not link with directly, and your board passes on netmail for others within the network it arrived on, as a Synchronet hub does. Private mail goes only to the system it is addressed to; before, with more than one QWK connection, most of it reached the wrong one.

Messages sent to Synchronet boards no longer arrive as one long line, and UTF-8 messages from Synchronet boards read correctly.

QWK packets carry files, in both directions. Links can exchange files as Synchronet always allowed, and a user's personal packet carries a new-files list, their download queue and their private mail attachments.

A QWK packet download that failed no longer loses its messages. They are marked read only once the download completes.

Saving a peer connection no longer resets it. NNTP groups started again from the first article, and QWK and NNTP polling intervals fell back to their defaults.

Old update backups are deleted, where every update kept a full database dump for ever.

Switch between stable and development from the Update page.

Much better on a phone: message lists, threads, file areas, private mail and message headers fit the screen, and messages are no longer double spaced.

Upgrading

From 0.9.11a the update applies itself. Worth knowing afterwards:

  • Regenerate stored messages again, even if you did so for 0.9.11a: node src/tools/maintenance.js --regen-html with the worker running (add --area SHORTCODE to try one area first). Messages received before updating keep trailing spaces that drop the last word of a line onto a line of its own at 80 columns until then.
  • QWK packet directories have moved to qnet/<ID>.hub/ for a system that is your hub and qnet/<ID>.node/ for one that is your node. The update moves what is there, packets waiting included, and leaves qnet/<ID> as a link to the node directory, so a node collecting with qnet-directory.js keeps working. When you next change that node's call-out, point it at the path shown on its connection in the peer page.
  • If you get a notification about QWK IDs, some of your connections or networks use an ID Synchronet would not accept, or two connections share one. They keep working; the notification says which to change. See "QWK IDs" in docs/sysop/QWK_NETWORKING.md.
  • Your board now relays QWK netmail for other systems on the same network, as Synchronet does. To stop it, untick Relay QWK netmail on the network. Every decision is in the Netmail Relay Log.
  • A board with several QWK connections on one network now passes messages between them. Messages from one system go to every other system on that network they have not already been through. That is what a hub needs, and it is how Synchronet behaves, but a board that is a node of two hubs carrying the same conferences will now send each the other's messages.
  • The QWK FTP hub is off until you turn on qwk_ftp_enabled and restart. It listens on port 8021 unless you set qwk_ftp_port.

Coming from 0.9.10a or earlier? The notes for the releases you skip apply to you too. The Update page lists every one that concerns your board before you update, and they are in the 0.9.11a release notes, https://canectic.tranqsoft.com/releases/0.9.11a/notes.

Changes

QWK networking

  • New: Canectic can be a QWK hub over the internet, and a QWK node of another Canectic board. Add a Hub (Inbound) connection for the node with a node password, and the node calls your board's web address with its QWK ID and that password, sending its replies and collecting its packet in one call. A packet counts as delivered only once the node confirms it has it, so a failed download loses nothing. A wrong password is logged to security.log for fail2ban. See docs/sysop/QWK_NETWORKING.md.
  • New: Canectic can be the FTP hub a Synchronet QWK node calls. With qwk_ftp_enabled on, a node using qnet-ftp.js (or other software that calls a hub over FTP) logs in with its QWK ID and node password and sends its REP and collects its packet as from a Synchronet hub. FTP does not encrypt the password, so for nodes on the internet the HTTP hub behind HTTPS is the safer choice.
  • New: a hub serves nodes that use a shared directory. Tick Node collects from a shared directory on the node's Hub (Inbound) connection, and every few minutes (qwk_hub_sweep_minutes, 5 by default) the board imports the REPs the node leaves in qnet/<NODE_ID>.node/in/ and builds its packet into out/. Before, the board built nothing for such a node.
  • Fix: a Canectic QWK hub did not pass messages between its nodes, so they only ever saw the hub's own users' messages, and a board that is a node of one system and a hub for others never passed its nodes' messages up. Messages now go to every system on the network except those they have already been through, with an @VIA line saying where they came from, as Synchronet writes it.
  • New: QWK netmail reaches systems you do not link with directly, and your board passes it on for others. The board learns how to reach each system from the mail that arrives (kept for 90 days) and sends by a direct link, a spelled-out path (HUBID/THEIRID) or a learned route. What cannot be passed on goes back to its sender as BADADDR:. Each QWK network has a Relay QWK netmail setting, on by default. The send form asks which network to use when a system is known on more than one, and replies go back the way the original came.
  • Fix: QWK private mail went out over whichever QWK connection sent first, so with more than one most of it reached the wrong system. It now goes only to the system in its address, and mail for a system you cannot reach returns to its sender as undeliverable.
  • Fix: QWK netmail for your own users went undeliverable when it arrived as user@YOURID or as NETMAIL with the address on the first line, the forms Synchronet uses. Undeliverable QWK private mail now records why.
  • Fix: a QWK node with no conferences subscribed never received private mail from a Canectic hub.
  • Fix: QWK messages sent from Canectic could arrive at a Synchronet board as one long line. The packet marked them UTF-8 while their text was CP437. The mark now matches the text, and UTF-8 messages from Synchronet boards, which were read as garbled text on one line, are read correctly.
  • New: QWK messages that do not fit CP437 go as UTF-8 instead of losing characters, on connections with Send UTF-8 when a message needs it ticked (the default). Messages that fit CP437 go as before.
  • New: QWK packets carry files, in both directions. Files you put in a link's out/files/ go with its next packet; files that arrive are kept, through your inbound wildcard rules or in the link's in/files/, with a notification for each. Before, a file sent in a QWK packet was deleted without a word.
  • Fix: messages in a REP that had to be retried reached the hub twice, private mail included. A REP that failed to upload is also retried at the next push even when there is nothing new, rather than waiting for a new message.
  • Each QWK link has its own packet directory, qnet/<ID>.hub/ or qnet/<ID>.node/. A system that was both your hub and your node used to share one, so a half-imported packet from one could be imported as the other's mail. The peer page shows each connection's directory.
  • QWK IDs follow Synchronet's rules: up to 8 characters, none of space \ / | < > * ? + [ ] : = " ; ,, stored in upper case, and each used once as your hub and once as your node. IDs that start with a digit or contain . or @ are accepted with a warning, since netmail cannot be addressed to them.
  • New: a QWK network can allow IDs of up to 32 characters, for networks where every system accepts them. Off by default, since Synchronet stops at 8.

Personal QWK packets

  • Fix: a QWK packet download that failed lost its messages. Downloading a personal packet from the web, the terminal or the API marked its messages and private mail read as soon as it was built, so an abandoned download left them out of the next packet. They are now marked once the download completes, as Synchronet does, and the same goes for files from the download queue.
  • New: personal packets carry files, as Synchronet's do: a list of new files (NEWFILES.DAT) in the areas the user scans for new files, the files in their download queue, and attachments to their private mail. From the reader, a message to SBBS with the subject FILES ON, FILES OFF, ATTACH ON, ATTACH OFF or FREQ <file name> switches the list or attachments, or asks for a file for the next packet, and a reply says what was done. The same switches are on the QWK page; both are on by default. The Download button no longer greys out when there are no new messages, since a packet can carry files alone.

Networking

  • Fix: saving a peer connection's settings made its next NNTP pull start every group again from the first article. The save discarded how far each NNTP group and QWK conference had been read, and for an FTN link the record of failed connects that holds off calls to a system that is down. Both are kept now; the failed-connect record is still cleared when you change the address the link calls.
  • Fix: saving a QWK or NNTP connection reset how often it polled to 2 hours (QWK) or 1 hour (NNTP) until the next restart. node src/tools/schedules.js also judged those schedules against the defaults rather than your setting.
  • Fix: the Force plaintext password box on an FTN connection could not be unticked.
  • Fix: a refused save on a network or peer page looked like it had worked. The reason is now shown at the top of the page, with any warnings.
  • New: a history of every QWK and NNTP transfer, under Networking > QWK and NNTP Transfers and on each connection of a peer's page: every pull and push, including ones that never reached the server, with what came of it, how long it took, how many messages moved and the error. The connection list shows when each last worked and, separately, when it last brought in mail, since a link can pull without error for weeks and bring nothing. Kept for network_transfer_retention_days (30).
  • Fix: a QWK or NNTP pull that failed was logged as though it had worked. It is now logged as a failure with its reason.
  • You are told when a connection's polling schedule is removed at startup, with the connection, its network and host, and why. Connections created before the Polling setting existed stopped collecting mail without a word when this happened in 0.9.6a; if that was not your intent, turn polling back on for the connection under Peers.
  • Fix: asking for the same job a second time often did nothing. Running --regen-html again, pressing a connection's pull or push button again, and repeat message ID repairs, file area scans and user maintenance runs were silently ignored for days after the first finished. A second request is still refused while the first is waiting or running.

Updates

  • New: switch between stable and development from the Update page. The Channel box switches and checks the new channel straight away. Switching to development asks you to confirm, after a warning that development builds get less testing and that there is no going back to the stable you run now. A development build moving to stable waits for the next stable release, and the page says so.
  • Fix: every update kept its backup for ever, database dump included, plus a staged copy of every release. A completed update now deletes older backups, keeping the last update_backup_keep (1, the update just finished; 0 keeps them all), and leftover staged releases. Nothing is deleted after a failed update. node src/tools/update.js --prune reclaims the space now; add --dry-run to see what it would remove.
  • Fix: an update started from 0.9.10a or earlier showed no upgrade notes, before or after. The new release's updater now fetches and verifies them itself, so they appear on the progress page and under the last update whichever release you came from.

Administration

  • Fix: changes made on the admin pages recorded nobody as having made them. Groups, areas, networks and peers now record the sysop who created or edited them, as do updates started from the Update page and closing or reopening the board. Records written before this release stay empty. A message posted from the admin message pages with From left blank is posted under your username.
  • Message group retention has its own Retention tab, as message areas and file groups do, rather than sitting among the Main settings.

Messages

  • Fix: messages looked double spaced in the web reader, worst at 80 columns on a phone. Lines now sit at the message's own spacing everywhere, so messages are noticeably more compact, and art too wide for the screen scrolls sideways rather than spilling out.
  • Fix: a word at the end of a line dropped onto a line of its own at 80 columns. Many systems pad each line with spaces to the full width; those spaces are now dropped. Messages received before updating need regenerating; see Upgrading.
  • Fix: the message and file area lists, the thread list, message headers and the file and group pages ran past the edge of a phone screen, so pages scrolled sideways, and a thread list showed its headings a letter at a time. On a phone each area, thread or file is now one entry with its details underneath, and a message's subject has a line of its own. Tablets and desktops keep the tables.
  • Fix: on a phone the last message in an area was often partly off the bottom of the screen. The list now fits the space left under the phone's address bar.

Private Mail

  • Fix: on a phone, opening a private message pushed Reply and Delete off the screen, and the bottom of the inbox was cut off. Both now fit.
  • Fix: the inbox, sent and trash lists were sorted by the attachment column instead of by date. They now start newest first.
  • Dates in the private mail lists are short on a phone ("Sep 25"), with the full time in the tooltip.
  • The standalone Sent and Trash pages are gone; /pm/sent and /pm/trash open those tabs of the inbox, so bookmarks still work.

Files

  • "New" files means new since your last visit, everywhere. A file is new if it arrived after your previous visit began, on the web and in the terminal alike, and stays new for the whole visit. On the web a visit begins at login or after web_idle_threshold minutes idle (120). The file lists, New Files page, call flow and terminal newscan now agree, where before each area kept its own marker that viewing moved along.
  • The terminal file browser's M (Mark Read) key is gone, since there is nothing left to mark.
Version
0.9.12a
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-text0008-qnet-role-dirs
SHA-256
e1f839faadf4ca76d3b5d458070907dd562da45616b66cde83b1ce611b9434e1
Files
metadata·manifest