Hub Chat

Hub Chat is a browser-based Direct Connect client for a hub assigned to your account. It opens a live server-side session to that hub and shows connection progress, main chat, guests, private conversations, notifications, and recovery actions without requiring a separate desktop client. It is an operational client, not an anonymous public chat room: use it only for a hub you are authorized to manage.

The browser receives live updates through the event stream when it is available and falls back to polling when it is not. A refresh can recover a retained session when the same signed-in account remains authorized, but a page URL or browser storage is not a promise that a worker will survive a browser, network, deployment, or hub interruption.

Overview

Hub Chat connects with the selected hub endpoint, protocol, port, nickname, and client profile. The connection panel is the authoritative place to check whether the worker started and the hub accepted the login. Main Chat and permitted private-message controls stay unavailable until the client is connected and logged in.

Use this page to inspect a hub you manage, send a short test message when the hub account permits it, and reproduce a connection or protocol problem. It does not grant a hub role, bypass a password, open client ports, publish files, or override the hub's registration, share, and chat rules.

Overview And Availability

Anonymous visitors cannot open a hub-specific session. A signed-in user must be authorized for the selected hub under the site's Hub Chat policy; site administrators can also use the operational route. The application resolves the hub address and protocol from the hub record, then uses the configured or generated client nickname and profile. The target hub can still reject that identity, request a password, redirect it, or apply its own class restrictions.

The application prevents duplicate active sessions for the same user and endpoint. Starting another client can replace a retained session, so two tabs are not a safe way to create independent logins. If a refresh cannot recover a retained session because it was closed, expired, or is no longer authorized, open Hub Chat from the hub profile again.

Starting A Session

1. Open a hub profile assigned to your account and choose Hub Chat.
2. Review the resolved address, protocol, port, nickname, and client profile. Enter a hub password only when the hub administrator supplied it.
3. Wait for Starting, then Connected, in the connection panel. A hub can still send a password request, redirect, or rule message during login.
4. Confirm the logged-in state before sending a public message or selecting a guest.
5. Use Main Chat for public testing, or choose a guest and the envelope action for a private conversation.

If the hub rejects the login, read the visible error and, where the diagnostic panels are enabled, the redacted protocol evidence. Correct the address, protocol, nickname, password, or hub-side account before reconnecting; repeated retries do not make an invalid login valid.

Runtime Modes

Interactive is for active use: the browser renders chat, guest, raw-protocol, and private-conversation updates and uses the ordinary event-stream/polling behavior. Background, displayed as Background Low CPU, keeps the session receiving main-chat and private-message traffic but pauses the guest list, raw protocol panels, and diagnostics until Interactive is selected again.

Background Low CPU reduces browser work; it does not turn the tab into a permanently hosted desktop client or guarantee delivery after a browser, network, worker, hub, or deployment interruption. Switch to Background only after confirming the connection, then return to Interactive before inspecting guests, protocol evidence, or diagnostics. The visible connection state, not the selected runtime mode, is the evidence that the hub session is usable.

Sender And Preview Control

The notification controls affect browser notifications, not text rendered inside Hub Chat. Notification mode chooses whether the browser may alert for private messages, mentions, all eligible main-chat messages, or no messages. Content chooses whether an alert shows a preview, only the sender, or a generic hidden-content notice.

Preview is useful but can reveal hub text on a locked screen or shared computer. Sender identifies who wrote without showing the body. Hidden is safer for private or moderation-sensitive traffic. The choices are stored in browser storage when available; they do not change what the hub receives, what the worker processes, or who can access the page.

Browser Notifications

1. Select a notification mode and a sender/preview content level.
2. Choose Enable Browser Notifications and accept the browser permission prompt.
3. Move focus away from the page and send an eligible test message.
4. Select an alert to return focus to Main Chat or the relevant private conversation.

The browser reports supported, granted, denied, disabled, and unavailable states. A denied permission must be changed in browser or operating-system site settings; Hub Chat cannot override it. Private messages are eligible when notifications are enabled. Main-chat alerts follow the selected mode: All alerts on eligible public messages, while Mentions alerts only when the configured nickname is mentioned. Initial history replay and messages sent by this client are not treated as new alerts.

Restart Session And Close Session

Restart Session is for a live but unhealthy worker. It requests a controlled stop and starts a fresh worker with the saved profile, nickname, and client settings. Use it after correcting a transient worker or socket problem, not to bypass a rejected password or hub nickname rule. A restart does not make rejected credentials valid.

Before a deployment stops an active retained session, Hub Chat adds this system message to the visible conversation: This hub connection is restarting for a deployment. It will reconnect automatically when the new release is ready. The published release restarts only sessions recorded during that pause. If the restart fails, the session remains closed or shows an error so the owner can review the cause before using Reconnect.

Reconnect is available after a terminal closed or error state and starts the saved connection again. Close Session ends the active worker and hub connection and removes the normal retained-session recovery path. It is not a promise to erase messages already rendered in the browser or any separate operational evidence; treat the next live snapshot as authoritative.

Closing a browser tab is not the same as Close Session: a refresh can still recover an authorized retained session, while Close Session explicitly asks the service to stop it. A closed session can be opened again from an assigned hub profile after its endpoint and credentials have been reviewed.

Connection Panel

Hub Connection and Connection Status remain visible in every state. When the page loads while the client is Connecting, Connected, or Reconnecting, both card bodies start collapsed so the workspace stays readable; expand either header to review its settings or status.

New Hub Chat sessions use HubCHAT as the default login nickname. Their default description is HubCHAT - hublist.pwiam.com. Change it before connecting when the hub requires a registered or unique account.

The Connection Status card above the workspace is shared with Hub GPT and Hub Mod. It remains visible before a live chat opens and reports this user's saved hub-session state as Disconnected, Connecting, Connected, Reconnecting, Failed, or Stopped, together with the endpoint, nickname, worker state, connection times, and last error. The live-client badge below continues to show the current browser session.

The connection panel is collapsible to keep the workspace readable. Collapsing it hides the panel only; it does not stop the worker or discard state. The named browser states are Starting, Connected, Closing, Closed, and Error. Connected is meaningful when the worker reports both a socket connection and completed login.

