ParlorNet
Turn-based game server for any computer, old or new
Clients | Protocols | Browsers | Telnet programs | Docs | Source

Supported protocols and server extensions

A parlor supports several protocols, one per port. Each is served by a server extension: a program on the server side that speaks that one protocol to frontends, the programs players use (a web browser, a telnet program, Reversi The Eclipse, MacFIBS and the like: frontends.md), and the native protocol to the core behind it. The native protocol is served by the core itself, with no extension in between. Every protocol reaches the same players and the same tables, so a game started in a browser can be watched from a terminal and joined from a 1990s Mac game. How the server extensions are built is in adapters.md; in the code they are the adapters/ package. This page tells, for each protocol, how to connect, how to sign up and sign in, what you can do, what it needs, and where the protocol came from.

KeyUsual portProtocolOriginYears in useServer extension
HTTP6500HTTP and HTML 3.2HTML 3.2: W3C Recommendation, January 19971997 to nowweb extension (adapters/web.py)
PARLOR/16501ParlorNet protocol (PARLOR/1)ParlorNet, 20262026 to nowthe core itself (parlord)
TELNET6502Telnet with ANSI escape codesTelnet: RFC 854, 1983; ANSI X3.64 / ECMA-48, 1970s; IBM PC characters (CP437), 19811983 to nowtelnet extension (adapters/telnet.py)
IOS6503Internet Othello Server (IOS)Igor Durdanovic, 1993, for the Waterloo computer Othello tournament1993 to about 2000IOS extension (adapters/ios.py)
GGS6504Generic Game Server (GGS)Igor Durdanovic, NEC Research, about 1999about 1999 to nowGGS extension (planned)
FIBS6505First Internet Backgammon Server (FIBS)Andreas Schneider, 1992; the CLIP client mode, 19971992 to nowFIBS extension (adapters/fibs.py)
OUTLAND6506OutlandOutland, Inc., Palo Alto: a Mac online games service1994 to the late 1990sOutland extension (adapters/outland.py; port 4000 in the container)
DOOM6507DOoM crossword-game serverJohn Chew, late 1993, to replace ScrabbleMOO1993 to about 2005DOoM extension (adapters/doom.py)

Each protocol has a key (HTTP, PARLOR/1, TELNET, IOS, GGS, FIBS, OUTLAND, DOOM). Each server extension declares its key, its port, a name and a one-line description to the core when it connects (protocol.md), and a server's own Protocols page (/protocols.htm) lists what is connected now, with its ports; the ports above are the usual ones. Each key there links to its entry in the docs site's protocols reference.

Status today: the web site (1997 side), telnet, the native protocol, IOS, FIBS, Outland and DOoM are running; Outland and DOoM have been tested against scripted clients but not yet with the original programs. The web site's 2027 side and GGS are planned. The docs site's Clients page has the programs that can play each game, game by game, each with a setup page: where to get it, how to point it at a server and how to sign in (clients.md).

Every server extension signs you in the same way, by passing on what the server asks for: see Signing up and signing in. Each part below says what that looks like with that protocol's frontends.

Web site

The web site is the pages on port 6500, from the welcome page on, served by the web extension (adapters/web.py); the frontend is your browser. It has two sides on the same port: 1997, which runs now, and 2027, which is planned.

1997 side

Connect: open http:// the parlor's name, port 6500 (for example http://parlornet.org:6500/); the server sends / to the welcome page. Plain HTTP, no encryption.

