Debugging on Phosphor BBS

The Case of the Vanishing Blink

Tue, 20 Oct 2026 00:00:00 +0000

For years, picking an item on the Phosphor main menu did a small, satisfying thing: the row flashed — inverted video for about 150 milliseconds — and then the next screen took over. It’s a 65-byte courtesy. Two tiny frames: highlight the row, unhighlight the row, go.

Then one day the flash was just gone in Terminal.app’s telnet client. Not intermittently. Gone. MuffinTerm still showed it. The web client showed it, but only one flash instead of two. Three different clients, three different answers, one unchanged server. By the time we sat down to hunt it, every standard explanation had already been eliminated: the code was untouched since the feature shipped, the server was provably running the current build, the user’s preferences and theme tested innocent, and the same binary rendered the blink perfectly against a test instance. Same client, same server, same account. Different port. Blink on one, gone on the other.

The Case of the Invisible Popups

Mon, 05 Oct 2026 00:00:00 +0000

The session log screen has two popups: [H] on a row pops up that connection’s full history, and Enter pops up the session’s details. The SysOp account-review screen pops up a confirmation with the temp password when you approve a request. File lists pop up a preview panel. All four had been built the same way — a Window, a hint list, a Label shoved into the contents panel — and all four now shared the same bug report: the popup doesn’t appear.

The Case of the Blended Batches: A Race Hidden Inside a Replace

Wed, 23 Sep 2026 00:00:00 +0000

The jterm thread-safety suite exists to answer one question: can a widget survive being redrawn from one thread while another mutates it? It has run thousands of times across dozens of widgets, mostly to say yes. On the morning we cut the 0.1.1 release, it said no — and the test that failed wasn’t even the one that was broken.

Two failures, two days apart

The release gate runs the whole suite, 2,926 tests. The first full run failed one test: FireworksTest.renderFrameProducesOutput — the fireworks animation was supposed to paint visible pixels after five frames and, once out of 2,926, it painted nothing. We re-ran the class in isolation: 12/12 green. Read the render path: fresh instance, deterministic math, five calls that each draw a rocket or particles. The failure looked like noise under load — the kind of flake you shrug at and re-run.

The Case of the Very Random Dead Ctrl-T

Sun, 20 Sep 2026 00:00:00 +0000

Two weeks into the popup chat feature, users started reporting the same thing in different words: Ctrl-T is very random. Sometimes it opened the chat popup instantly. Sometimes it did nothing — not even an error. Same terminal, same screen, same key. First press of the session would work, three presses in a row would work, then a press after closing the popup with ESC would go dead. Then it would work again. There was no pattern, which was the most maddening part — a consistently broken key is a bug report; an inconsistently broken key is a haunting.

The Case of the Garbled Borders: Fixing SyncTERM Support

Fri, 18 Sep 2026 00:00:00 +0000

Every BBS lives or dies by its client support. MuffinTerm works. The web client works. And then a user pointed out that the most popular terminal program in the BBS world — SyncTERM, the client that most of the people dialing into boards in 2026 are actually using — rendered every screen as mojibake. Box borders turned into ┬í┬┐ soup. The login screen was unreadable. Our own sysop confirmed it the same evening from his own machine: “completely messed up.”

Five Bugs in One Morning: Debugging the Phosphor iOS Client

Fri, 04 Sep 2026 00:00:00 +0000

The QR pairing post ended with a working native iOS client for Phosphor BBS. What it didn’t cover is what happened next: the app crashed randomly, the keyboard never appeared, and the whole UI rendered in a sad little window in the middle third of the screen. One morning of debugging later, every bug had a root cause, and every root cause was a lesson worth writing down.

This is a war story. Five bugs, five root causes, and the one thread that ties them together: things that pass every test and still fail on real hardware.