Password challenges, redirects, and protocol-specific login steps are hub messages rather than separate permanent browser states. Raw Hub Response and Raw Hub Request panels are optional bounded diagnostics; outgoing passwords are redacted. Confirm TLS failures, an invalid nickname, or a rejected password from the panel message or hub response rather than guessing from a spinner.

Main Chat

Main Chat shows public messages delivered to this client, including system or hub notices alongside user messages. Rendered entries carry the sender and timestamp where the incoming event provides them. The visible history is bounded client state, not a promise of a permanent archive.

Enter a public message and choose Send. Press Enter to send; press Shift+Enter for a new line. Plain NMDC, NMDCS, and non-RTF0 connections accept up to 240 characters. An ADC or ADCS connection that negotiated RTF0 accepts up to 8,192 characters and preserves the reviewed CommonMark structures shown in Available Formatting. The composer stays disabled while the client is not logged in. Before writing a frame, the service rejects blank input, removes NUL bytes, and normalizes carriage-return line endings; only plain NMDC-family messages replace the Direct Connect frame separator with a space. A local or server-side echo is shown once and is reconciled with the hub echo, including ADC RT and timestamp parameters. If the worker rejects a send because the session closed, the hub class cannot speak, or the transport failed, review the failure message and connection panel before retrying.

Example: after Connected appears, send Hello, I am checking the hub connection. once and wait for the hub's echo or response. Do not paste an API key, account password, or long diagnostic transcript into public chat.

Guests

The Guests panel shows the hub users parsed from the current session and its reported count. Search filters the visible list by nickname without reconnecting. The table can be sorted through its visible columns and, when the hub supplied them, can show nickname, role, share, slots, client tag, IP, IPv4, IPv6, upload speed, download speed, description, and history. Selecting a guest or using the envelope action opens a private conversation when private messaging is available.

A robot icon marks a hub-reported bot and a key icon marks a hub-reported operator. The current client does not render a separate registered-user icon, so registration must not be inferred from an icon. A guest can leave while a thread stays open; its presence becomes offline, and a later reuse of the same nickname must be treated as fresh live state.

Guest Activity records joined and left events when enabled. Its header toggles the activity panel vertically without clearing recorded events. Treat the current guest list and newest event as evidence instead of assuming that two appearances of one nickname represent the same connection.

Private Conversations

Private Conversations is the workflow for starting or reviewing a direct discussion with a selected hub guest. It is not a guarantee that every guest accepts private messages; the hub, target, and connection can refuse the action.

1. Find a guest and use the envelope action or selection control.
2. Open the conversation and review Messages.
3. Enter a short private message and send it after the target and connection are available.
4. Use Conversations to return to an opened or remembered thread.

If no guest is selected, the client asks for a target. If the guest leaves, the thread can show offline and outbound delivery can fail. If the nickname no longer exists or private messages are disabled, verify the current Guests list and connection state before opening another thread.

Private Feed Messages

NMDC direct frames addressed with $To:, including messages from #_PH_FEED, belong in the private conversation for their sender. They may contain moderation, search, or operational feed events; they are not public-chat messages.

Main Chat contains only actual public frames. Hub Chat, Hub GPT, and Hub Mod tests use private messages and must never publish correlation values or system probes. If a private feed appears in Main Chat, stop further testing on that session and inspect the routing fault.

Messages

Messages is the selected private conversation's message area. It shows incoming and outgoing entries with the sender and timestamp supplied by the session. The composer stays disabled until a target is selected and the session is logged in; it rejects blank text, uses the 240-character limit for plain connections, and uses the 8,192-character reviewed CommonMark limit after an ADC or ADCS connection negotiates RTF0.

Unread state tracks incoming conversation activity and is cleared through the normal reading action. The server snapshot is authoritative after refresh; the browser may retain only short-lived optimistic actions while it waits for acknowledgment. A visible thread is not proof that all private history is permanently stored.

Conversations

Conversations is the searchable list of opened or remembered private threads. It identifies the active thread, highlights unread activity, and shows online or offline presence when known. Search matches a nickname or displayed message text without querying the hub again.

The close control dismisses a thread from the panel. It is a workspace action, not a promise to erase server-side records, audit evidence, or a guest's messages. Reopen a reachable guest with the envelope action when needed.

Reconnection And Failures

A temporary browser-stream failure can fall back to polling. A hub restart, network interruption, invalid nickname, password rejection, TLS problem, or worker failure can leave the session Closed or Error. Deployment changes can also interrupt a worker. Use the latest visible error and connection state before recovery.

Reconnect is appropriate for a terminal state after verifying the same endpoint and credentials. Restart is appropriate for a running worker that needs controlled replacement. Repeated failure is evidence of a hub-side or configuration problem, not a reason to retry faster. Close the session when testing is complete or a duplicate login is suspected.

Privacy And Logging

Hub Chat displays public messages delivered to the client and private messages in threads opened for that session. The application keeps operational session state to support authorized recovery, but this page makes no permanent-archive, fixed-retention, or deletion promise. Raw protocol panels redact outgoing passwords.

Browser notifications can expose message content outside the page when Preview is selected. Choose Sender or Hidden on shared devices. Never send passwords, OpenAI keys, recovery codes, or other sensitive information through public or private hub chat. Give diagnostic screenshots only to people authorized to administer the hub.

Hub Chat Examples

• Public check: wait for Connected, send one short greeting, and confirm the hub accepted or echoed it.
• Private check: search for a test guest, choose the envelope action, and send one non-sensitive confirmation.
• Notification check: choose Private plus Sender, grant permission, unfocus the page, and have a test guest send a private message.
• Recovery check: after a controlled hub restart leaves Closed, inspect the error, choose Reconnect once, and confirm the same nickname reaches Connected.

Hub Chat Troubleshooting

Related Pages

Use Hub to choose a hub, Hub for general hub guidance, and Hub GPT when the hub uses a configured bot instead of a user-controlled session.

Parent Page

Return to Hub for the Hub Help index and surrounding Direct Connect tools.

Configuration Reference

This reference covers the connection profile and the live controls used by an assigned hub owner.

When this page loads for an already connected client, Hub Connection and Connection Status start collapsed. Both card headers remain visible; expanding or collapsing either panel does not disconnect or reconnect the client.

