Ctrl+C to Step Away: Keyboard Shortcuts for Phosphor's Session Persistence

Mon, 31 Aug 2026 00:00:00 +0000

Last week we shipped session persistence for Phosphor BBS: detach your session, close your terminal, reconnect later, and your screen, cursor, and half-finished input are exactly where you left them. The first post covered the detach/reattach architecture. This post is about the keyboard shortcuts we built to make it feel right.

Because the hardest part of session persistence isn’t keeping the state alive — it’s making the exit feel natural.

The key binding problem

A BBS is not a shell. When you SSH into a Linux box and hit Ctrl+C, you’re sending SIGINT to the foreground process. When you hit ESC in vim, you’re entering normal mode. These are deep muscle memories, and every terminal application has to decide how to honor or override them.

tmux for Your BBS: Phosphor Sessions Now Survive Disconnects

Sat, 29 Aug 2026 00:00:00 +0000

If you’ve used tmux or screen, you already understand what we just shipped for Phosphor BBS: the ability to walk away. Close the laptop. Lose the train tunnel Wi-Fi. Kill the app by accident. Come back — and everything is exactly where you left it.

That’s now how sessions work on a Phosphor DTP server. And it changes what kind of place your community server can be.

The problem: a socket is not a person

Traditional BBS software — and, honestly, most modern chat infrastructure — ties a user’s session to a network connection. The socket closes, the connection dies, and everything the user was doing evaporates. You were halfway through writing a long post, three screens deep into a file area, mid-conversation in a chat channel. Gone. Reconnect and you’re back at the login prompt, starting over.

Session Persistence on Phosphor BBS

Ctrl+C to Step Away: Keyboard Shortcuts for Phosphor's Session Persistence

The key binding problem

tmux for Your BBS: Phosphor Sessions Now Survive Disconnects

The problem: a socket is not a person