Signing up and signing in: Sign in and New account are separate, on the welcome page and in the navigation bar. New account: type the name you want and press Make the account. The server then asks, one page at a time, for what its methods need: on a password server, a password to choose and type again; on an authenticator server, your email address, then the 6-digit code from your authenticator app once you have scanned the QR code mailed to you. To come back, Sign in: your name and your password (or leave it empty and answer the next page). A name with no account is told so, with a link to New account; signing in never makes an account. Your session is kept in a cookie (in the page's links for a browser without cookies) and ends when you sign out or close the browser; your password never appears in an address.

What you can do: in the lobby, see every table with its game, seats and players, join an open one, watch a running one, and start a table of any game the server hosts, with a time per turn (5 minutes to 1 week) and public or private seating (by invitation). Invite players to your table, and accept or decline invitations. Play Reversi by clicking a yellow dot, and Backgammon by clicking a checker and then where it goes, with buttons to roll, double, take, drop, undo and end the turn. Resign (after a confirmation), stand up or stop watching. Sign out, or sign out everywhere; on a password server, change your password. The Protocols page (/protocols.htm) lists the protocols the server speaks now, each linking to its entry on the docs site, http://docs.parlornet.org/, which has these docs, the clients and their setup.

Refresh: a table page updates itself while you wait for the other player. Without JavaScript it reloads itself (an HTML meta refresh) at the rate you pick on the page: off, every 3, 5, 10, 30 or 60 seconds (5 is the default); it does not reload while it is your turn or after the game ends. With JavaScript and XMLHttpRequest, a small script asks the server every 2 seconds whether anything changed and reloads only when it did. JavaScript is optional: every page works without it.

What it needs: a browser that shows HTML 3.2 tables, forms with menus (SELECT), and GIF images with an image map, server-side (ISMAP) or client-side (USEMAP). The pages use no CSS and no frames (a cookie holds the session where the browser keeps one), and only named and decimal character references. On a 68000 Mac (Plus, SE, Classic, PowerBook 100), the recommended browser is Mill (freeware from OneInAMillion Software); on a System 7 Mac with a 68020 or later, or a PowerPC Mac, it is Netscape Navigator 3.01. The Browsers page lists every browser known to meet these needs, with its setup; the evidence for each is in clients.md. How the pages look in each class of browser: site.md.

History: HTML 3.2 was published as a W3C Recommendation on 14 January 1997 (W3C); NCSA Mosaic, the browser the page is written to work in, dates from 1993. The JavaScript polling uses XMLHttpRequest, which browsers took up in the early 2000s; older browsers simply use the meta refresh.

2027 side

Planned, not built. A modern site on the same port: a JSON API under /api/ with the same typed views as the native protocol, and canvas, WebAssembly and WebGL clients on top of it. /2027/ is reserved for it. Both sides are clients of the same game server, so 1997 and 2027 players share tables.

Telnet

Served by the telnet extension (adapters/telnet.py); the frontend is any telnet program.

Connect: telnet the parlor's name, port 6502 (for example telnet parlornet.org 6502).

Signing up and signing in: at the Login prompt, type new for a new account, then the name you want. The server then asks, one prompt at a time, for what its methods need: on a password server, a password to choose and type again; on an authenticator server, your email address, then the 6-digit code from your authenticator app once you have scanned the QR code mailed to you. To come back, type your name at Login and answer the prompt for your password or the current code. A name with no account is told so, with a reminder about new. Passwords and codes are not echoed. Then pick a display.

Display modes: the terminal type your telnet program reports picks a default, and a menu shows a sample line in each mode so you can pick the one that looks right:

What you can do: in the three ANSI modes the screen is a full-screen menu and board. The menu lists your tables (opponent, time per turn, whose move, time left), the other tables, and an entry to start a table of each game. Move with the arrow keys and choose with Enter; single keys are listed in a status bar (N new table, W watch, P password on a password server, O options, ? help, Q log off). On a board, arrow keys move a cursor, Enter or Space plays, T talks to the table, R resigns after a confirmation, and Esc goes back to the menu while the game goes on. Typed commands work everywhere too (join 1, new 5m, d3, say hi, quit). Leaving a table or hanging up never resigns.

Movement keys: if your telnet program sends no arrow keys, letters can move the cursor instead: IJKL, ESDF, WASD or HJKL (vi). Choose them with O in the menu (or K at the login's last prompt, offered when the terminal type suggests no arrow keys). The arrows still work. Those four letters then always move; to type a command or a word that starts with one of them, press : first (:join 3), and a key whose letter is one of them is : then the letter (:d). The choice is kept for your next visit.

Mouse: when the terminal type is one that reports mouse clicks (xterm-class terminals: xterm, PuTTY, iTerm, Alacritty, kitty, Konsole, GNOME Terminal, WezTerm, foot, and screen or tmux; not the Linux console), you can click menu rows, squares, checkers, dialog buttons and status bar keys. The keyboard always works without it.

What it needs: for the full screen, a telnet program with VT100 or ANSI cursor positioning and a screen of 80 columns by 24 rows; arrow keys, colour and line characters are optional (letter keys can stand in for the arrows). Without cursor positioning, the plain mode plays line by line. The Telnet programs page lists programs known to work, with their setup. If the telnet program reports its window size and the window is smaller than 80x24, the screen asks you to make it larger and redraws once it is. Only the cells that change are sent, so moving the cursor costs about 100 bytes and a 2400 baud line is usable.

History: Telnet is the Internet's original remote terminal protocol; the version in use today is RFC 854, May 1983 (RFC 854). The terminal type and window size come from telnet options added later (RFC 1091, terminal type, 1989; RFC 1073, window size, 1988). The colour and cursor codes are the ANSI escape sequences of ECMA-48 (first edition 1976) and ANSI X3.64 (1979), as made popular by the DEC VT100 (1978). The pc characters are code page 437, the character set of the IBM PC (1981). The utf8 mode uses UTF-8, designed in 1992.

Native protocol

Connect: port 6501. The client sends a newline first (CR LF, CR, LF CR or LF), within 5 seconds; the server answers with its greeting and uses that line ending from then on. The core serves this protocol itself, with no server extension in between. It is the protocol every server extension uses to talk to the core, and it is open to anyone writing a frontend of their own (a native ParlorNet client).

Signing up and signing in: both go through the same dialogue: the client sends USER name to sign in or REG name to sign up (or HELO name, which does either), and the server sends lines to show (INF) and asks for each value it needs (ASK field label), which the client answers with AUT field value until the server says OK. A client that shows each line and label and sends back what the player types can sign up and sign in under any method (accounts.md).

What you can do: everything: list games and tables, start, join, watch and leave tables, invite players, play moves (including staged turns such as a Backgammon turn), chat, and poll for events. Each game type has its own typed view and move grammar, so a client can draw the game its own way.

What it needs: a machine that can open a TCP connection and read and write lines of 7-bit ASCII text. Lines are at most 80 bytes, nothing is sent unasked, and there are no keepalives, so an 8-bit micro can poll at its own pace. The protocol is in protocol.md; the game types are in types/reversi-1.md and types/backgammon-1.md.

History: ParlorNet's own, designed in 2026 for this project. Its greeting line is PARLOR/1.

IOS

Served by the IOS extension (adapters/ios.py).

Connect: port 6503, from an IOS client. In Reversi The Eclipse, type the parlor's name as the host and 6503 as the port in its Internet Othello Server dialog.

Signing up and signing in: IOS login names are at most 8 letters and digits. Give your name and, as the password, your password or the current code from your authenticator app. A new name signs up in the client's own window, before the lobby: the server's questions appear as prompts there (Type it again: , Sign up as tia? (y/n): , Email address: , Authenticator code: ) and what you type in the window answers them; the password you gave is used only where a password or code is asked for. With no password given, the same prompt asks for it.

What you can do: play Reversi against anyone on the parlor, whether they came by IOS, the web or telnet. who lists the players who are online, wherever they connected, and the bot. match <name> accepts their challenge if they sent one. Otherwise it joins their open Reversi table if they are waiting at one, or opens a table and invites them. The bot sits down within a few seconds. The challenger's minutes become the time per turn. Invitations from anywhere arrive as challenges, and accept and decline answer them, moves are squares like d3 (passes are made for you), ob <game> watches a game, board shows a board, tell and say talk, and resign resigns. set board 1 adds text boards for people using IOS from a terminal. Games are unrated: ParlorNet keeps no ratings.

What it needs: an IOS client.

History: the Internet Othello Server was written in 1993 by Igor Durdanovic, after the Fall 1993 computer Othello tournament at Waterloo, where the server provided was poor; he modelled its commands and look on other Internet game servers such as the Internet Chess Server (ICS). It ran at Paderborn, Germany, and moved with him to the NEC Research Institute in Princeton in Fall 1996 (external.nj.nec.com, port 5000). It had over 1000 users by the late 1990s, and around 1999-2000 it was replaced on the same host and port by its successor, GGS. The IOS protocol is text meant for telnet, read by clients by line and column; no manual for it survives, so the IOS extension follows what Eclipse 1.2 and the OLIOS client source parse. Sources: research/ios-protocol.md (Durdanovic's history page, Wayback copy) and research/eclipse-ios-client.md.

FIBS

Served by the FIBS extension (adapters/fibs.py).

Not FIBS: the First Internet Backgammon Server (FIBS) still runs at fibs.com port 4321, and it is the place for serious Backgammon, with its long-standing community and ratings. ParlorNet speaks the FIBS protocol only so that vintage FIBS clients can play ParlorNet's games, which are aimed at vintage machines, events and casual play. ParlorNet is not FIBS, is not affiliated with it, and is not a replacement for it; its FIBS-protocol service says so in its login banner and never connects to fibs.com. More on the games page.

Connect: port 6505, from a FIBS client or a terminal. FIBS itself was on port 4321, so give the client the parlor's name and 6505:

Signing up and signing in: give your name and, as the password, your password or the current code from your authenticator app. As on FIBS, the login only signs in: a name with no account is told so. To sign up, do it the FIBS way: log in as guest, type name and the name you want, and answer the prompts.

What you can do: play Backgammon against anyone on the parlor, whatever they connected with. invite <name> <points> (or unlimited for a single money game) makes a private table and invites them; join <name> accepts, resumes a match, or sits at their open table, and decline <name> declines. Invitations made on the web or by telnet arrive in FIBS's own words. who lists the players who are online and the bot. Matches of several games are played at one table. Moves are typed or sent by the client (move 13-9 8-7, bar-22, 6-off), with roll, double, accept, reject and resign. who, watch, look, board, pip, and chat with tell, say, kibitz, whisper and shout (whispers and shouts reach FIBS players only). Left out: ratings (games here are unrated; the rating field that clients expect shows 0.00), redoubles and beavers, and stored messages. FIBS has no turn clock, but the table's time per turn still applies.

What it needs: a FIBS client, or any terminal.

History: the First Internet Backgammon Server was announced on 19 July 1992 by Andreas Schneider. It began in Aachen, Germany, moved to Chalmers in Sweden in December 1993, and was the only Internet backgammon server until 1997. It was designed for people on telnet, "similar to a MUD"; the first graphical clients, MacFIBS and FIBS/W, came in 1994. Schneider's CLIP specification (version 1.008, March 1997) added a mode that is easier for programs to parse. Patti Beadles has run FIBS since 1996, and it still answers at fibs.com port 4321 (checked 21 November 2026). Sources: research/backgammon-network.md, research/bg-client-macfibs.md, research/bg-client-fibsw.md and research/bg-client-x11.md (CLIP specification, Wayback copy; Backgammon FAQ, 1995).

Outland

Served by the Outland extension (adapters/outland.py), which listens on 4000 in the container, Outland's own port; the host publishes it as 6506.

Connect: port 6506. In the Outland Gateway, open the Outland TCP Tool's settings and type the parlor's name as the host and 6506 as the port (the field is editable; Outland's own port was 4000). Nothing else on the Mac needs changing.

Signing up and signing in: the Gateway's account name is your ParlorNet name, and its password answers what the server asks for: your password or the current code from your authenticator app. As with Outland's own service, the Gateway only signs in: make your account on the web site (New account) or by telnet (log in as new) first. For a name with no account the Gateway shows where, then hangs up. The Gateway's own account creation is not used.

What you can do: play single games of Backgammon with Outland Backgammon. The lobby lists the players who are online, wherever they connected, and the bot. You can challenge anyone there. A challenge to another Outland player goes straight to them. A challenge to a player waiting at an open table joins that table. A challenge to anyone else, such as the bot or a web player, becomes an invitation they answer from their own program. Invitations from the web or telnet arrive as challenges. /open in the lobby chat opens a table that web and telnet players can join, and you get a challenge when someone sits down. The server rolls the dice, as Outland's did. Doubles from web and telnet players are offered to you to take or drop; your own double is refused, because the client offers the cube only after the server has already rolled. Left out: watching, draws, high scores and software downloads.

What it needs: Outland Gateway 1.3.2 and Outland Backgammon: a Mac with a 68020 or later, or a PowerPC Mac (Backgammon itself is 68k code), with System 7 and MacTCP. The Info-Mac copy of the Outland installer has no games; the full set with Backgammon is on a 1998 Macworld CD (see the Clients page).

History: Outland was a Mac online games service run by Outland, Inc. from Palo Alto, from 1994: a free client, US$9.95 a month, reached by modem or over the Internet. Backgammon (by Aaron Barnett) was part of it by early 1995. Its protocol was never published; what the Outland extension speaks was recovered from the 1994-95 client software. The service closed in the late 1990s (the exact date is not established) and the company is gone. Sources: research/bg-client-outland.md and research/backgammon-network.md (Outland's own pages, 1996, Wayback copy).

DOoM

Served by the DOoM extension (adapters/doom.py).

Not DOoM: DOoM was John Chew's crossword-game server, and none of its servers is known to run today. ParlorNet speaks DOoM's commands so that DOoM's clients, BobGrid and any telnet or MUD client, can play ParlorNet's Grid Words with anyone on the parlor. The game is Grid Words on the standard board, with the classic ruleset on boards made here (docs/types/gridwords-1.md). The service says in its banner that it is not DOoM.

Connect: port 6507. In BobGrid, type /HOST parlornet.org 6507 and then /GO (BobGrid's own default is a DOoM host on port 7777). From a terminal or a MUD client such as TinyFugue or MUDDweller, connect to the parlor's name on port 6507.

Signing up and signing in: connect name password (or co name password), as on DOoM. The password is what the server asks for, your password or the current code from your authenticator app. BobGrid sends this line by itself once /CONWIZ has saved your name and password. A name with no account is told so. To make an account, type request name and answer the server's questions at the prompts, or sign up on the web or by telnet.

What you can do: after connecting you are in the Gaming Room, where every Grid Words table on the server is a board called bd_ and its number. look lists them. newboard sets up a board and sits you at it, and invite <name> asks someone to it, the bot too (invite bot). join bd_12 goes to a board and watches it, and join there sits down in a free seat; the game starts when every seat is taken. On your turn, place 8d WORD (row first for across, column first for down, lower case or ?-style marks for blanks, as in DOoM's help place) shows what the play scores, commit plays it and undo takes it back; exchange and pass are the alternatives. b shows the board, track the unseen tiles, time the scores and clock, log and log2 the game, and ", kibitz and page are for talking. Invitations made on the web or by telnet arrive as a line of text, and accept <name> or decline <name> answers them. who lists the players who are online and the bot. BobGrid redraws its board, log and tile tracker by itself on each turn. Left out: DOoM's world of rooms and objects, the board Workshop (every board here has the standard layout and tiles), ratings, time penalties and pausing the clock (the table's time per turn applies instead), and challenges, because every word is checked against the server's word list when it is played; ospd word looks words up.

What it needs: BobGrid 2.3 (Mark Watkins, 1999), a Java 1.1 program for Windows with Sun's JRE 1.1.8, for Unix with Java 1.1, and in principle for the Mac with MRJ, or any telnet or MUD client.

History: John Chew wrote DOoM, the "Distributed Object-oriented Mud", in Perl from late 1993, after ScrabbleMOO closed. It ran public crossword-game servers (MarlDOoM, WisDOoM) and a server for expert players (PoslDOoM), reached by telnet and later over HTTP too, and called itself a generic crossword-game server, since each board's layout and tiles were set by its owner. By late 2000 the DOoM servers had over 6,000 users and nearly 200,000 rated games. Mark Watkins' BobGrid gave it a graphical front end in 1999. Sources: research/clients-gridwords.md (DOoM FAQ, Wayback copy; BobGrid's pages, Wayback copy).

GGS

Planned: a GGS extension for Reversi on port 6504.

What it needs: a GGS client, such as GGSA (Java) or Lion (Windows 95 and later).

History: the Generic Game Server, by Igor Durdanovic at the NEC Research Institute, replaced IOS on the same host and port around 1999-2000. Unlike IOS it has a documented protocol with a mode for client programs, and its source was released under the GPL. It still runs, now at skatgame.net port 5000, on Michael Buro's pages. Sources: research/ios-protocol.md (GGS home).

Signing up and signing in

Neither frontends nor server extensions know the sign-in or sign-up method: the server names what it wants, the server extension passes that on, and the frontend shows it and sends your answer back. The operator picks one way to sign in and one way to sign up (accounts.md):

A password or code is never sent to the server unless it asks for one, and never shows in a page, an address or a log.

ProtocolSign upSign in
Web siteyes, every method: New accountSign in: name, then each answer the server asks for
Telnetyes, every method: log in as newname, then each answer the server asks for
Native protocolyes, every method: REG (the INF / ASK / AUT dialogue)USER, the same dialogue (HELO does either)
IOSyes, in the client's own window: a free name signs upname, and the password or current code as the password
FIBSyes, in the client's window: log in as guestname, and the password or current code as the password
Outlandon the web or by telnet firstname, and the password or current code as the password
GGSplannedplanned

After a wrong answer the name is locked for a minute, longer after repeated ones (at most 4 hours). While it is locked, reset still gets a code or a new setup by mail.

Operators have their own console, separate from these protocols.

This doc on GitHub


 These pages cover every ParlorNet server. | Source code | ParlorNet is free software.