Converse, direct messages, and notifications on CADR and Genera

The whole visible facility is a pop-up receiver

The System 46 lmio/chsaux.113 source defines the direct-message substrate but not the later conversation editor. QSEND is a macro that quotes its destination and optional message and expands to SEND-MSG; the arguments therefore are not ordinary evaluated function arguments. SEND-MSG forces a user login, opens the Chaosnet SEND contact, writes a sender-and-time header followed by the body, and returns NIL on success or an error string on failure.

A destination containing @ is split at the last at-sign. Its person part is uppercased and its host part is parsed as the remote machine. A destination without an at-sign is treated as a host and addressed to anyone. If no message argument is given, an input editor reads the body until End, either encoded Control-C form, or end of input.

The receiver listens on the same SEND contact. It accepts an explicitly named recipient from the request or uses anyone, appends its local heading, then copies the remote first line and body directly into the extensible string SAVED-SENDS. It closes the transport only after the copy and then appends two returns. A read failure can therefore leave partial history and an open registered connection; history is not a commit-at-EOF transaction. Completed messages are retained in arrival order. PRINT-SENDS writes the entire string and returns true.

The user sees a reusable pop-up text window named QSend, 400 pixels high—described in source as about seventeen lines. It beeps twice by default, displays the new message, and asks whether to reply. A yes answer invokes SEND-MSG back to the derived sender; a no answer dismisses the window. A global lock admits only one message interaction at a time. Only a waiter's first failed lock attempt can report to the current notification stream, and only when the shared pop-up is not already selected. On normal completion the owner clears the lock and yields; it deselects and deactivates only if no successor acquired the lock during that scheduling opportunity. The closed connection is removed from the active registry after the message slice displays and before the reply query, so display and reply failures have different cleanup states.

This is the complete System 46 source-visible user surface:

The file contains no cold-initialization reset and no file writer for SAVED-SENDS. It is therefore safe to call the history memory-resident; it is not safe to infer the exact lifetime of the object across every kind of world save from this file alone.

A release-bounded absence

A full-text audit of the pinned System 46 source found no Converse frame, Converse command table, SHOUT, NOTIFY, or NOTIFY-ALL-LMS implementation. This is an important version boundary: the direct-message protocol and received-message buffer predate the editor that later organized those messages into conversations. The absence claim is limited to this public snapshot and is not a claim about all MIT Lisp Machine software ever produced.

A structured Zwei buffer, not a transcript window

The maintained System 303 io1/conver.lisp identifies Converse as a network message facility written by Cliff Lasser in 1982. It runs a CONVERSE-FRAME containing a single Zwei pane. The visible buffer begins with a headerless To: composer. Each established peer has another To: template, messages are separated by thin black diagram lines, and conversations are separated by thick ones.

The black lines are structural objects. Each conversation retains its own first and last lines, active To: boundary, peer identity, insertion mode, and OLDMSGS history. Commands recover the conversation from line ownership rather than reparsing the visible heading. Editing across a divider can invalidate those relationships; Regenerate Buffer rebuilds them from recorded messages but discards unsent edits.

System 303 groups a conversation by exact user@host. Sending to several comma- separated recipients creates a separate message copy and a separate conversation record for each recipient. A bare user name causes Converse to search logged-in Lisp Machines plus *CONVERSE-EXTRA-HOSTS-TO-CHECK*; one match is selected directly and several matches open a host-choice menu.

Incoming network work does not edit the Zwei buffer from the network process. Requests are queued on the frame and drained by its command loop and post-command hook. This source-visible boundary explains how a message can arrive while the user is editing or stopped in a break loop without letting the receiver mutate editor state concurrently.

Complete System 303 direct bindings

The table inherits the standard Zwei command table, so normal motion, killing, yanking, filling, and searching remain available when they do not damage the structural lines. No Converse-specific mouse command table is installed. The only source-defined menus in this path are the ambiguous-destination chooser and the choices in the incoming-message pop-up.

Complete System 303 named commands

Write and Append are the only persistence operations in this application source. There is no automatic transcript file.

