Two kinds of server-side plugin, kept apart:
- Game plugins (plugins.md): rules for one game type. Subprocess, pure functions.
- Server extensions (this file): programs on the server side that each speak one protocol to frontends, the programs players use (a browser, a telnet program, a 1990s game client), and the client protocol (protocol.md) to the core. They sit in the transport layer of architecture.md and connect to the core's trusted port for server extensions. They never touch game plugins, and the core never learns that a player came through one. Players see them as the supported protocols (protocols.md, served as /docs/protocols.htm).
Server extensions live in the adapters/ package (adapters/*.py), and the code calls them adapters. The native protocol on 6501 has no extension: the core serves it itself.
One parlor (a deployment) listens on consecutive ports from 6500; the firewall opens 6500-6800.
| Port | Protocol | Served by |
| 6500 | HTTP, with two sides (below) | web extension, adapters/web.py |
| 6501 | native protocol (protocol.md) | the core itself (parlord) |
| 6502 | telnet | telnet extension, adapters/telnet.py |
| 6503 | Reversi over the IOS protocol | IOS extension, adapters/ios.py (game-network extension) |
| 6504 | Reversi over the GGS protocol | GGS extension (game-network extension; planned) |
| 6505 | Backgammon over the FIBS protocol | FIBS extension, adapters/fibs.py (game-network extension) |
| 6506 | Backgammon for the Outland Gateway | Outland extension, adapters/outland.py (game-network extension; it listens on 4000 in the container, Outland's own port, and the host publishes it as 6506) |
| 6507 | Grid Words over the DOoM protocol | DOoM extension, adapters/doom.py (game-network extension) |
| 6508-6800 | further server extensions | |
Port 6510 is the admin console (below), an operator extension: the operator's blue-screen menus, not for players and not listed on the web site. The core's admin socket, 6599, listens on 127.0.0.1 inside the container only and is never published.
The web site's pages, their frame and what each holds are in site.md, with the docs site's. The lists behind the web site are in adapters/web.py:
- The welcome page's Games list and the Games page (/games.htm) list every planned game in build order (GAMES) with players and status. A game is marked playable when the core lists it in GAM (asked before sign-in and cached with the greeting), so installing a plugin is enough. Each game has its own page, /games/<type>.htm: players, its status here, what the game is and the rules and options played here (GAME_ABOUT, from the type specs in docs/types/), and links to its type spec, its chapter of the protocol guide and its programs on the docs site. The Backgammon page says where FIBS is and that ParlorNet is not FIBS. /games.htm#<type> still lands on the game's row.
- The Protocols page (/protocols.htm) lists what this server speaks now, from the core's PRL: one row per protocol (key, port, name, what it is), each key linking to its entry in the docs site's protocols reference. There is no table of ports in the web extension: each server extension declares its own protocol when it connects (below).
- The clients for each game and each kind of computer, their setup pages, the Browsers and Telnet programs pages and these docs are on the docs site (http://docs.parlornet.org/, built by tools/build_docs.py from adapters/clients.py, docsite/ and docs/). Their old addresses on the web site answer with a 301 to the docs site.
Every server extension that players connect to declares its protocol to the core (docs/protocol.md, Protocols; docs/design/protocol-declarations.md). Its module has PROTOCOL = (key, name, description), and its serve() calls declare.start(args, PROTOCOL) (adapters/declare.py) once it listens: one connection to the core is kept open for PRO key port name and PRD key description, sent again every 5 minutes, and made again if the core goes away. The port is --public-port when the extension is published under another port than it listens on (Outland: 4000 in the container, 6506 on the host; deploy/start.py passes it from catalog.PUBLISHED), else --port. The core lists the protocol while that connection is open, and the web's Protocols page shows it. The admin console and the bot declare nothing.
| Extension | Key | Name |
| web | HTTP | HTTP and HTML 3.2 |
| (the core) | PARLOR/1 | ParlorNet protocol (PARLOR/1) |
| telnet | TELNET | Telnet with ANSI escape codes |
| IOS | IOS | Internet Othello Server (IOS) |
| FIBS | FIBS | First Internet Backgammon Server (FIBS) |
| Outland | OUTLAND | Outland |
| DOoM | DOOM | DOoM crossword-game server |
A GGS extension, when there is one, declares GGS. A new extension picks a key and adds its entry to the docs site's protocols reference (docsite/protocols.py); a test checks that every declared key has one.
Port 80 on the parlor's own name (parlornet.org, and www.) is a plain 301 to port 6500; the web server on 6500 then sends / to /welcome.htm.
- 1997: server-rendered HTML 3.2 for any browser with tables, forms and image maps (Mac Mosaic 2.0 and later; the Browsers page lists them): tables, forms, links and small GIFs only, no CSS (a little optional JavaScript polls for changes). Sign-in runs the server's steps through POST forms; the session the core issues is kept in a cookie, or in links (s=) for a browser that returns no cookie (docs/accounts.md, docs/security-design.md). No credential is ever in a URL or a page. Pages end in .htm. A game's board is one GIF drawn on the server (/board.gif, cached by the browser while the board is unchanged) with an image map: client-side (USEMAP) and, for older browsers, server-side (ISMAP, /click.htm); docs/games-howto.md has the details. Connections may be kept alive for a few requests (HTTP/1.0 Connection: keep-alive, HTTP/1.1). Built: every game with click-to-move.
- 2027: a modern site on the same port, a JSON API under /api/ with the same typed views as JSON, and canvas, WebAssembly and WebGL clients on top of it. Not built yet; /2027/ is reserved.
- The welcome page lets the visitor choose. Both sides are clients of the same core through the same extension code.
One telnet server for the whole game server, not one per game.
- Login by handle (as HELO), a menu built from GAM, then the table list from LST, with join or create.
- Per-type renderers: each game type has an 80x25 ASCII reference rendering (the rule in protocol.md); ANSI terminals get color and cursor placement as an enhancement. A renderer reads the type's typed view and events and draws the screen; it contains no rules.
- Terminal capability is negotiated or asked at login (plain 80x25, ANSI, narrower).
- Runs beside the server, is not part of it, and may be omitted by an operator.
Built (adapters/telnet.py): the screen is 80x24. The terminal type (telnet TTYPE) picks a default display mode, offered in a menu with a sample line per mode: pc (ANSI colour, IBM PC CP437 characters; the default when no type is sent), utf8 (the same characters in Unicode), ansi (colour, ASCII only) and plain (no escape codes).
- ANSI modes are full screen. The main menu has a title bar, a "Your tables" panel (opponent, time per turn, whose move and time left), an "Other tables" panel and a "Start a new ... table" entry per game (Reversi, Backgammon), chosen with the arrow keys and Enter; a status bar lists the keys (N new table, with a game picker when no new-table entry is selected, then a time-per-turn picker of 5m, 15m, 1h, 1d, 3d or 7d; W watch, P password (under sign-in password: the server's change steps), O options (the movement keys), ? help, Q log off after a Y/N confirmation; R refresh is in the help).
- The Reversi screen draws the board with double-line frame and single-line grid (ASCII in ansi mode), dark discs ??? and light discs ??? (X and O in ASCII) on green, a cursor cell, legal-move dots on your turn, and a side panel with players, disc counts, whose move, the turn clock and a log. Arrow keys move, Enter or Space places, T talks, R resigns after a Y/N confirmation, Esc goes back to the menu and the game goes on.
- The Backgammon screen draws the board as character art in a wooden frame: 24 points as triangles (CP437 blocks in pc and utf8; # and : fills with \ / edges in ASCII), checkers (?) and (?) ((O) and (X) in ASCII; white is seat 0) stacked on the points with a count when a stack is taller than 7, the bar, the tray with borne-off checkers and the cube (on its owner's side), the dice still to play on the mover's side, and a side panel with players, pips, borne-off counts, whose turn and the phase, the dice, the cube, the turn clock and a log. Your side is at the bottom with your home board on the right. Arrow keys move a cursor over the points, the bar and the tray; Enter or Space picks up a checker that can move (the cursor goes to its nearest target, and all its targets are marked) and Enter on a target plays the step (MOV); U undoes a step (UND), E ends the turn (END; Enter too, once nothing is left to play), Enter rolls, D doubles, A takes and P drops (after a Y/N confirmation). T talks, R resigns and Esc goes back to the menu, as on the Reversi screen; the status bar shows the keys that apply. Typed: 13-9, bar-22, 6-off, roll, double, take, drop, undo, end.
- Mouse: when the terminal type is one that reports the mouse (xterm, screen, tmux, rxvt, PuTTY, iTerm, Alacritty, kitty, Konsole, GNOME Terminal, WezTerm, foot; not the Linux console), full-screen mode turns on click reports (DECSET 1000 with SGR coordinates, 1006; the older ESC [ M form is read too) and turns them off again on leaving. A click selects a menu row (a second click opens it), plays a legal Reversi square, picks up a Backgammon checker and puts it down, picks an option or a button in a dialog, and presses a status bar key. Arrow keys work everywhere without a mouse.
- Typed commands still work in every screen (join 1, new 5m, d3, say hi, quit): a hotkey letter followed at once by more typing counts as typing.
- Movement keys, for terminals that send no arrow keys: a session's choice of IJKL, ESDF, WASD or HJKL (vi), made with O in the menu, or at the login when the terminal type is unknown or VT52-class (K at the "Press Enter for the menu" prompt). The arrows work in every choice, and the default is the arrows only. On an empty line the four letters, either case, move the cursor in the menu, the pickers and every board and never act as hotkeys. : opens the command line, where every letter types; : then a hotkey letter does what that key does (:d for D under WASD). The status bar shows the letters in place of "Arrows" and such keys as :d, and the help box starts with the letters. In Grid Words every letter types once Enter has set a word's start. The choice is kept with the player in the telnet extension's own data on the core (PRF, docs/protocol.md) and comes back at the next sign-in.
- Screens are composed as a grid of cells and only changed cells are sent, with short colour changes; a cursor move costs about 100 bytes and a clock tick about 25, so 2400 baud is usable. No line feed is sent and the bottom-right cell is never written, so the screen never scrolls.
- plain mode is line by line with a prompt; moves are typed (d3, 13-9). Backgammon prints the same ASCII board with the players, dice and cube beside it.
- Invitations: The menu lists the player's invitations. The plain menu shows them under "Invitations for you". The full-screen menu shows them at the top of Your tables and gives a notice when a new one arrives. Enter or join n accepts an invitation, and X or decline n declines it. At a table, invite name invites a player, uninvite name withdraws the invitation, and bot invites the bot. The table's log says how each invitation ended. who lists the players who are online.
- Leaving a table or disconnecting never resigns; only RES or the turn timer ends a game early.
adapters/admin.py, on port 6510: the operator's menus (docs/accounts.md, admin panel), over telnet. It reuses the telnet extension's terminal handling, cell screen and line drawing, and draws dialog-style screens: a blue background with a title line and a key hint line, grey boxes with a light top-left and dark bottom-right edge and a shadow, sunken lists, < OK > buttons with the active one highlighted. Menus, checklists, radio lists, one-line inputs (hidden for passwords), a multi-line editor for the message of the day, and message boxes; arrow keys, Tab and Shift-Tab, Enter, Space and Esc, and the first letter of an item or button. Before the first screen it asks for the display (pc, utf8 or ASCII), as the telnet extension does.
It is a client of the core's admin socket (127.0.0.1:6599: TLS 1.3 with an admin-role key, then the admin password) and has no power of its own; at most 4 sessions at a time.
adapters/catalog.py lists the server extensions a parlor can run, the admin console included, with their ports. The admin menus store the choice (the Adapters menu; setting adapters.enabled); the container's start script (deploy/start.py) reads it before starting anything and starts those that are installed, then parlord. With no choice stored, PARLOR_ADAPTERS or else every installed extension runs. If any process exits, the container exits and Docker restarts it.
Many games already have a network mode or a community server with its own text protocol. Where it makes sense, a server extension lets existing clients of that network play on our server, using our game types underneath.
- A game-network extension is specific to a game type (for example Reversi) and to one foreign protocol. It maps the foreign commands and login onto client-protocol requests, and our events onto the foreign output.
- Foreign identities become handles in HELO terms. Anything the foreign protocol has that we do not (ratings, rooms, tells, channels) is either mapped to an optional capability or left out; the extension documents what it drops.
- First target: the Othello-server protocol used by Reversi "The Eclipse" ("IOS"), in adapters/ios.py. Its output follows what Eclipse 1.2's code parses (docs/research/eclipse-ios-client.md): login ends on the first <ios> line, who in Eclipse's columns, listing the players who are online on any frontend and the bot, <ios> [name(-) connected and disconnected lines as players come online and go idle or leave, [GAME n ...] created/ended for every game, PB board lines, match name as an invitation through the core on a table made for it, invitations from anywhere as MATCH ... FROM offers that accept and decline answer, tells as name: text, and ob/board <n> for watching. Sign-in and sign-up run in the client's window before the lobby (docs/accounts.md, the dialogue): the name alone goes to the server, the IOS password answers its credential question (and is dropped if none comes), and every other step, a whole sign-up included, is a prompt with the server's own label; ratings are left out (games are unrated). A related documented Othello server, GGS, is planned as a further extension (port 6504).
- Second: Backgammon for clients of the First Internet Backgammon Server (FIBS), in adapters/fibs.py on port 6505 (research: docs/research/backgammon-network.md and bg-client-macfibs.md, bg-client-fibsw.md, bg-client-x11.md). Below.
- Third: Backgammon for the Outland Gateway (Mac, 1994-95), in adapters/outland.py (docs/research/bg-client-outland.md). The Gateway talks a binary framed link (sequence and ack numbers, DLE stuffing, a keyed 16-bit check) with a control channel and up to three game channels; Backgammon uses fixed 258-byte records. The extension speaks the link, signs the player in with the Gateway's account name and password (the password answers the server's credential question, the password or the authenticator code; the login only signs in, as Outland's did, so a name with no account is refused with a pointer to the web and telnet; a refusal shows a text window and then the Gateway's own "account not found" or "password incorrect"), lists Backgammon as the only service, and maps the lobby, challenges, the server's dice, moves, doubles offered by others, resigning, chat and the end of the game onto backgammon/1 tables. Players type the parlor's host and port 6506 into the Outland TCP Tool's settings (the tool's port field is editable; the extension's own port is 4000, as Outland's was). The lobby lists the players who are online and the bot. A challenge to another Outland player is relayed to them. A challenge to anyone else becomes an invitation through the core, and an invitation from anywhere reaches the Outland player as a challenge. Left out: watching, draws, high scores, account creation and software downloads; an Outland player's own double is refused because the client offers the cube before it shows dice the server has already rolled.
- Fourth: Grid Words for the clients of DOoM, John Chew's crossword-game server (1993 to about 2005), in adapters/doom.py on port 6507 (docs/research/clients-gridwords.md, section b). Below.
- Possible later: an outbound extension, where our client plays on a foreign server through a bridge. Not planned.
Speaks FIBS's plain-text ("telnet") mode, which MacFIBS 2.0.3, FIBS/W 1.30, xfibs 0.8 and xibc 0.31 parse, and CLIP for later clients.
ParlorNet is not FIBS: the First Internet Backgammon Server still runs at fibs.com port 4321, with its own community and ratings, and ParlorNet is not affiliated with it. The extension takes from FIBS only what the clients need to work: the protocol's message formats, the board: line, and the word counts and fixed phrases that MacFIBS, FIBS/W and xfibs match (for example ** User name authenticated., You are registered., the toggle replies and the game messages). Everything else is ParlorNet's own and says so:
- The login banner reads "This is ParlorNet's FIBS-protocol service for vintage Backgammon clients; it is not FIBS. For FIBS, the First Internet Backgammon Server, telnet to fibs.com 4321." FIBS's ASCII-art banner is not reproduced (only FIBS/W's dial-up MANUAL.SCC script waits for it; its host scripts wait for login: ).
- The guest sign-up, help, about / version, the welcome line after login and whois are in ParlorNet's words; the message of the day is the parlor's own.
- No ratings: the rating field that who, rawwho and CLIP lines need shows 0.00 for everyone, and whois says games are unrated. The "from" field shows client for players on this service and web for everyone else.
- The extension connects only to the core. It never connects or relays to fibs.com, imports no accounts, and copies no data, help text, news, rules text or bot names from FIBS.
The login line tells the session's style apart:
| Login | Clients | Session |
| connect name password (one line) | MacFIBS | no > prompts (toggle telnet NO); ** User name authenticated. starts the client's set / toggle / rawwho sequence |
| name, then password: | FIBS/W, xfibs, xibc, terminals | a > prompt after every reply and every burst of news (xfibs parses nothing until its input ends in > ) |
| login client 1008 name password | CLIP clients | numbered lines: 1-4 at login, 5/6 for who and rawwho, 7/8 log in and out, 12-19 chat; no prompts |
| guest | any | FIBS-style registration: name x, then the server's sign-up steps as prompts (under sign-up password: choose a password, type it again), You are registered. |
- Input lines may end in CR, LF or CR LF; output ends in CR LF. No telnet options are sent.
- Sign-in is generic (docs/accounts.md, the dialogue): the name alone goes to the server; the FIBS password answers its credential question (the password, the authenticator code) and is dropped if none comes; every other step is a prompt with the server's label. As on FIBS, a login only signs in (USER): a name with no account is told to log in as guest, which signs up (REG). Three refused logins close the line.
- Geometry: seat 0 of a backgammon/1 table is FIBS's O (colour 1, direction -1, home 0, bar 25) and seat 1 is X (colour -1, direction 1, home 25, bar 0), so point numbers are the same both ways. The board: line has all 53 fields; positions 0 and 25 carry X's and O's bar checkers. set boardstyle 3 is the default; 1 and 2 give a small text board.
- Commands: move 13-9 8-7 (also m, bare 13 9 8 7, bar-22, b 22, 6-off; a checker moved through several dice in one pair is split into steps), roll, double, accept / reject (a double or a resignation, by state), resign n|g|b, invite name n|unlimited (no length: resume a running match, else 1 point), join [name], decline name (ParlorNet's own addition, since FIBS has none), leave, board, pip, watch / unwatch / look, who [ready], rawwho, whois, show games|saved|watchers, tell, say, kibitz, whisper, shout, toggle, set, away / back, gag, blind, help, motd, bye. Command words may be abbreviated. Anything else gets a ** reply, so no client waits.
- Tables: invite makes a private table (NEW backgammon/1 standard match=n vis=private), sits in seat 0 and invites the other player to seat 1 (INV); join name sits down at that invitation (IVL, JON), resumes a running match with name, or joins name's open public table. Invitations made anywhere else, such as the web, telnet or IOS, arrive in FIBS's own two lines, name wants to play a n point match with you. and Type 'join name' to accept.. decline name declines one. The inviter is told when an invitation is declined or expires. invite name unlimited is a single money game (match length 9999 on the board line).
- Matches: the plugin plays the games of a match at one table. Between games the extension prints FIBS's Type 'join' if you want to play the next game ... and holds that player's output until join (the next game has already begun for the server and the web).
- Chat: say and kibitz are table chat (CHT); a table chat event shows as name says: text. tell goes straight to a FIBS session, or to the table if the name is the opponent. whisper reaches the other FIBS watchers of the table and shout every FIBS session; neither reaches the web.
- Presence: one shared task polls LST and WHO. who, rawwho and CLIP's rows list the players who are online (see "Who is online" in docs/accounts.md). The bot always shows as ready. Players who come online get a name logs in. notice (CLIP 7), and players who go idle or leave get name logs out. (CLIP 8).
- Left out: ratings and experience (0.00 and 0 are sent), redoubles, beavers, stored messages, automove and greedy (accepted as toggles; no effect), the turn clock (FIBS has none; the table's time per turn still applies). A FIBS leave only stops following the table: the game goes on and the clock runs.
Speaks the commands and wording of DOoM, a MUD for crossword games, so that BobGrid 2.3 and people at a terminal or MUD client can play gridwords/1. The sources are DOoM's help files, its English message catalogue and BobGrid's class files, read statically (docs/research/clients-gridwords.md, section b, which marks what is still unverified). ParlorNet is not DOoM; the banner and about say so.
- Connection: plain text, lines end in CR LF out and CR, LF or CR LF in; no telnet options are sent. A new connection is a numbered connector that can read help, about and who. connect name password (or co) signs in (USER); request name signs up (REG), each further step a prompt with the server's label. Three refused logins close the line. After sign-in come the message of the day between its rules and a sentence on playing the bot.
- World: one room, the Gaming Room, and a board bd_<table id> for every open or running Grid Words table (bd_<player> and a player's name find their board too). Going to a board (join bd_12, go bd_12) watches it (SEE); join there sits down (JON); home goes back (and stops watching). A player with a running game is taken to its board at sign-in.
- Board display (b, look, look bd_12), as BobGrid reads it: the column guide a b c d e f g h i j k l m n o, a border, fifteen rows with the square of column c at character 2c+1 (a tile in upper case, a blank in lower case, = - " ' for triple word, double word, triple letter and double letter), a border and the guide. From character 38: the players on rows 2 and 3 (name, the viewer's own rack with ? for blanks, score, time as MM:SS), Waiting for <name> to play. or The game is over. on row 5, the bag on row 6, the clock on row 7, Time penalties are not in effect. on row 9, and the last play. A placed play shows on the board until it is committed or undone.
- Play: place (p) takes DOoM's three forms (8d WORD across, d8 WORD down, WORD a|d 8d; lower case in a mixed-case word, _x, -x or (x) is a blank) and checks it with CHK, answering with the score; commit (c) sends MOV ... PLAY, undo (u) drops it. exchange (x, ? for a blank), pass, resign. Refusals use DOoM's sentences where it had one ("Your first play must cross H8.").
- Events: <name> plays WORD at 8D for N points., draws (<name> draws two tiles from the bag., (You now hold ...)), exchanges and passes; after each turn <name> starts the clock. and It is <name>'s turn.; at the end <name> plays out., the rack penalties, <name> ends the game. and > Final scores: .... BobGrid sends b, log2 -tagged and track -tagged after the lines that end "starts the clock.", "plays out." and "ends the game.".
- log2 [-tagged] writes two 40-character columns, one per player, with the coordinate at 8, the word at 14, the score in [29:33] and the running total in [34:38]; racks are not kept by the core, so the rack field shows dashes, which BobGrid takes for a hidden rack. track [-tagged] writes Unseen tiles: and the letters. Both go between [BEGIN] and [END] when tagged.
- Talking: " and say, kibitz (k) at a board are the table's chat (CHT); in the Gaming Room they reach the DOoM players there. 'name text and page reach DOoM players only. beep, flip, : and doing work among DOoM players.
- Invitations, ParlorNet's own addition: invite <name> (at your open board, or on a new one), accept <name>, decline <name>; invitations from anywhere arrive as one line of text. who lists the players online (the core's WHO) and the bot.
- Rules: newboard makes classic tables (six scoreless turns in a row end the game, as on DOoM); boards made elsewhere keep their ruleset. Left out: rooms and objects, the board Workshop (tws, dws, certify: every board has the standard layout), ratings, time penalties, pausing the clock, extend, challenges and withdraw (words are checked when played; ospd, ods, osw and sowpods look words up in the server's word list).
Every server extension reaches the core on its extension channel (127.0.0.1:6590 in the container): TLS 1.3 with its own pre-shared key, --core 127.0.0.1:6590 --key /data/frontends/NAME.key (the container's start script enrols each extension it starts). A server extension never checks or keeps a credential: it signs in with the name alone, relays the player's answers to the server's steps (a password the client supplied answers only a question flagged cred), and sends OUT when the player leaves (telnet, IOS, FIBS and Outland hold one connection per player). It opens that connection only once its client has sent a login line, passes the client's address with SRC (for the core's per-address limits), and counts its clients that have not signed in yet, per extension and per address, with a short time to log in (Gate in adapters/common.py), so idle connects cannot use up its share of the extension channel. The container runs everything as one unprivileged user by default; docs/security-design.md (Containment) has the opt-in separations. New server extensions follow the same rules (docs/security-design.md, what each server extension must do).
A server extension may keep a little data with each player, under its own key name, with PRF GET, SET, DEL and LST (docs/protocol.md, data kept per extension and player): at most 16 keys of up to 12 characters, values of up to 56 printable ASCII characters, 1024 bytes per player. It reads and writes only its own namespace and only for the player signed in on the connection. CoreClient has prefs(), pref_get(), pref_set() and pref_del(), and for settings load_pref(key, choices, default) (at sign-in; never fails a sign-in) and save_pref(key, value) (when the player changes it). The first user is the telnet extension's movement keys (MOVE_KEYS_PREF, MOVE_KEYS in adapters/common.py). Nothing secret goes there.
- Server extensions and bridges are the only components that know a foreign protocol; neither the core nor a game plugin does.
- A server extension can only do what a client could do; its trusted credential asserts identity but grants no extra power over games.
This doc on GitHub
| | These pages cover every ParlorNet server. | Source code | ParlorNet is free software. |