When a Hub Chat, Hub GPT, or Hub Mod worker restarts, the open product page keeps monitoring the saved session and reconnects its event stream automatically; a browser refresh is not required. If a release changes the browser/server protocol incompatibly, the page stops retrying and explicitly asks you to reload before reconnecting.

A restart notice appears as a System message inside the open Hub Chat transcript, so the chat layout remains stable. When the browser and worker versions are incompatible, that System message includes the same-page reload action.

Protocol Notices And Workspace Behavior

On ADC and ADCS hubs, an IMSG can carry the hub message of the day or a connection notice. Hub Chat displays the complete text once as a Hub notice and never invents a sender for it.

A TCP socket can open even when the endpoint speaks the other Direct Connect protocol family. If an NMDC or NMDCS attempt receives an ADC handshake, Hub Chat stops it before reporting a connection and names the configured scheme. A successful connection is recorded before the hub MOTD or history that follows login. Select ADC or ADCS for an ADC hub, or NMDC or NMDCS for a legacy hub, then connect again.

When a remote hub closes without a protocol reason, Hub Chat records one clear System notice and uses bounded reconnect. An intentional Close Session remains final.

The red X closes only the selected Hub Chat workspace tab and stops that connection. It does not delete the saved public or private snapshot, related history, or another open tab.

A saved workspace tab remains visible after a worker closes, a deployment pauses it, or the connection is temporarily unavailable. Close Session disconnects only; use the red X when you explicitly want to remove that tab from this browser workspace.

The connection form belongs to the selected tab. Connect applies the edited endpoint and profile to that same session while retaining its transcript. New Connection creates a separate tab only when you choose it. Leaving the password field blank keeps the protected password already stored for that session.

ADC RTF0 Markdown Messages

On an ADC or ADCS hub that advertises ADRTF0 during login, Hub Chat displays incoming RT1 messages as formatted CommonMark and changes the shared composer to its limited rich-text toolbar. The server converts editor data to safe CommonMark and sends RT1 only while that same connection remains negotiated. NMDC and NMDCS, and ADC or ADCS hubs without the extension, remain plain text.

Press Enter to send the message. Press Shift+Enter to insert a line break. The editor grows to five visible lines and then scrolls without limiting message length. The Send button remains on the right and grows to the same height as the editor.

Choose Source to edit the canonical CommonMark behind the visual message. Paste or edit reviewed Markdown there, then choose Source again to validate and apply it; Escape cancels the source edit and restores the unchanged visual message. The same parser and safety policy run before sending, so editor markup is never submitted and unsafe raw HTML cannot bypass validation.

The reviewed subset accepts headings, hard breaks, horizontal rules, quotes, ordered and nested lists, disabled task markers, aligned tables, safe labelled links, inline code, fenced or indented code, Unicode emoji, bold, italic, and strike-through. Available Formatting contains copyable syntax examples for the exact subset.

The editor measures its rendered content and begins at the configured minimum of one line, grows to the configured maximum of five lines, and then scrolls internally. Line limits are editor properties, not CSS height rules. Its formatting toolbar opens above or below according to the available viewport space and remains available while focus stays within the editor controls. These settings do not change other editors in the application.

Open Available Formatting beside the composer for the exact reviewed CommonMark subset, syntax examples, and compatibility notes. The toolbar appears while focus remains within the editor and shows only actions that apply to the current format and selection. Safe inbound messages can also display headings, tables, task lists, hard breaks, and other supported structures.

Raw HTML, images, scripts, arbitrary attachments, and unsafe URL schemes are removed before content reaches the editor or the hub. Hub Chat permits only reviewed web, Direct Connect, and validated magnet links; it never fetches, previews, or downloads remote media automatically.

Hub Chat: Open the Hub Chat workspace to use this editor with an available ADC or ADCS connection. The repository reference docs/adc-rtf0.md records the protocol boundary, sanitizer, and exact wire-format rules.

Private Message Delivery States

An authorized operator message is tracked by its client message ID. A delivery state describes the local queue or socket write; it is not a reply from the remote user or service bot.

Private message queued for delivery.

Queued means the browser accepted the request and the worker has not yet written it to the hub. It remains pending until login and a write attempt are available.

Message written to the hub. No reply has been received.

Written means the client wrote one private frame to the hub. The recipient can still be offline, ignore it, or answer later, so this state never claims a reply.

The private message was not sent. Reconnect and try again.

Failed means the private frame was not written. The worker keeps the command available for a reconnect attempt and shows a safe System notice in the same private conversation.

Read-Only Transfer Cache

Generated hublist files shared only after hub-mediated peer authorization.

The transfer cache is disabled by default for Hub Chat, Hub GPT, and Hub Mod. Each product has an independent global switch, host, ports, connection cap, and bandwidth cap; a hub owner cannot enable it from a per-hub page.

This feature fails closed. Enabling the switch does not advertise a share until the immutable manifest, listener, advertised host, port, and any TLS files are healthy.

Settings And Defaults

Enable Transfer Cache

Allow this product to advertise its read-only generated-file cache after every health check passes. Disabled is the default.

Advertised Public Host

Public hostname or unicast IP sent to authorized Direct Connect peers. Private, loopback, local, and reserved addresses are rejected.

Plain Transfer Port

Optional NMDC or ADC peer port from 1024 to 65535. It must be unique across enabled Hub products.

TLS Transfer Port

Optional NMDCS or ADCS peer port from 1024 to 65535. TLS certificate and key paths remain environment-owned.

Maximum Concurrent Transfers

Maximum active peer connections for this product, from 1 to 32.

Bandwidth Limit In Bytes Per Second

Per-product transfer limit from 65,536 to 104,857,600 bytes per second.

Health And Advertisement

An enabled product advertises transfers only while the shared gateway has bound every configured listener and reports a current healthy state. A missing host, occupied port, unavailable TLS file, failed listener, or stale worker keeps the advertised endpoint and share disabled.

Save the transfer settings, then use Check Public Ports. It requires one running shared gateway, a fresh listener report that exactly matches the saved host and ports, stable public DNS with no private or reserved address, and a successful TCP connection to every resolved address and configured plain or TLS port. The probe sends no protocol payload. Because it originates on the application server, also verify the endpoint from an authorized external Direct Connect client when NAT or firewall hairpin behavior differs.

