See architecture.md for the layering. This file covers who may connect and how servers relate.
- LAN / event (e.g. VCF): one server, no accounts. The network is the trust boundary. HELO name claims a handle (sign-in none) for as long as the connection lasts; optional table PINs; admin kick/ban; tables expire. A read-only spectator frontend can drive a scoreboard display.
- Open internet: the core never does modern auth. The plain 8-bit port stays on loopback or LAN. Reachable endpoints are *bridges* (trusted server extensions) that handle TLS, identity, rate limits and abuse, then assert a player identity to the core with a trusted credential. A retro machine talks plain protocol to a bridge on its own LAN; the bridge talks TLS onward.
- Every table is hosted and arbitrated by exactly one server (its host); there is no replicated game state.
- Players are user@domain; the home server vouches for them with signed requests. A remote player reaches a table through their home server, acting as a server extension.
- Servers advertise their hosted games (type/ver and rulesets) and open tables to each other: a federated lobby. A remote client sees the same type/rules listing as a local one.
- Used for: server and player identity (actors, WebFinger), discovery (actor collections for hosted games and open tables), signing (HTTP signatures), and challenges, invitations and session setup (activities delivered to inboxes). Our own extension types (Table, Game, Move) carry game data; servers that do not understand them ignore them.
- Not used for live turns. ActivityPub is asynchronous and retried, fine for the lobby, invitations and correspondence-speed play, but slow for live games. Once a remote player is seated, their home server holds a persistent signed connection to the host and carries the ordinary client protocol (protocol.md) over it.
- Optional. A LAN parlor, such as one at an event, needs none of it.
- Humans see it too. Because it is ActivityPub, the human-readable layer (notifications) can later use the same actors; that stays a separate, punted layer (architecture.md).
- Reference implementations: snac and snarc, for the actor, WebFinger and signature mechanics.
Deliberately punted. See architecture.md, layer 4.
This doc on GitHub
| | These pages cover every ParlorNet server. | Source code | ParlorNet is free software. |