Repository navigation
Releases
Nunki 0.7.0
Published as a pre-release: a work in progress for the Raspberry Pi image. 0.6.0 was never published, so its notes (below) arrive with this one.
-
[Feature] Two hall screens, each with a mind of its own.
/hallis Screen 1 and/hall?screen=hdmi2is Screen 2, for a box with two monitors. Each can be Live (what it always did), Paused (it keeps showing what it showed, clock and all, while the hall moves on; Nunki keeps talking) or Black (nothing, not even a cursor - for the prize-giving, or for the hour in which nobody needs to be told the pairings again). Each can also be told which tournament to show, instead of guessing. All of it survives a restart, and an open screen follows a change at once.?t=still overrules everything, for whoever opens a screen by hand. -
[Feature] The control page grew up into a management display. The two screens sit side by side at the top with their three buttons, a small preview of what each shows, the tournament picker and a link to open it; on a wide monitor the rest of the page splits into two columns. Everything is big enough to hit with a finger. "Identify the screens" puts a 1 and a 2 the size of the monitor on each for five seconds, which settles the question of which cable went where faster than following it behind the desk.
-
[Feature] A sound switch. Off means nothing is said - not queued, not saved up for a dramatic reading later. The control page says so in red, the screens go on showing everything, and the "line being said" at the bottom of the hall screen stays away, since there is no line.
NUNKI_AUDIO=offmakes a fresh install start silent; it is only the default, and the switch wins once somebody touches it. -
[Feature] A local control API,
/api/local/v1, for programs on the same machine - the touch menu of the Raspberry Pi image, mainly.GET /state, andPOSTto/screen,/audio,/hall_tournament,/identifyand/stop, JSON both ways; the contract is docs/local-api.md. It answers loopback only, whatever the PIN andNUNKI_LISTENsay, and refuses anything a proxy passed on (tailscale serveincluded) or a web page sent. Bad input gets a 422 and a sentence, not a shrug. -
[Change] Nunki answers to its own Tailscale name. With
NUNKI_LISTEN=lanit asks the local Tailscale daemon, every fifteen seconds, what this machine is called on the tailnet and which addresses it has there, so a page opened ashttp://hall-pi.<tailnet>.ts.net:4062works even when Tailscale came up after Nunki. Only this machine's own name: "anything under ts.net" would have been a lovely gift to anybody doing DNS rebinding. The PIN still applies to everyone who is not this machine. -
[Change] After the PIN, a hall screen opened as
/hall?screen=hdmi2(with or withoutt=) goes back to that address instead of forgetting which screen it was. -
[Fix] One phone can no longer lock every other browser out of the PIN door. The box-wide cap of forty wrong guesses a minute stays, but once it is reached an address that has not failed yet still gets two tries of its own, and a right PIN gives back its own failure to the count instead of whichever one shared its second.
-
[Fix] "Remove" no longer claims OpenPairings is told when the line is down. The confirmation says when it will not be, and afterwards the page says OpenPairings was not told and that the device has to be removed there too. With the line up nothing changes.
-
[Fix] The plug-in says 0.6.0. It said 0.3.0 while speaking announcements and rooms, so OpenPairings' plug-in list was out of date; a test now holds it to the program's own version.
-
[Fix] The installer shows the PIN, and says that there is one.
install.sh --lanis for a box without a screen, the PIN was only ever shown on a screen, and the installer cheerfully ended with "no PIN", which made the first visit from the arbiter's laptop a short and unrewarding one. The installer now prints the PIN when it is done (it is in/var/lib/nunki/access-pinfor root to read, so the installer can), says where it lives, and the unlock page names the same file for a box with no screen. The three lines that claimed there was no PIN are gone. -
[Fix] A failed Linux update says it failed. The updater wrote down what went wrong and nobody read it, so the control page announced "Nunki stops and comes back in about a minute" to a Nunki that had not stopped and was not going to. The page now asks, and a failure is shown with the updater's own words and a button to try again.
-
[Fix] The updater trusts no symlink in a folder the service owns. It runs as root inside
/var/lib/nunki, which belongs to the unprivileged service user, and used to copy and chown whatever it found there. A state file or abackupsfolder that is a symlink is now skipped with a word, and so is a request that is not a plain file. -
[Fix] The PIN stays out of the log, and out of the lost-and-found.
pinjoins the parameters Phoenix hides when it logs a request. A PIN that cannot be written (full disk, read-only folder) is an error on the page instead of a crashed page whose crash report quoted the new PIN. Aaccess-pinedited in a Windows editor, whose lines end in CRLF, is the PIN it says, not a reason to make a new one; a file that really is unusable is replaced with a line in the log saying so. -
[Fix] A join that could not be saved is not a join. The one-time code is spent and the key lives only in
state.json; if that file cannot be written, the page now says so instead of listing a tournament that vanishes at the next start. State is flushed to disk before it replaces the old file. -
[Fix] A frame Nunki cannot make sense of is skipped. A round with boards that are not boards used to crash the line, reconnect, be sent again and crash again until the supervisor gave up on every tournament at once. It is now logged and skipped, and not stored.
-
[Fix] Reconnecting a line no longer adds another ping chain to it. A stopped reading no longer leaves its sound file in the speech folder on Windows, and the folder is swept at start. The cookie-signing secret is never in a world-readable file, not even for a moment.
POST /unlockwith a body that is not a PIN is a wrong guess, not a 500, and a control-page event with a made-up announcement is ignored. The 403 for a name Nunki does not answer to now says which name and what to do. -
[Security] There is always an access PIN, and every other computer is asked for it. Until now
NUNKI_LISTEN=lanmeant that anybody on the hall's network could start a countdown, stop a reading or read the pairings off the hall screen, on the theory that a hall is full of friends. Nunki now makes 6 random digits at the first start (access-pinin the data folder, owner-only), shows them on its own control page, and asks every browser that is not on this machine for them before any page, the hall screen included; a TV's browser enters them once. This machine is never asked, and neither is anybody while Nunki listens on this machine only, which is still the default. The PIN can be changed on the control page (6 to 64 characters, no space at either end, nothing invisible) or replaced by a new random one, and cannot be removed: an empty field is an error, not a policy. Five wrong guesses make an address wait 5 seconds, then 10, 20 and so on up to a quarter of an hour, and the right PIN is refused while it waits; the whole box takes at most 40 wrong guesses a minute. The guess is counted before it is compared, so a burst cannot outrun the count. A browser is given a keyed stamp of the PIN, never the PIN, so changing it logs every other browser out and closes their open pages. The PIN is never logged, never in an address, and never on the hall screen. A Raspberry Pi image can set it before Nunki starts with apin-requestfile (setand the PIN, ornew), which Nunki applies and deletes whatever came of it. -
[Change] Reference source, no longer a free-for-all. The Functional Source License lasted an afternoon, which is roughly the lifespan of a decision nobody finished thinking about. Nunki's source is now published for reference under the Microsoft Reference Source License (Ms-RSL): you may read it, and that is the whole grant. The builds we publish remain free to use for running chess events; builds you make yourself are not covered. The version published under the FSL today keeps the FSL for whoever already has it, since a licence, unlike a mood, cannot be taken back. CI runs on GitHub-hosted runners now that anybody may watch it, and the release workflows stay switched off until December.
Nunki 0.5.0
-
[Security] phoenix_html 4.4.0. 4.3.0 picked up an advisory overnight (EEF-CVE-2026-117645, medium), and the dependency audit stopped the build, as it should.
-
[Security] Bandit 1.14.1. Three fresh advisories against the old Bandit (HTTP/2 header blocks that unfold into unbounded allocations, quadratic work on blocked streams, WebSocket frames after a close) turned the dependency audit red. Updated, with
plug_crypto2.2.1 riding along; the audit is green. Nunki never spoke HTTP/2 to anybody, but the audit does not grade on intent. -
[Change] The control page fits a 3.5 inch screen. A Nunki box with a 480x320 panel (or 320x480 upright) showed the control page as a desktop one: a header that did not fit upright and pushed the page sideways, links and language buttons about 30 pixels tall, ticks the size of a comma. Under 520 pixels wide or 360 tall the margins, panels and type tighten and the nav links, language buttons, buttons, fields and ticks get 44 pixel targets; upright, the nav drops to its own row under the logo instead of leaving the screen. The hall screen already scaled itself and is unchanged. A bigger screen sees the same page it always did.
NunkiWeb.CompactCssTest. -
[Change] The control page is small until you ask for more: "Show advanced features". Most halls want the announcer, the list, Join, Read now and a countdown, and had to scroll past voice pickers, two Test buttons, a rooms form per tournament and a panel about the device's name to find them. All of that now sits behind a switch at the bottom of the page, off by default; the voice you chose keeps being used while its picker is hidden, and a missing speech engine is reported regardless, because silence with no explanation is not a minimalist design. An existing installation that already uses any of it (a chosen voice, a room or announcer name, a renamed device, update checks off) is switched on once, when it first starts, and stays as it is. The manual marks the advanced parts.
Nunki 0.4.3
- [Change] The Mac app is signed with a Developer ID and notarised by Apple. Until now it was signed with nothing but good intentions, and every Mac that downloaded it asked the arbiter to override Gatekeeper by hand, which is a strange way to greet someone who just installed your software. The release workflow now signs every binary inside Nunki.app, hardened runtime and BEAM entitlements included, sends the bundle to Apple, staples the ticket and checks the verdict with
spctlbefore the zip exists. A fork without the secrets still builds, with a warning, ad-hoc signed. The workflow can also be started by hand with mac_only to test all this without publishing anything. - [Change] Releases carry signed build provenance. Every file of a release,
SHA256SUMSincluded, is now attested through GitHub and Sigstore, keyless, sogh attestation verify <file> --repo teapot-chess/Nunkican say who built it and from what. Until now the checksums vouched for a download only against the release they sat in, which is a witness who was hired by the defendant.
Nunki 0.4.2
- [Fix] Stopping from Ascella, an update or a logout no longer hangs on "Stopping". On a Mac, the window waited for its server to end inside the very queue that was to bring the news, so the server ended and the window kept saying "Stopping" until somebody force-quit it. Quit from the menu never had the problem, which is how it survived this long. Any stop that hangs anyway now ends after forty seconds.
Nunki 0.4.1
- [Feature] Nunki for Intel Macs, from macOS 10.13. macOS 10 exists only on Intel Macs, and they had been struck off on the 14th because their build is slow. It is back, and it is built only when there is a release to put it in (or when somebody starts the workflow by hand), so the other pushes are as quick as they were. Nunki's own update notice picks the zip for the Mac it is on, and no longer says an Intel Mac has no build; an Intel Nunki running under Rosetta on an Apple Silicon Mac is treated as the Apple Silicon Mac it is. Every program in the bundle is checked against the oldest macOS promised, as before. Whether a 2017 Mac and its
sayvoices agree is for a person with both to say; see docs/macos.md.
Nunki 0.4.0
- [Fix] Switching the hall announcer off now cuts the announcers off. The feature only removed the menu entry: announcers already joined kept receiving every round (and read it aloud), a join link made in the fifteen minutes before still worked, and the admin could not remove an announcer because the disabled-feature guard swallowed Remove. An announcer of an account without the feature is now refused at
hello(as revoked) and at joining; the page keeps listing the announcers, with Remove, while the feature is off. - [Security] A web page can no longer drive the announcer by renaming it. The pages were open to any
Hostand any socket origin, so a page in the hall PC's browser could point its own name at 127.0.0.1, count as same-origin, and press the control page's buttons, including the ones that decide what the hall's loudspeakers read out. Nunki now answers 403 to aHostthat is not its own (localhost,127.0.0.1,PHX_HOST, and withNUNKI_LISTEN=lanthe machine's host name and addresses), and the live socket checks the same list. The launcher, the in-app window, the hall screen on another machine and LAN mode ask for those names and carry on as before.
Nunki 0.3.1
- [Fix] Stopping no longer ends in a red stack trace. On the way out the launcher-details process tidied up its secret by asking the application controller, which at that point is busy dying and answers everyone with an exit. The secret goes with the VM anyway, so now it lets the question go unanswered and leaves quietly.
Nunki 0.3.0
- [Feature] An announcer's room is now a room of the tournament, and it reads only that room's boards. The free-text field was a label with ambitions; the tournament's rooms (Settings, Rooms in OpenPairings) are the list now, kept by id, so renaming "Hall B" to "Annexe" does not strand anyone. An announcer in a room is sent just the boards the room holds, and a room change sends the round again. No room still means every board. The
settingsframe gainsrooms_availableand, for a room the tournament never heard of,error: "room"(hall-link v1, additive). Nunki shows a select when the server sends the list and a text field when it does not. Rooms typed before this existed match nothing, stay on screen as a label, and filter nothing; they are not migrated, because there was nothing to migrate them to. - [Change] New address. The repository moved to github.com/teapot-chess; old links still redirect, out of politeness rather than obligation.
Nunki 0.2.0
-
[Fix] Stopping Nunki stops the voice too, whoever goes first. Every program Nunki starts -
say,espeak-ng, PowerShell,killitself - now has a deadline, and is killed when whoever was waiting for it is gone. The voice reading a line aloud is killed even when the Speaker is not given the chance to say goodbye, and whatever is still talking when Nunki stops goes with it. Erlang closes the port and walks away; the program on the other end used to finish its sentence to an empty hall. -
[Fix] No part of a stop waits forever. Every supervisor has a deadline, open browser connections get three seconds instead of fifteen, and on the Mac the launcher's SIGKILL after twenty seconds now reaches the whole tree under the server - the BEAM and the programs it started - rather than the BEAM alone. The app's own last resort, ten seconds later, does the same instead of killing only the script and leaving the server to launchd.
-
[Change] The Hall announcer moved from a tournament's top bar into its Settings. It is set up once per tournament and then left alone, which is what the Settings rail is for; the top bar goes back to what is used every day. In OpenPairings: the tournament's Settings, Hall announcer, Add an announcer. The page keeps the rail beside it, and every text that told you where to look now tells you where to look.
-
[Feature] An announcer has a name and a room, and both sides can change them. OpenPairings shows the room beside the name and has a small form per announcer; Nunki shows both per tournament and has its own. There is one truth, the server's: a change from either side becomes a new
settingsframe (hall-link v1, additive, still version 1), and the other side shows what the server says, not what it was asked. With the line down the fields are disabled, because asking nobody for a change is just typing. -
[Change] The Hall announcer switch is in the Belgian pack of OpenPairings' Features, not under "Optional tools for any federation", a heading whose main achievement was never being read.
Nunki 0.1.0
- [Feature] Nunki exists. It reads the pairings aloud the moment OpenPairings publishes them, white first, byes last, and counts down to the round: ten minutes, five, one, and "starts now". Only the moments still ahead, so a countdown started at five minutes does not open with "ten".
- [Feature] English and Dutch, following the tournament unless the control page says otherwise. Dutch says "je", because nobody in a playing hall has ever been addressed as "u" by a loudspeaker and liked it.
- [Feature] The machine's own voice, not the browser's: PowerShell on Windows,
sayon a Mac, espeak-ng on Linux. It speaks with every page closed and never waits for somebody to click first. - [Feature] A control page: join a tournament with one pasted link, see whether each line is up and why not, Read now, Stop, a countdown of your own, the voice per language and a button to hear it before the players do.
- [Feature] A hall screen for a projector: the minutes in very large digits, then "Round 3 has started"; the latest pairings otherwise; the line being said at the bottom. One button for full screen.
- [Feature] A round that is corrected after it was read is not read again by itself. Reading the same pairings twice is how a hall learns to stop listening.
- [Feature] Installers and updates as in the other hall programs: a Windows installer that updates itself and a portable zip, Linux archives for PCs and the Raspberry Pi with a one-line installer and a systemd service, and an Apple Silicon Mac app. An update refuses while a countdown runs or Nunki is speaking, unless somebody says yes twice; a countdown that stops a minute before zero is a round that starts in silence. The news of a newer version is on the control page and the help, and never on the hall screen, which the players read and which is none of their business.
- [Feature] "Start Nunki when Windows starts", on the control page of an installed Windows copy, off until somebody turns it on. Uninstalling takes the setting with it, so Windows is not left starting something that is gone.