The gateway reads one immutable manifest generation built from approved public hublist artifacts. A generation records each published name, byte size, and TTH. A missing file, changed hash, symlink, malformed file list, or incomplete atomic publication makes the manifest unhealthy.

When both the product listener and manifest are healthy, the client profile advertises the manifest byte total, active transfer port, slots, and supported NMDC or ADC transfer capabilities. When either dependency is unhealthy, it advertises no cache share or transfer endpoint.

Discovery And Authorization

A bounded NMDC or ADC search is matched only against the current manifest. Results identify an exact published file and TTH; broad, malformed, oversized, or unrelated searches do not enumerate the server filesystem.

The hub coordinates discovery and CTM/RCM negotiation but does not proxy file bytes. The product observes the peer nickname, direction, and public endpoint through its authenticated hub session, registers a short-lived authorization, then the peer opens the separate transfer connection.

Every inbound or outbound transfer requires a recent, one-time authorization tied to the product, hub session, peer nickname, public address, direction, and expiry. Direct scanners, expired records, replay, wrong products, wrong peers, wrong addresses, and private or reserved outbound destinations are rejected.

Files And Read-Only Limits

The share contains only generated hublist downloads copied into the dedicated cache plus its generated Direct Connect file list. It never exposes arbitrary application files, source paths, uploads, remote URLs, or files outside the approved generation.

Each immutable manifest also contains HUBLIST.PWIAM.COM.md, a project-owned read-only information file. It identifies PWiAM as the host of Public DC Hublist, summarizes hub search and generated hublist files, and introduces the Hub Chat, Hub GPT, and Hub Mod products. Peers can read it with the other approved manifest entries; the application generates it and a peer cannot upload, replace, or modify it.

The gateway is download-only. It accepts only file-list and ranged download requests for exact manifest entries, rejects traversal and invalid ranges, and does not implement uploads, deletion, rename, directory creation, or arbitrary path access.

Maximum Concurrent Transfers limits active peers per product. Bandwidth Limit In Bytes Per Second applies a shared per-product rate cap. Frame size, handshake time, idle time, requested range, and authorization lifetime are also bounded so slow or oversized peers cannot hold unlimited resources.

TLS And Peer Security

The plain and TLS listeners are separate. A TLS port is advertised only when its environment-owned certificate and private-key paths are usable. Encryption does not replace hub-mediated authorization; current Direct Connect CTM messages do not carry a verifiable certificate hostname or keyprint, so peer TLS encrypts transport without asserting a public Web PKI identity.

Troubleshooting

If the share is absent, keep the product disabled and check the current manifest, advertised public host, unique public port, listener health, TLS paths, worker state, and firewall forwarding in that order. Rebuild and verify the manifest, restart the shared gateway, then test one authorized file-list request and one artifact request. Never weaken endpoint validation or accept a direct unauthenticated socket to make a test pass.

Hub Connection

Host Or Address

Enter a public hostname, IP address, or hub-style address such as dchub://example.com:411.

Protocol

Choose the hub protocol to connect with.

TCP Port

Optional. Leave empty to use the common default port for the selected protocol.

Connect To Hub

The connection form belongs to the selected tab. Connect applies the edited endpoint and profile to that same session while retaining its transcript. New Connection creates a separate tab only when you choose it. Leaving the password field blank keeps the protected password already stored for that session.

New Connection

The connection form belongs to the selected tab. Connect applies the edited endpoint and profile to that same session while retaining its transcript. New Connection creates a separate tab only when you choose it. Leaving the password field blank keeps the protected password already stored for that session.

Username / Nickname

Optional. Use your registered hub username or leave empty to generate a temporary nick like user-123456.

Hub Password

Optional. Used for registered NMDC/NMDCS nicknames when the hub requests a password.

Upload Speed

Optional upload capacity advertised in ADC and ADCS identity data. Enter an amount and unit; the protocol receives bytes per second.

Download Speed

Optional download capacity advertised in ADC and ADCS identity data. Enter an amount and unit; the protocol receives bytes per second.

Advanced Client Profile

Client Tag Name

Client name sent in NMDC and ADC identity tags.

Client Version

Client version sent in NMDC and ADC identity tags.

Connection Speed

Connection value advertised in the NMDC client tag.

Client Mode

Sets the M value in the NMDC client tag. Active sends M:A; passive sends M:P.

Fake Share

Share size sent to the hub in bytes. Use 0 to test minimum-share restrictions.

Normal Hubs

Number of normal hubs reported in the client tag.

Registered Hubs

Number of registered hubs reported in the client tag.

Operator Hubs

Number of operator hubs reported in the client tag.

Open Slots

Open upload slots reported to the hub.

TCP Port

Optional TCP listening port exposed in ADC client information.

UDP Port

Optional UDP listening port exposed in ADC client information.

TLS Port

Optional TLS listening port exposed in ADC client information.

Client Description

Optional description exposed to the hub as the diagnostic client description.

Client Email

Optional email field exposed to NMDC hubs.

NMDC Support Flags

Choose the NMDC $Supports flags sent during login. BotINFO is off by default for normal chat-client behavior.

NMDC Support Flags

Choose the NMDC $Supports flags sent during login. BotINFO is off by default for normal chat-client behavior.

