Hub

Hub Profile Overview

A hub detail page shows live information collected from the hub plus application-owned fields such as owner, status, address links, reliability, and history.

Description And Topic

The description and topic are usually reported by the hub during ping. Treat them as hub-owned content that can change after the next hourly update.

Hub History Graph

The graph records pinger snapshots for one hub over time. A point is not a live measurement from the browser: it is the value stored after a completed scheduled check. Public visitors can compare guests, total share, and average share per user. Administrators can additionally inspect stored numeric settings, ping counters, reliability, votes, limits, clone data, and status trends.

Read The Time Range Before Comparing Values

Use the range selector to choose the period that answers the question. A short range is useful after a restart, address change, or unexplained outage. A longer range shows repeated failures, gradual user changes, and whether a reliability change is a pattern rather than one missed check. Gaps do not mean zero users or zero share. They usually mean that no successful snapshot was stored for that point.

Timestamps, Retention, And Reconnects

Dates and times use the application display timezone. The graph reflects retained records, so an older point can remain visible after a hub is edited, moved, renamed, or temporarily unavailable. A reconnect can create a later snapshot but does not rewrite earlier measurements. The Last Checked and Last Available fields in the details table provide the current operational context for the newest point.

Use The Graph With The Profile, Not In Isolation

Open Hub for the selected hub profile and use Hubs to find another entry when you need a comparison. Check the connection addresses, protocol, status, and software beside the graph before drawing a conclusion. A TCP listener, TLS certificate, or protocol question needs the matching diagnostic tool; the history graph shows stored hublist observations, not proof that a client login will succeed at this moment.

Troubleshooting A Missing Or Surprising Line

If a series is absent, first verify that the hub was checked successfully during the selected period and that the metric is available to your role. A sudden change can follow a hub configuration change, a temporary network failure, or data reported differently by the hub software. Compare the current details and user list, then return after the next scheduled check. Do not use the graph to identify individual users or to infer private activity.

Hub Details

The details table explains address, secure address, added time, last checked time, last available time, location, encoding, status, owner, software, category, reliability, share, and requirements.

Join Requirements

Min Share is the minimum shared size a user must have to join. Min Slots is the minimum open upload slots required. Max Hubs blocks users who are already joined to more hubs than the configured limit.

Connection And TLS Icons

The secure shield means the address uses TLS, such as NMDCS or ADCS. The unsecure shield means the address is plain NMDC or ADC.

Guests

The Guests panel shows the hub's current user-list snapshot. It is a live presence view rather than a durable identity record: a nickname can leave and reconnect later. Use the current count and listed rows when confirming access; the role-icon meanings are documented below.

User List Icons

The user list is parsed from the hub userlist snapshot. A blue user icon marks a registered or recognized user entry when the hub exposes that role. A silver robot marks a bot or service account, such as feed bots, security bots, clock bots, hublist bots, or automated announcement users. A gold key marks an operator, moderator, or privileged hub account. Rows without an icon are ordinary users. Administrators may also see raw role values.

The hub profile and live hub chat intentionally use the same role language: blue is a user role, silver robot is a bot/service role, and gold key is an operator role. If a bot is also an operator, the application prioritizes the bot/service marker where the user list is specifically identifying automated accounts.

Icon Reference