Conversational Real-Time Text¶
Show participants the unfinished text of an ongoing conversation in successive updates before its writer completes a message or line.
Core Idea¶
Conversational real-time text, in this entry's bounded sense, lets another participant see the words of an ongoing conversation while the writer is still composing them. The text arrives in successive partial updates before a line is finished or a Send action completes a message. The reader can therefore respond to an evolving utterance, not only to a completed turn. T-Mobile describes this behavior for compatible RTT calls, while an original Talkomatic implementer describes characters appearing as typed in a group channel.[1][2]
The common operation does not require a phone, a particular packet format, or exactly two people. A supported direct mobile call and an early multiwriter PLATO channel differ in service, participant arrangement and display design. They share the narrower relation unfinished composition → incremental transmission → participant-side partial display → possible response during composition.[1][2] The definition names a response opportunity, not a claim that every reader actually interrupted or that the two systems had equal latency.
The word “real-time” is contextual. Neither source establishes a universal millisecond limit, zero delay, or a common standards implementation. The decisive test is whether the other participant can read actual partial text before a conventional complete-message boundary. A rapid completed-message exchange can be conversational without satisfying this entry.
Structural Signature¶
Sig role-phrases: continuing conversation; unfinished text composition; precompletion updates; participant-side partial display; response opportunity during composition.
- Continuing conversation. The text has other current participants who can respond. T-Mobile's case is a supported call between compatible users; Talkomatic's is a shared channel with multiple active writers.[1][2] A one-way caption feed or solitary editor lacks this role.
- Unfinished text composition. A participant is still forming a line or message. The identity concerns this ongoing authorship, not merely the later delivery of a finished unit.
- Precompletion updates. Successive characters or partial words become available before a final Send or line-completion boundary. T-Mobile says the other person sees text as it is typed; Woolley says Talkomatic transmitted characters instantly as typed instead of waiting for the whole line.[1][2]
- Participant-side partial display. Actual evolving text reaches the interlocutor's screen. A “someone is typing” indicator reveals activity but not words. Talkomatic allocated separate screen windows to simultaneous writers, keeping their partial contributions distinguishable.[2]
- Response opportunity during composition. A reader can use the partial words to begin a response before the writer completes the unit. The opportunity follows from the documented display mechanics; it is not a measured frequency of interruption in either system.
The roles form one interaction relation. Text could be transmitted character by character to a server but hidden until Send; that would fail participant-side display. A shared editing screen could show partial words without participants addressing each other in a conversation; that would fail the conversational role.
What It Is Not¶
It is not identical to all instant messaging. The live Instant Messaging entry covers network services organized around rapid message turns; unfinished words need not appear before submission. Talkomatic's group chat can overlap that category and this one.[2] The supported T-Mobile example is an answered and ended RTT call with text visible during composition, rather than evidence that every such call requires an instant-messaging service or discrete message turns.[1] The precompletion display relation is the differentia here.
It is not a typing indicator. An indicator may let a reader anticipate a message without revealing any partial text. It is not live audiovisual caption delivery: captions represent speech or sound in a program interval, whereas this entry tracks words a conversational participant is composing for other participants. It is not automatically text relay: the reviewed BT Relay UK service involved an assistant and a real-time text channel, but the consulted service note did not establish whether the assistant saw an unfinished utterance before a submit or turn boundary.[3] That case remains a held neighbor rather than a positive instance.
The name also does not assert use of T.140, RFC 4103, or another shared telecom protocol. The positive PLATO and mobile service descriptions support interaction behavior, not protocol equivalence.
Scope of Application¶
The positive evidence spans a direct supported mobile RTT conversation and a historical online group chat. T-Mobile describes RTT-to-RTT use on compatible VoLTE or Wi-Fi calls and simultaneous voice and text where supported.[1] Woolley, who says he helped expand Talkomatic, describes characters appearing as typed in separate participant windows; Hody's 1974 PLATO user report independently describes an operating shared display for five geographically scattered participants.[2][4]
These settings establish literal reach across two mediated-conversation arrangements. They do not establish that every current chat application, emergency call, relay service, textphone, or caption system has this exact partial-display behavior. Compatibility, member count, transport and accessibility purpose can vary. The inclusion question is behavioral: does the other participant see the unfinished words in time to converse around them?
Clarity¶
Three phrases often blur together: “fast messages,” “typing awareness,” and “text visible as typed.” They answer different questions. Fast messages reduce delay after submission; typing awareness shows that composition is happening; this process reveals the composition itself. The difference is observable by asking whether the receiver can read a letter or word that the sender has not yet committed as a completed message.
The two cases sharpen what remains constant. In a direct RTT call the reading and writing occur between two compatible endpoints. In Talkomatic several people could write simultaneously; separate windows kept their text attributable.[1][2] Neither a phone number nor a group room is required by the shared identity. What matters is a receiver's access to actual partial content during active conversation.
Manages Complexity¶
A communication system can mix input editing, network carriage, addressing, display and conversational turn-taking. The five roles let a curator or designer locate the exact behavior without equating all low-latency text services. If partial updates leave a sender's device but the other person's interface holds them until completion, the break is at display. If text appears on a shared screen but cannot be tied to a participant, attribution becomes the design problem. If it appears during audiovisual playback as captions of program speech, the represented object has changed.
Talkomatic's horizontal windows illustrate one implementation choice for simultaneous writers, not a rule for every real-time-text system. Woolley reports that each channel could have up to five active participants and additional monitors.[2] That limit says something about this interface and screen allocation; it is not a universal upper bound on the abstraction.
Abstract Reasoning¶
Let \(x_i(t)\) denote participant \(i\)'s text composition at time \(t\), and let \(v_j(x_i,t)\) mean that another participant \(j\) can view an unfinished prefix of it. A positive case has some \(t\) before the writer's conventional completion point for which \(v_j\) is true. The reader need not send a response at that instant; the interaction design must make such a response possible. This is a diagnostic model, not either source's network algorithm.
Remove any one role and the classification changes. If \(x_i\) is not being composed by a conversational participant, it may be captions or a live data feed. If only a status indicator is sent, \(v_j\) contains no words. If all content stays hidden until completion, the system may be fast chat but not partial-text exchange. If a server sees updates but no participant sees them, there is no receiver-side conversational visibility.
Knowledge Transfer¶
The same literal behavior can move from a carrier-supported call to a multiuser computing channel. The phone path involves compatible call endpoints and optionally simultaneous voice; Talkomatic used a shared PLATO channel and separate writer windows.[1][2] The mechanism transfers because unfinished composition reaches interlocutors before conventional completion. Its transport protocol, membership model and display layout do not transfer as requirements.
Outside mediated conversation, seeing an unfinished draft can be analogous, but analogy is insufficient. A collaborative document may expose keystrokes without participants treating those updates as conversational turns. A program caption may update continuously but represents audiovisual source content rather than a participant's unfinished utterance. Those boundaries keep the entry domain-specific.
Examples¶
Canonical: direct mobile RTT conversation¶
T-Mobile describes RTT for compatible users during supported calls: text appears to the other person as it is typed, without waiting for an entire message to be sent.[1] It also describes simultaneous voice and text for supported situations.[1] This is an operator account of an available service, not a published trace of one named call or a guarantee for every device pairing.
Mapped back: continuing conversation → two compatible call participants; unfinished composition → one user's typed words; precompletion updates → text shown as typed; partial display → the other endpoint's RTT screen; response opportunity → the reader can react before a completed message. The source does not specify quantitative latency, packet format, or a required voice channel in every use.
Applied: PLATO Talkomatic group channel¶
Woolley says Talkomatic transmitted characters as typed, rather than waiting for a finished line.[2] He describes several horizontal participant windows so multiple people could type at once without their text becoming jumbled.[2] A contemporary PLATO user, Hody, describes Talkomatic as a shared screen on which five participants could each write and erase four lines, including participants at different locations.[4] Hody corroborates operation and group display; Woolley's later implementer account supplies the character-level detail.
Mapped back: continuing conversation → one group channel; unfinished composition → each active writer's current line; precompletion updates → characters transmitted before line completion; partial display → a shared screen divided into writer windows; response opportunity → other active writers can see and answer the evolving contribution. Monitors who only watched were not active writers and need not satisfy every writer role. Neither source supplies a packet trace or a universal response-time measurement.
Structural Tensions¶
T1 — Immediate visibility versus revision before exposure. The defining precompletion display gives another person the chance to react early. It also makes provisional spelling and wording visible while the writer is still deciding what to say. The latter cost is an analytic consequence of exposing partial text, not a measured user outcome in the two reports. Waiting until Send permits more private revision but crosses the identity boundary into completed-message exchange. Diagnostic: Which characters can another participant read before the writer has committed the message?
T2 — Simultaneous group writing versus readable attribution. In Talkomatic, separate windows enabled several people to type at once while keeping their contributions apart.[2] More concurrent writers increase the need for screen space and attribution; fixed windows limit how many active contributions fit. This trade-off belongs to Talkomatic's group design, not every two-party RTT call. Diagnostic: Can a reader follow whose unfinished text is changing when several people compose simultaneously?
Structural–Framed Character¶
This is a mixed, communication-framed process. Evaluative weight: the mechanism is describable without declaring early exposure good, but its usefulness is judged by whether participants can understand and respond to evolving words. Human-practice dependence: composition, turn-taking and the choice to answer partial text belong to human conversation; the relation cannot be reduced to a network packet stream. T-Mobile describes a direct call, and Woolley describes active Talkomatic writers plus non-writing monitors.[1][2]
Institutional origin: telecommunications accessibility and early online community supplied different implementations, but neither one owns the complete identity. Vocabulary travel: “unfinished utterance” and “partial display” travel literally across direct calls and group chat; outside conversations they may be mere analogies. Import versus recognition: apply the name only when another participant sees actual unfinished text before completion, not because a product advertises low latency, displays a typing indicator, or calls its channel real time. The portable skeleton is progressive exposure of a changing representation, but its cross-domain status remains a future-Prime question pending full-signature evidence. Its character: a domain-bound conversational interaction whose delivery mechanics are structural enough to recur across unlike services, while human composition and reply opportunities remain constitutive.
Structural Core vs. Domain Accent¶
What is skeletal: a changing representation becomes available to a consumer before the producer declares it finished. That broad pattern might recur beyond conversation, and its wider cross-domain identity remains a future-Prime question. The directed dependence between a writer's actual unfinished update and another participant's visible partial words is an internal Coupling constituent: in a functioning session, emitting rather than withholding an update changes the displayed prefix before completion.[1][2] This is an analytic contrast grounded in the two described behaviors, not a measured experiment or universal latency claim. Flow may cover movement of information, but its full source–sink, rate and continuity signature has not been shown necessary here.
What is domain-bound: conversational participants compose words, view each other's unfinished utterances, and may answer before completion. A telephony RTT interface and Talkomatic's group display implement that relation differently.[1][2] Replacing those participants with a dashboard, sensor stream, or audiovisual caption feed changes the recognition test.
Why this is not a prime: the named mechanism remains anchored to addressed conversation and human text composition. The two operating cases broaden it within communication, not across unrelated substrates. Coupling is a typed internal constituent, while the entire precompletion text relation beyond conversation remains a question for a different candidate. The staged edge awaits the exact post-edit and physical graph checks before canonical release.
Instantiates / Related Primes¶
This entry includes Coupling.
Coupling is a typed internal constituent of the staged mechanism: when a writer emits rather than withholds an unfinished update in a functioning session, another participant's visible partial words change before completion.[1][2] This local influence is a curatorial causal inference, not a measured coefficient or a claim that the reader must answer. The complete child additionally requires an ongoing conversation, human unfinished words, successive updates, participant-side partial display and response opportunity. Flow remains a comparison for movement of character information without an approved all-role transport-rate, source–sink and continuity proof. Concurrency can help analyze Talkomatic's simultaneous writers, but is not all-instance for direct RTT calls. The Coupling edge awaits post-edit and physical graph validation before canonical release.
Relationships to Other Abstractions¶
Current abstraction Conversational Real-Time Text Domain-specific
Parents (1) — outgoing typed relations
-
Conversational Real-Time Text includes Coupling Prime
Precompletion changes in a writer's text affect another participant's visible partial words, a directed Coupling constituent of conversational real-time text.Conversational real-time text contains distinguishable writer-side composition/transmission and participant-side display activities. In a functioning supported T-Mobile RTT call and the described Talkomatic group channel, a writer's newly emitted unfinished characters become part of another participant's actual visible partial text before the line or message is complete. Holding the receiving operation and other updates fixed, emitting one such update rather than withholding it changes whether those characters appear in the reader's visible prefix before completion; substituting different characters changes the corresponding visible content. This update-specific binary content difference specifies a directed, nonzero local influence on the precompletion timescale, not a measured coupling coefficient or universal latency number. The offered-service and retrospective accounts support the behavior; the causal contrast is curatorial inference. They do not establish a shared protocol, receiver buffer or alternate route. A reader's response is possible, not required by this relation. The complete child also requires ongoing conversation, unfinished composition, successive updates, partial display and response opportunity. The cross-case Coupling classification is a curatorial inference.
Hierarchy path (1) — routes to 1 parentless root
- Conversational Real-Time Text → includes Coupling
Neighborhood in Abstraction Space¶
Conversational Real-Time Text sits in a moderately populated region (59th percentile for distinctiveness): it has near-neighbors but no dense thicket of look-alikes.
Family — Language, Mind & Meaning-Making (69 abstractions)
Nearest neighbors
- Tautophrase — 0.85
- Fixed-Response Question — 0.85
- Live Timed Caption Delivery — 0.85
- Dialogical analysis — 0.85
- Narrative Thread — 0.84
Computed from structural-signature embeddings · 2026-10-25
Not to Be Confused With¶
Instant Messaging is a network messaging-service neighbor. Talkomatic's group channel can overlap its message-turn pattern, while IM need not expose unfinished words.[2] T-Mobile describes an answered RTT call with as-typed text, without establishing that an IM service is necessary for every such call.[1] Typing indicators reveal ongoing composition without conveying its text. Live Timed Caption Delivery attaches later text cues to an audiovisual program's timing rather than exposing a participant's unfinished words to interlocutors. The cited BT Relay UK service remains a held text-relay neighbor under the partial-word test explained above.
References¶
[1] T-Mobile, “T-Mobile accessibility”, Real-Time Text (RTT) section, consulted 22 October 2026. First-party operator description of compatibility-limited direct RTT service, text visible while typed, and simultaneous voice/text where supported; no quantitative performance or protocol trace. registry ↩a ↩b ↩c ↩d ↩e ↩f ↩g ↩h ↩i ↩j ↩k ↩l ↩m ↩n ↩o
[2] David R. Woolley, “PLATO: The Emergence of On-Line Community”, 1994, “Talkomatic and Term-Talk” section. First-person implementer recollection of the operating Talkomatic channel, character updates before line completion and multiwriter window design; the 1994 account is retrospective. registry ↩a ↩b ↩c ↩d ↩e ↩f ↩g ↩h ↩i ↩j ↩k ↩l ↩m ↩n ↩o ↩p ↩q ↩r
[3] British Telecommunications plc, “Relay UK Service Description”, Suppliers' Information Note 359, issue 1.11, October 2023, pp. 2–5. Operator description of a text/voice relay-assistant service; does not establish unfinished-text visibility before a submit boundary, and later service migration limits any inference about current platform internals. registry ↩
[4] G. L. Hody, “PLATO IV: A User's Overview”, 1974 ADCIS presentation, zero-based PDF pp. 6–7. Contemporary PLATO user report corroborating operating five-person Talkomatic shared display; does not itself document character-level transmission. registry ↩a ↩b