• NoHello: Advertises the faster login flow in which the hub can omit a separate $Hello exchange. It is part of the normal default profile; disable it only when reproducing an older handshake. It does not authenticate the account.
• NoGetINFO: Advertises support for a fast initial user list without individual $GetINFO requests. Keep it for a normal connection; disable it only while diagnosing legacy user-list behavior.
• UserIP2: Advertises support for extended user and IP information. A hub may then send address data, so use it only when that handling is appropriate for the test. It grants no access or operator permission.
• BotList: Advertises support for the $BotList frame and bot markers in the Guests list. It is a normal default; disable it only when testing an older parser or hub profile.
• FailOver: Advertises support for hub-directed failover or redirect behavior. The flag does not make the client follow arbitrary addresses; the client connection policy still applies.
• NickRule: Advertises that the client understands nickname rules sent by the hub. It helps the client report validation correctly, but it never overrides the hub rule.
• HubURL: Advertises hub-URL exchange. When the hub sends $GetHubURL, this client sends one $MyHubURL built from the configured endpoint. Disable it only for a compatibility test.
• ExtJSON2: Advertises compatibility with extended JSON metadata. The flag does not send JSON by itself; enable it only when the hub supports the format being tested.
• BotINFO: Advertises bot-client behavior. Leave it disabled for normal chat-client behavior unless you are testing a bot-specific hub rule.
• MiniSlots: Advertises fractional slot counts in user information. It describes how the client reports slots and does not grant additional transfer capacity.
• XmlBZList: Advertises compressed XML file-list support. Enable it only when the transfer client can actually create and read XmlBZList data.
• ADCGet: Advertises the ADCGET transfer command for files, file lists, and hash-tree requests over an NMDC connection.
• TTHL: Advertises Tiger Tree leaf-list transfers used to verify file blocks before or during a download.
• TTHF: Advertises Tiger Tree Hash file transfers. The flag describes transfer compatibility and does not publish a file by itself.
• UserCommand: Advertises support for hub-provided $UserCommand menus. Enable it only when the client can receive and safely present reviewed command entries.

Status

Hub Chat

Admin-only tool that connects to a hub as a configurable diagnostic user and shows raw hub responses, chat lines, private messages, and user-list data returned during the session.

Starting

Starting hub chat worker...

Connected

Connected as %nick% to %target%. Keep this panel open until you close the session.

Closing

Disconnected from hub.

Closed

The remote hub closed the connection without a protocol reason.

Error

Could not refresh the live hub session. Retrying...

Logged In

Connected as %nick% to %target%. Keep this panel open until you close the session.

Raw Hub Response

Waiting for hub chat lines. Restriction and login messages are still available in the raw response.

Raw Hub Requests

Optional. Used for registered NMDC/NMDCS nicknames when the hub requests a password.

Connected

Connected as %nick% to %target%. Keep this panel open until you close the session.

Closed Or Filtered

Disconnected from hub.

Close Workspace Tab

The red X closes only the selected Hub Chat workspace tab and stops that connection. It does not delete the saved public or private snapshot, related history, or another open tab.

The remote hub closed the connection without a protocol reason.

When a remote hub closes without a protocol reason, Hub Chat records one clear System notice and uses bounded reconnect. An intentional Close Session remains final.

This Hub Chat session is unavailable after a restart. Its tab remains here until you dismiss it.

A saved workspace tab remains visible after a worker closes, a deployment pauses it, or the connection is temporarily unavailable. Close Session disconnects only; use the red X when you explicitly want to remove that tab from this browser workspace.

Hub Chat

On ADC and ADCS hubs, an IMSG can carry the hub message of the day or a connection notice. Hub Chat displays the complete text once as a Hub notice and never invents a sender for it.

Runtime Mode

Runtime Mode

Background Low CPU Mode is active. Main chat and private messages are still received. Guest list, raw protocol, and diagnostics are paused until Interactive mode.

Interactive

Background Low CPU Mode is active. Main chat and private messages are still received. Guest list, raw protocol, and diagnostics are paused until Interactive mode.

Background Low CPU

Background Low CPU Mode is active. Main chat and private messages are still received. Guest list, raw protocol, and diagnostics are paused until Interactive mode.

Switch To Background

Background Low CPU Mode is active. Main chat and private messages are still received. Guest list, raw protocol, and diagnostics are paused until Interactive mode.

Switch To Interactive

Background Low CPU Mode is active. Main chat and private messages are still received. Guest list, raw protocol, and diagnostics are paused until Interactive mode.

Restart Session

Restarting hub chat session.

This hub connection is restarting for a deployment. It will reconnect automatically when the new release is ready.

An active retained session shows this notice before deployment stops its worker. Only that recorded session is restarted after the published release is ready.

Reconnect

The hub session could not be reconnected from the browser.

Close Session

The hub session could not be closed from the browser.

The hub session runtime mode could not be changed.

Choose Interactive or Background Low CPU mode.

Hub Chat

Hub Chat

Press Enter to send. Press Shift+Enter for a new line. The editor grows from one line to five and then scrolls; the Send button stays on its right.

Chat Message

Press Enter to send. Press Shift+Enter for a new line. The editor grows from one line to five and then scrolls; the Send button stays on its right.

Type a public hub message...

Press Enter to send. Press Shift+Enter for a new line. The editor grows from one line to five and then scrolls; the Send button stays on its right.

Rich-text formatting is available for this ADC/ADCS connection. Messages are sent as safe CommonMark.

On an ADC or ADCS hub that advertises ADRTF0 during login, Hub Chat displays incoming RT1 messages as formatted CommonMark and changes the shared composer to its limited rich-text toolbar. The server converts editor data to safe CommonMark and sends RT1 only while that same connection remains negotiated. NMDC and NMDCS, and ADC or ADCS hubs without the extension, remain plain text.

Available Formatting

Open Available Formatting beside the composer for the exact reviewed CommonMark subset, syntax examples, and compatibility notes. The toolbar appears while focus remains within the editor and shows only actions that apply to the current format and selection. Safe inbound messages can also display headings, tables, task lists, hard breaks, and other supported structures.

Rich-text Message

On an ADC or ADCS hub that advertises ADRTF0 during login, Hub Chat displays incoming RT1 messages as formatted CommonMark and changes the shared composer to its limited rich-text toolbar. The server converts editor data to safe CommonMark and sends RT1 only while that same connection remains negotiated. NMDC and NMDCS, and ADC or ADCS hubs without the extension, remain plain text.

Rich-text formatting is not available for the current hub connection.

Raw HTML, images, scripts, arbitrary attachments, and unsafe URL schemes are removed before content reaches the editor or the hub. Hub Chat permits only reviewed web, Direct Connect, and validated magnet links; it never fetches, previews, or downloads remote media automatically.

Send

Press Enter to send. Press Shift+Enter for a new line. The editor grows from one line to five and then scrolls; the Send button stays on its right.

Waiting for hub chat lines. Restriction and login messages are still available in the raw response.

Press Enter to send. Press Shift+Enter for a new line. The editor grows from one line to five and then scrolls; the Send button stays on its right.