Delete Conversation also has a strict source-profile edge defect. The command calls DELQ without assigning its returned list head. Deleting a non-head conversation can splice the list in place, but deleting the initial headerless composer leaves the old head in *CONVERSE-LIST* and then deletes that conversation's interval. A safe reimplementation can prohibit deletion of the composer or store the returned head, but either choice is an explicit correction rather than maintained-source identity.

Receiving modes and options

The documented receive modes are:

The receiver also accepts :POP-UP as an alias for :SIMPLE, but the option's own documentation lists only the four values above. This is a source-visible extension, not an additional documented System 303 choice.

There is a second, less benign discrepancy. The :NOTIFY-WITH-MESSAGE branch passes the message body as the only argument to a format string whose visible wording says “received from”. The documented behavior says the notification includes both sender and body, but the pinned implementation omits the sender and places the body after “from”. This probable formatting defect has not been exercised against a peer.

The simple window is 400 pixels high and labeled Incoming Message. Its full local choice set is:

One-shot QSend, replies, and saved sends

(QSEND) selects the Converse frame. With a destination but no message it opens an input editor; End and Control-Z finish, Abort quits, Control-Meta-Y yanks the last received body, and Control-Meta-E transfers the unfinished text to Converse. With WAIT-P false, QSend starts a background sender and immediately returns NIL; with it true, it waits and returns the successfully reached recipients.

Unlike raw SEND-MSG, QSend records outgoing success or failure in the appropriate Converse conversation. (REPLY) uses the most recent sender. QSENDS-OFF and QSENDS-ON control whether the inbound server accepts further messages.

Ordering differs by entry path. An in-frame multi-recipient send attempts and records in comma-input order, but each new peer block is inserted immediately after the headerless composer, so all-new blocks appear in reverse creation order. Out-of-frame QSend pushes resolved recipients: its wire attempts and delayed record requests run in reverse input order, while pushing successes again restores their original relative order in the synchronous return. Zero-argument REPLY with no last sender delegates to destinationless QSend and merely selects Converse. In the mail path, a failure reason from an unresolved recipient can remain attached to a later successful mail record because the per-recipient local is not cleared.

System 303 still retains the compatibility *SAVED-SENDS* history separately from the full editor. Incoming messages are prepended to that string, so PRINT-SENDS prints the newest received message first—the reverse of System 46. The initial source binding is an empty extensible string, but before-cold stores NIL. The first receive after that reset coerces the old value to the literal suffix NIL, and an immediate post-reset PRINT-SENDS passes non-string NIL to the stream; the latter result remains a runtime oracle. Before any receive, direct editor Control-Meta-Y likewise inserts literal NIL, whereas the transient QSend reader inserts no bytes. The yank text comes from *SAVED-SENDS*, whereas *LAST-CONVERSE-SENDER* supplies only the default reply destination. The selected before-cold initializer does not assign that sender register, so invoking that operation retains its prior value; this does not establish persistence through every possible cold-boot or world-loading mechanism.

System 303 does not have one aggregate “cold reset” here. Cold initialization alone clears gag state; one before-cold action clears saved sends; another calls the frame finder (creating a missing frame and ensuring its process has a run reason) before clearing the request queue; and :ONCE constructs/activates the comtab and frame. None of these selected operations resets receive mode.

Help and command-table mismatches in the maintained source

The executable End and Control-End handlers, the dynamic mode-line text, and the System 94 release note agree: with the default option, End sends and remains while Control-End sends and exits. The hard-coded COM-CONVERSE-HELP prose says the opposite. It is stale documentation inside the application itself.

The same Help text omits the direct Control-Z cell. More importantly, that cell names COM-CONVERSE-SEND-WITH-EXIT, while the selected System 303 source tree defines only the ordinary function CONVERSE-SEND-WITH-EXIT; a whole-tree search found no command definition or alias for the installed target. Its name reveals the intended operation, but its effective runtime result remains an exact oracle rather than a claimed working send path. These are release-source findings, not inferences from a modern keyboard mapping.

Entry points and the display model

Genera registers Converse both as an activity and as Select C. It can also be entered from the System menu, by invoking the activity, by calling (ZL:QSEND) with no destination, or by choosing C in an incoming-message pop-up.

