The Hub Portal

────────────────────────────────────────────────────────────────────────────────

              ─▄─  ▄──▄  ─▄─  ▄──▄  ▄──▄  ▄──▄   ▄──▄  ▄──▄  ▄──▄
               █   █  █   █   █─    █─▄▀  █  ▐▌  █  █  █  █  █─▄▀
              ─▀─  ▀  ▀   ▀   ▀──▀  ▀  ▀  ▀──▀   ▀──▀  ▀──▀  ▀  ▀


                   Federated Terminal Game Network   hub.interdoor.net
────────────────────────────────────────────────────────────────────────────────

  1 node online  ·  5 events indexed

  #    NODE              GAME                   ADDRESS                  PLAYERS
  ───  ────────────────  ─────────────────────  ───────────────────────  ───────
  [1]  thelow            Ledger of the Low      node.interdoor.net:2323  1



  [1-9] Connect  ·  [R] Refresh  ·  [Q] Quit
  Select: 

The hub is the network's front door. Browse nodes, see who's online, press a number to get the connect command for that game. Runs in any SSH client with no setup. Each node defines its own game and its own look — this screen is the hub itself.

Connect

What This Is

InterDOOR is a hub-and-spoke network of SSH game servers. Each node is independent — its own binary, its own SQLite database, its own players. But they all speak to a shared hub, which gives you:

  Cross-node roster — see who's playing on other servers right now.
  Cross-node PvP — attack players on other nodes. They fight back.
  Travel — move your character to another node and play there a while.
  Obligation ledger — debts accrue and replicate across the network.

The reference game, Ledger of the Low: The Old Bargain, ships with the node binary. Think Legend of the Red Dragon without the dragons: twelve actions a day, a shared leaderboard, and an economy that runs on scavenged goods and outstanding debts. The network is the product. The game is the demonstration.

Node Directory ● live

Run a Node

The node binary is statically compiled — no runtime, no database server, no Docker. Drop it on any Linux box and it runs. The SSH host key generates on first start. Player accounts are stored in a local SQLite file. Standalone mode needs nothing else; federation just adds a config key and a registration token.

To join the public network, you need a registration token from the hub operator. The process:

1. Download the binary and run it in standalone mode. Confirm it works.
2. Open a GitHub issue with your proposed node ID and public SSH address.
3. Token arrives by return. Add it to your config file and restart.

Full sysop guide: github.com/njb1966/interdoor → files/SYSOP_GUIDE.md