Enter a message before sending.

Explains that public or private Hub client commands require a non-empty message body before they can be sent.

Connect to a hub before sending messages.

Explains that you must connect before the hub can accept chat commands or messages.

Status

Explains that you must connect before the hub can accept chat commands or messages.

The message could not be queued for the active hub session.

Explains that you must connect before the hub can accept chat commands or messages.

The hub accepted this connection, but the current nick is in a class that cannot write to main chat. Use a registered hub nickname and password if you expect chat access.

Press Enter to send. Press Shift+Enter for a new line. The editor grows from one line to five and then scrolls; the Send button stays on its right.

Collapse Hub Chat

Collapses Hub Chat into a left-side rail and expands Guests to the full workspace width without closing the session.

Expand Hub Chat

Restores Hub Chat from the left rail and returns Hub Chat and Guests to their normal side-by-side widths.

Rich Text Editor

Rich Text Editor

On an ADC or ADCS hub that advertises ADRTF0 during login, Hub Chat displays incoming RT1 messages as formatted CommonMark and changes the shared composer to its limited rich-text toolbar. The server converts editor data to safe CommonMark and sends RT1 only while that same connection remains negotiated. NMDC and NMDCS, and ADC or ADCS hubs without the extension, remain plain text.

Rich-text Message Editor

On an ADC or ADCS hub that advertises ADRTF0 during login, Hub Chat displays incoming RT1 messages as formatted CommonMark and changes the shared composer to its limited rich-text toolbar. The server converts editor data to safe CommonMark and sends RT1 only while that same connection remains negotiated. NMDC and NMDCS, and ADC or ADCS hubs without the extension, remain plain text.

Write a message...

Choose Source to edit the canonical CommonMark behind the visual message. Paste or edit reviewed Markdown there, then choose Source again to validate and apply it; Escape cancels the source edit and restores the unchanged visual message. The same parser and safety policy run before sending, so editor markup is never submitted and unsafe raw HTML cannot bypass validation.

Undo

Choose Source to edit the canonical CommonMark behind the visual message. Paste or edit reviewed Markdown there, then choose Source again to validate and apply it; Escape cancels the source edit and restores the unchanged visual message. The same parser and safety policy run before sending, so editor markup is never submitted and unsafe raw HTML cannot bypass validation.

Redo

Choose Source to edit the canonical CommonMark behind the visual message. Paste or edit reviewed Markdown there, then choose Source again to validate and apply it; Escape cancels the source edit and restores the unchanged visual message. The same parser and safety policy run before sending, so editor markup is never submitted and unsafe raw HTML cannot bypass validation.

Clear Formatting

Choose Source to edit the canonical CommonMark behind the visual message. Paste or edit reviewed Markdown there, then choose Source again to validate and apply it; Escape cancels the source edit and restores the unchanged visual message. The same parser and safety policy run before sending, so editor markup is never submitted and unsafe raw HTML cannot bypass validation.

Bold

The reviewed subset accepts headings, hard breaks, horizontal rules, quotes, ordered and nested lists, disabled task markers, aligned tables, safe labelled links, inline code, fenced or indented code, Unicode emoji, bold, italic, and strike-through. Available Formatting contains copyable syntax examples for the exact subset.

Italic

The reviewed subset accepts headings, hard breaks, horizontal rules, quotes, ordered and nested lists, disabled task markers, aligned tables, safe labelled links, inline code, fenced or indented code, Unicode emoji, bold, italic, and strike-through. Available Formatting contains copyable syntax examples for the exact subset.

Strikethrough

The reviewed subset accepts headings, hard breaks, horizontal rules, quotes, ordered and nested lists, disabled task markers, aligned tables, safe labelled links, inline code, fenced or indented code, Unicode emoji, bold, italic, and strike-through. Available Formatting contains copyable syntax examples for the exact subset.

Inline Code

The reviewed subset accepts headings, hard breaks, horizontal rules, quotes, ordered and nested lists, disabled task markers, aligned tables, safe labelled links, inline code, fenced or indented code, Unicode emoji, bold, italic, and strike-through. Available Formatting contains copyable syntax examples for the exact subset.

Heading

The reviewed subset accepts headings, hard breaks, horizontal rules, quotes, ordered and nested lists, disabled task markers, aligned tables, safe labelled links, inline code, fenced or indented code, Unicode emoji, bold, italic, and strike-through. Available Formatting contains copyable syntax examples for the exact subset.

Paragraph

The reviewed subset accepts headings, hard breaks, horizontal rules, quotes, ordered and nested lists, disabled task markers, aligned tables, safe labelled links, inline code, fenced or indented code, Unicode emoji, bold, italic, and strike-through. Available Formatting contains copyable syntax examples for the exact subset.

Quote

The reviewed subset accepts headings, hard breaks, horizontal rules, quotes, ordered and nested lists, disabled task markers, aligned tables, safe labelled links, inline code, fenced or indented code, Unicode emoji, bold, italic, and strike-through. Available Formatting contains copyable syntax examples for the exact subset.

Horizontal Rule

The reviewed subset accepts headings, hard breaks, horizontal rules, quotes, ordered and nested lists, disabled task markers, aligned tables, safe labelled links, inline code, fenced or indented code, Unicode emoji, bold, italic, and strike-through. Available Formatting contains copyable syntax examples for the exact subset.

Line Break

The reviewed subset accepts headings, hard breaks, horizontal rules, quotes, ordered and nested lists, disabled task markers, aligned tables, safe labelled links, inline code, fenced or indented code, Unicode emoji, bold, italic, and strike-through. Available Formatting contains copyable syntax examples for the exact subset.

Code Block

The reviewed subset accepts headings, hard breaks, horizontal rules, quotes, ordered and nested lists, disabled task markers, aligned tables, safe labelled links, inline code, fenced or indented code, Unicode emoji, bold, italic, and strike-through. Available Formatting contains copyable syntax examples for the exact subset.

Bulleted List

The reviewed subset accepts headings, hard breaks, horizontal rules, quotes, ordered and nested lists, disabled task markers, aligned tables, safe labelled links, inline code, fenced or indented code, Unicode emoji, bold, italic, and strike-through. Available Formatting contains copyable syntax examples for the exact subset.