The visible model remains recognizably descended from the System 303 editor:

• a blank headerless To: composer is kept at the top;
• thick diagram lines separate conversations and thin lines separate messages;
• normal Zmacs editing is available within message text;
• outgoing, incoming, and failed-send records are retained since cold boot; and
• Regenerate Buffer reconstructs the structure from those records while losing unsent edits.

The grouping rule is broader than System 303. A Genera conversation can own a recipient list treated as a set, with Also-to: metadata and a message identity. The strict comparator first requires equal lengths and then checks whether every candidate address matches some existing address, without consuming matches. It is therefore order-independent but not true multiset equality: [A,A] can compare equal to [A,B]. A corrected recreation must label a consuming multiset comparator as a deviation. Group sends can otherwise remain one multi-recipient conversation rather than being copied into one conversation per recipient. Addresses are canonicalized through the namespace system. Giving name@host avoids the bare-name search; an unqualified name can require a host choice.

The default divider heights are three quarters of a text line for the thick conversation header and one quarter for a message divider. These are configurable source values, not estimates from a screenshot.

Complete Genera Converse direct bindings

The complete local Control-X subtable is:

Both tables inherit their standard Zmacs counterparts. No Converse-specific mouse menu is installed in the inspected source; ordinary inherited editor gestures still apply.

Complete Genera Converse named commands

Commented encryption command cells are not commands. They are intentionally excluded from this available-surface inventory.

The built-in Help describes the send/exit keys dynamically and correctly, but it is not a complete command census. It omits Meta-Q, all five local Control-X window commands, the three explicitly undefined Z chords, and the Compile, Load, Hardcopy, Bug, and Report Bug extended commands. This is precisely why the command table must be audited in addition to the manual.

Sending, delivery feedback, and incoming choices

Genera sends from Converse in a background process. The editor first inserts a temporary “being sent” or “being mailed” record, then replaces that header with the success or failure result. If the frame is hidden, delivery failures become notifications. The failed attempt remains part of the conversation history. Mailing from Control-M uses the subject [Failing Converse message].

Before sending, the code checks canonical recipients, local service state, the receiver's availability, and whether styled or non-thin text requires protocol support. If interactive receiving or the relevant services are disabled, the user can decline, send anyway, or enable service as applicable. This validation and the transient status record are source-visible behaviors that the concise Help does not fully expose.

Listener-level QSend uses the Command Processor input editor and a dedicated message-string history so large bodies do not pollute ordinary string completion. Both End and Control-End activate the body. QREPLY snapshots the most recent recipient set and message identity before sending, preventing a newly arriving message from retargeting a reply halfway through the operation. The public QSend entry remains a macro that quotes its optional destination and message, preserving the historical “arguments are not evaluated” calling convention.

The ordinary incoming pop-up is 400 pixels high and labeled Incoming Message:

For a message marked encrypted, the first choice set is Decrypt (D/d), Converse (C/c), or Nothing (N/n/Rubout); after decryption the normal reply choice follows. The temporary window deactivates through the surrounding window-mouse interaction.

Receive modes and protocol content

The old auto-expose and notify-with-message variables remain only as compatibility inputs and are translated into *CONVERSE-MODE* when a message arrives.

When Converse is already visible, the message is inserted there. Arrival beeps are performed directly when Converse is visible or the mode is Auto or Pop-Up; Notify modes rely on the notification path rather than duplicating that direct beep.

Genera still accepts the old Chaosnet SEND service, but its newer CONVERSE protocol can transmit the date, sender, primary recipient, additional recipients, message identity, private-delivery flag, encryption marker, notification marker, character-type mappings, fonts, and the message body. Private delivery checks the logged-in user name. No logged-in user, a mismatched private recipient, or a gagged receiver causes rejection. Property names are case-insensitive. The server accepts repeated normally-singleton lines with last-write-wins rather than rejecting them; missing Date defaults to current time, while missing From or To falls into downstream address operations rather than a clean required-field error.