Numbered List

The reviewed subset accepts headings, hard breaks, horizontal rules, quotes, ordered and nested lists, disabled task markers, aligned tables, safe labelled links, inline code, fenced or indented code, Unicode emoji, bold, italic, and strike-through. Available Formatting contains copyable syntax examples for the exact subset.

Task List

The reviewed subset accepts headings, hard breaks, horizontal rules, quotes, ordered and nested lists, disabled task markers, aligned tables, safe labelled links, inline code, fenced or indented code, Unicode emoji, bold, italic, and strike-through. Available Formatting contains copyable syntax examples for the exact subset.

Decrease Indent

The reviewed subset accepts headings, hard breaks, horizontal rules, quotes, ordered and nested lists, disabled task markers, aligned tables, safe labelled links, inline code, fenced or indented code, Unicode emoji, bold, italic, and strike-through. Available Formatting contains copyable syntax examples for the exact subset.

Increase Indent

The reviewed subset accepts headings, hard breaks, horizontal rules, quotes, ordered and nested lists, disabled task markers, aligned tables, safe labelled links, inline code, fenced or indented code, Unicode emoji, bold, italic, and strike-through. Available Formatting contains copyable syntax examples for the exact subset.

Insert Table

Open Available Formatting beside the composer for the exact reviewed CommonMark subset, syntax examples, and compatibility notes. The toolbar appears while focus remains within the editor and shows only actions that apply to the current format and selection. Safe inbound messages can also display headings, tables, task lists, hard breaks, and other supported structures.

Add Row Before

Open Available Formatting beside the composer for the exact reviewed CommonMark subset, syntax examples, and compatibility notes. The toolbar appears while focus remains within the editor and shows only actions that apply to the current format and selection. Safe inbound messages can also display headings, tables, task lists, hard breaks, and other supported structures.

Add Row After

Open Available Formatting beside the composer for the exact reviewed CommonMark subset, syntax examples, and compatibility notes. The toolbar appears while focus remains within the editor and shows only actions that apply to the current format and selection. Safe inbound messages can also display headings, tables, task lists, hard breaks, and other supported structures.

Delete Row

Open Available Formatting beside the composer for the exact reviewed CommonMark subset, syntax examples, and compatibility notes. The toolbar appears while focus remains within the editor and shows only actions that apply to the current format and selection. Safe inbound messages can also display headings, tables, task lists, hard breaks, and other supported structures.

Add Column Before

Open Available Formatting beside the composer for the exact reviewed CommonMark subset, syntax examples, and compatibility notes. The toolbar appears while focus remains within the editor and shows only actions that apply to the current format and selection. Safe inbound messages can also display headings, tables, task lists, hard breaks, and other supported structures.

Add Column After

Open Available Formatting beside the composer for the exact reviewed CommonMark subset, syntax examples, and compatibility notes. The toolbar appears while focus remains within the editor and shows only actions that apply to the current format and selection. Safe inbound messages can also display headings, tables, task lists, hard breaks, and other supported structures.

Delete Column

Open Available Formatting beside the composer for the exact reviewed CommonMark subset, syntax examples, and compatibility notes. The toolbar appears while focus remains within the editor and shows only actions that apply to the current format and selection. Safe inbound messages can also display headings, tables, task lists, hard breaks, and other supported structures.

Toggle Header Row

Open Available Formatting beside the composer for the exact reviewed CommonMark subset, syntax examples, and compatibility notes. The toolbar appears while focus remains within the editor and shows only actions that apply to the current format and selection. Safe inbound messages can also display headings, tables, task lists, hard breaks, and other supported structures.

Delete Table

Open Available Formatting beside the composer for the exact reviewed CommonMark subset, syntax examples, and compatibility notes. The toolbar appears while focus remains within the editor and shows only actions that apply to the current format and selection. Safe inbound messages can also display headings, tables, task lists, hard breaks, and other supported structures.

Align Cell Left

Open Available Formatting beside the composer for the exact reviewed CommonMark subset, syntax examples, and compatibility notes. The toolbar appears while focus remains within the editor and shows only actions that apply to the current format and selection. Safe inbound messages can also display headings, tables, task lists, hard breaks, and other supported structures.

Center Cell

Open Available Formatting beside the composer for the exact reviewed CommonMark subset, syntax examples, and compatibility notes. The toolbar appears while focus remains within the editor and shows only actions that apply to the current format and selection. Safe inbound messages can also display headings, tables, task lists, hard breaks, and other supported structures.

Align Cell Right

Open Available Formatting beside the composer for the exact reviewed CommonMark subset, syntax examples, and compatibility notes. The toolbar appears while focus remains within the editor and shows only actions that apply to the current format and selection. Safe inbound messages can also display headings, tables, task lists, hard breaks, and other supported structures.

Link

Raw HTML, images, scripts, arbitrary attachments, and unsafe URL schemes are removed before content reaches the editor or the hub. Hub Chat permits only reviewed web, Direct Connect, and validated magnet links; it never fetches, previews, or downloads remote media automatically.

Remove Link

Raw HTML, images, scripts, arbitrary attachments, and unsafe URL schemes are removed before content reaches the editor or the hub. Hub Chat permits only reviewed web, Direct Connect, and validated magnet links; it never fetches, previews, or downloads remote media automatically.

Enter a safe link URL

Raw HTML, images, scripts, arbitrary attachments, and unsafe URL schemes are removed before content reaches the editor or the hub. Hub Chat permits only reviewed web, Direct Connect, and validated magnet links; it never fetches, previews, or downloads remote media automatically.

Emoji

The reviewed subset accepts headings, hard breaks, horizontal rules, quotes, ordered and nested lists, disabled task markers, aligned tables, safe labelled links, inline code, fenced or indented code, Unicode emoji, bold, italic, and strike-through. Available Formatting contains copyable syntax examples for the exact subset.

Source

Choose Source to edit the canonical CommonMark behind the visual message. Paste or edit reviewed Markdown there, then choose Source again to validate and apply it; Escape cancels the source edit and restores the unchanged visual message. The same parser and safety policy run before sending, so editor markup is never submitted and unsafe raw HTML cannot bypass validation.

Edit the clean source content...

Choose Source to edit the canonical CommonMark behind the visual message. Paste or edit reviewed Markdown there, then choose Source again to validate and apply it; Escape cancels the source edit and restores the unchanged visual message. The same parser and safety policy run before sending, so editor markup is never submitted and unsafe raw HTML cannot bypass validation.

The source could not be applied safely. Review it and try again.

Raw HTML, images, scripts, arbitrary attachments, and unsafe URL schemes are removed before content reaches the editor or the hub. Hub Chat permits only reviewed web, Direct Connect, and validated magnet links; it never fetches, previews, or downloads remote media automatically.

Guests

Guests

No guest list has been returned yet.

Search Guests By Nickname

Search guest nickname...

Nickname

Search guest nickname...

Role

Search guest nickname...

Share

No guest list has been returned yet.

Client

No guest list has been returned yet.

IP Address

No guest list has been returned yet.

Tag

No guest list has been returned yet.

IPv4

No guest list has been returned yet.

IPv6

No guest list has been returned yet.

Upload Speed

No guest list has been returned yet.

Download Speed

No guest list has been returned yet.

Description

No guest list has been returned yet.

History

No guest list has been returned yet.

Operator

Search guest nickname...

Bot

Search guest nickname...

Message

Choose a guest before sending a private message.

Guest Activity

No guest activity yet. Join and leave events will appear here.

joined

Guest Activity

left

Guest Activity

Collapse Guests

Collapses Guests into a right-side rail and expands Hub Chat to the full workspace width.

Expand Guests

Restores Guests from the right rail and returns both panels to their normal side-by-side widths.

Private Conversations

Private Conversations

No messages yet. Use the envelope button beside a guest to start one.

Messages

Type a private message...

Private Chat: %nick%

Type a private message...

Private Message

Choose a guest before sending a private message.

Type a private message...

Choose a guest before sending a private message.

Send

Choose a guest before sending a private message.

Conversations

Search nickname or message...

Search Private Conversations

Search nickname or message...

Message

Choose a guest before sending a private message.

Close Private Chat

No messages yet. Use the envelope button beside a guest to start one.

Unread Messages

Type a private message...

Guest Online

No messages yet. Use the envelope button beside a guest to start one.

Guest Offline

No messages yet. Use the envelope button beside a guest to start one.

Private messaging is disabled for this hub chat session.

No messages yet. Use the envelope button beside a guest to start one.

The private message could not be queued for the active hub session.

Explains that you must connect before the hub can accept chat commands or messages.

Private message queued for delivery.

Queued means the browser accepted the request and the worker has not yet written it to the hub. It remains pending until login and a write attempt are available.

Message written to the hub. No reply has been received.

Written means the client wrote one private frame to the hub. The recipient can still be offline, ignore it, or answer later, so this state never claims a reply.

The private message was not sent. Reconnect and try again.

Failed means the private frame was not written. The worker keeps the command available for a reconnect attempt and shows a safe System notice in the same private conversation.

Browser Notifications

Browser Notifications

Choose a notification mode, then enable browser permission.

Enable Browser Notifications

Choose a notification mode, then enable browser permission.

Disabled

Browser notifications are not available in this browser.

Private Messages Only

Choose a notification mode, then enable browser permission.

Mentions + Private Messages

Choose a notification mode, then enable browser permission.

All Messages

Choose a notification mode, then enable browser permission.

Notification Content

Choose a notification mode, then enable browser permission.

Show Sender And Preview

Choose a notification mode, then enable browser permission.

Show Sender Only

Choose a notification mode, then enable browser permission.

Hide Message Content

New hub chat message.

Private message from %nick%

Choose a notification mode, then enable browser permission.

Mention in %hub%

Choose a notification mode, then enable browser permission.

Message in %hub%

Choose a notification mode, then enable browser permission.

Browser notifications are enabled.

Choose a notification mode, then enable browser permission.

Notifications are disabled.

Choose a notification mode, then enable browser permission.

Notification permission is blocked in browser settings.

Choose a notification mode, then enable browser permission.

Browser notifications are not available in this browser.

Choose a notification mode, then enable browser permission.

Error

System

A restart notice appears as a System message inside the open Hub Chat transcript, so the chat layout remains stable. When the browser and worker versions are incompatible, that System message includes the same-page reload action.

The hub worker is restarting. This page will reconnect automatically.

When a Hub Chat, Hub GPT, or Hub Mod worker restarts, the open product page keeps monitoring the saved session and reconnects its event stream automatically; a browser refresh is not required. If a release changes the browser/server protocol incompatibly, the page stops retrying and explicitly asks you to reload before reconnecting.

This hub connection could not be restored automatically. Reload the page to reconnect.

When a Hub Chat, Hub GPT, or Hub Mod worker restarts, the open product page keeps monitoring the saved session and reconnects its event stream automatically; a browser refresh is not required. If a release changes the browser/server protocol incompatibly, the page stops retrying and explicitly asks you to reload before reconnecting.

This page is using an older live-client version. Reload the page to reconnect.

When a Hub Chat, Hub GPT, or Hub Mod worker restarts, the open product page keeps monitoring the saved session and reconnects its event stream automatically; a browser refresh is not required. If a release changes the browser/server protocol incompatibly, the page stops retrying and explicitly asks you to reload before reconnecting.

Reload This Page

When a Hub Chat, Hub GPT, or Hub Mod worker restarts, the open product page keeps monitoring the saved session and reconnects its event stream automatically; a browser refresh is not required. If a release changes the browser/server protocol incompatibly, the page stops retrying and explicitly asks you to reload before reconnecting.

Could not refresh the live hub session. Retrying...

Explains that you must connect before the hub can accept chat commands or messages.

The chat session security token expired. Refresh the page and connect again.

Explains that you must connect before the hub can accept chat commands or messages.

The hub session could not be closed from the browser.

Explains that you must connect before the hub can accept chat commands or messages.

The hub session could not be reconnected from the browser.

Explains that you must connect before the hub can accept chat commands or messages.

The hub session could not be restarted from the browser.

Explains that you must connect before the hub can accept chat commands or messages.

The hub session runtime mode could not be changed.

Choose Interactive or Background Low CPU mode.

Icon Reference