A message carrying the protocol's notification property deliberately bypasses *SAVED-SENDS*, last-reply state, and every Converse conversation. It goes directly to TV:NOTIFY with sender, date, and trimmed body. This early branch does not hide the body when the encryption property is also present; it is distinct from the hidden-frame notify-with-message mode above. The same wire service can therefore carry either a conversation message or an asynchronous notification without merging their histories.

Three histories and their lifetimes

Genera exposes three related but nonidentical records:

The Converse reset clears saved sends, then the most recent recipient set, and only then looks for an already existing frame. If one exists, it sets the conversation list NIL and destructively rebuilds the interval as exactly one fresh headerless To: composer, moves point to the new first-line end, and requests redisplay. It does not reset *LAST-IDENT*, the frame request stack, or receive/gag/layout policy; those exact values survive this operation even though no blanket reboot-persistence claim follows. Failure has no rollback, so earlier clears or partial frame rebuilds remain. Write and Append commands are manual exports, not a background transcript service.

Send Message

The Command Processor command accepts one or more address presentations, defaults to the most recent Converse recipients, forces login, prompts for a body, canonicalizes addresses, and uses the ordinary QSend path. It therefore receives the same background-delivery feedback and Converse recording as listener-level QSend.

Complete Show Messages keyword surface

If Query becomes true, the implementation turns Summarize off because the combination is meaningless. The command accepts a Start type whose minimum is one; its later unless start fallback to zero is therefore defensive code that normal argument acceptance cannot reach.

Show Messages ordering mismatch

Installed Help defines Forward as most-recent-first. The implementation always pushes new OLDMSGS entries, so the stored list itself is newest-first. The report then conditionally reverses that list based on each conversation's display append mode, and pushes each selected entry onto a result list:

Thus a display-layout option changes the report's interpretation of Forward. This is a static source derivation and a high-priority runtime follow-up, not yet an observed Genera transcript.

Record, queue, and delivery order

A notification is a three-field record: universal time, a presentation-recording string, and an optional window of interest. TV:NOTIFY pushes the record onto NOTIFICATION-HISTORY, making index 0 the newest, and wakes one central delivery process. The process walks list tails so that delivery remains first-in/first-out even though the retained history is newest-first.

For each console, delivery first offers the record to the selected stream's notification protocol. The stream gets three seconds to accept it. A notification mode can force the result:

Any other post-timeout mode is treated as a notification-protocol error. Remote terminals are offered the same notification; if they do not accept it, the system uses stream-style output.

The delivery process can wait up to twenty seconds for a selected window to appear or for a newly spawned pop-up to become selected. That selection timeout is separate from the three-second opportunity given to an already selected stream.

*ALLOW-POP-UP-NOTIFICATIONS* defaults true. Setting it false retains and indicates notifications without opening fallback pop-ups. The display formatter has distinct ordinary, stream, window, and pop-up styles.

Pop-up behavior and a stale timing comment

The notification pop-up is intentionally the same 400-pixel height as the Converse pop-up. Immediately after selection it waits three seconds before treating typein as a dismissal request. During that interval, ordinary characters are forwarded to the previous window; Abort forces the pop-up down. After the interval, any character dismisses it except Help, which replaces the content with the local explanation. A mouse-button input can select the recorded window of interest. The window can also feed that interest into the system's background-window selection path.

New notifications arriving while the pop-up is active replace the flush prompt and are appended into the same temporary display. An inactive pop-up automatically deactivates after fifteen minutes by default.

When a notification carries a window of interest, a mouse click on the pop-up can select that window. The same association makes it available through the system's Function-0-S background-interest selection history.

The source comment says pop-ups should be separated by five seconds, but the actual constant is 600 ticks and the same implementation divides ticks by 60 when waiting: the executable value is ten seconds. This is an internal source/comment mismatch; the value is derived from code and has not yet been timed in the VLM. The delivery process keeps this timestamp independently per console and prunes each association after its interval; a pop-up on one console does not throttle another console.

PRINT-NOTIFICATIONS accepts numeric endpoints, treats the most recent entry as 0, clips or swaps confusing ranges, and prints newest-first. Its cursor side effect is broader than the visible subset: To limits the count, but the state test and assignment use the full list tail beginning at From. Thus printing only item zero can move the delivery cursor to the history head, update the TV notification tick, and mark other unprinted pending records delivered.

Converse is a full-screen editor with a structural starting line

Select C immediately exposed the Converse activity. Its fresh buffer was almost entirely blank except for the To: template and black structural separator at the top. The mode line identified Converse (Text) and summarized the three most important lifecycle controls: End sends without leaving, Abort exits without sending, and Control-End sends and exits. No peer, address, or message was entered.

Runtime observation — Genera 8.5 System 452.22, session d09-converse-notifications-genera-20260718, generation 2, verified 2026-07-18 after local login and Select C. The reviewed 1200 by 900 PNG has SHA-256 8a8360166f24aa0d0e6b2ce2df29c9e3f3ac0ad963b2af93e5d78208dabff043 and normalized-pixel SHA-256 425d5c9c3b353fa7bb93aa824c1b85a55cbb44e4989da1841ccad8b2c6566bc9. It establishes only the fresh layout and short labels, not message delivery, command effects, or source-to-world identity. Symbolics and other applicable rightsholders retain interests in the licensed screen; this minimum image is published under the page-specific reviewed fair-use conclusion for historical criticism and reconstruction, and no endorsement is implied.

The local Help dispatcher opened successfully and described conversation grouping, the send/exit bindings, navigation, file export, listener QSend operations, and user options. That raw Help screen remains ignored because its substantial installed prose is not needed once its behavior has been checked against source. It also confirmed the article's source finding that Help is useful but not a complete command census.

Notifications is a separate retained-history viewer

Select N opened a distinct application: a title pane, a left-scrollable typeout pane, and only Help and Exit in its fixed menu. It was initially empty. After the Listener called TV:NOTIFY with pop-ups disabled, returning to the activity showed exactly one timestamped line containing the synthetic museum text. This establishes in the compiled world that TV:NOTIFY retains a record centrally and that the Notifications activity reads that history even when fallback pop-ups are disabled. It does not by itself prove the source-defined live polling interval or the ordering of multiple records.

Runtime observation — Genera 8.5 System 452.22 in the same session and generation, verified 2026-07-18 after the researcher-authored TV:NOTIFY call and Select N. The reviewed 1200 by 900 PNG has SHA-256 8b9d2ed2c941eb23f344a37f839757d46e9a5e7b97aebf4780dc1af4518b7592 and normalized-pixel SHA-256 3819127ac6504aa52c226e1118a52d91ba46b301bad9b9ec365bc55acdb99d74. It establishes one retained synthetic record while fallback popups were disabled, not multi-record ordering, popup timing, or network receipt. Symbolics and other applicable rightsholders retain interests in the licensed screen; this minimum synthetic-data image is published under the page-specific reviewed fair-use conclusion for historical criticism and reconstruction, and no endorsement is implied.

Both images passed the capture-specific review in the screenshot publication policy. The first contains only functional layout and short labels; the second adds one researcher-authored record. The full Help screen, login screen, Listener transcript, and initially empty Notifications duplicate remain untracked. Exact raw mappings and image identities are in the curated Genera screenshot catalog.

The final generation-2 run record is 26,055 bytes, SHA-256 1ffacb2809fa4aee90e12fb7ff65413d1e443e0471adc82e1af2265743ad15f7. The 14-record action log is 6,881 bytes, SHA-256 742d8554f5273038b99e555d1262afbbbdb4dc2f0096f2a55f1357d7827eec03. The shutdown prompt was observed and accepted and cleanup began; the known Cold Load channel mutex stall then required bounded host termination. Final status is forced-stopped, with forced_after_confirmed_shutdown_stall=true, state_may_be_incomplete=true, and orderly_vlm_host_shutdown=false. The base and private worlds remained byte-identical, the harness invoked neither Save World nor a process checkpoint, unsaved Lisp state was discarded, and no session process remained.

The peer-dependent boundary remains

The harness has no configured Lisp Machine peer. This run therefore does not claim delivery, reply identity, multi-recipient grouping, broadcast behavior, duplicate filtering, or Converse history ordering. A later peer-enabled experiment must use a deliberately isolated, disposable site; it must not fabricate a peer or infer network behavior from these two local application states.