What The Edit Page Controls
The hub edit page lets owners and administrators maintain contact details, display opacity, pinger identity, and administrator-only synchronization fields. Help text under each field should be kept translated in every supported language.
Owner And Public Fields
Owner, email, website, country, name, topic, description, software, encoding, and URL fields describe how the hub is shown publicly. Some values are read-only because the hourly pinger refreshes them from the hub itself.
Appearance Fields
Background Opacity controls how strongly the hub background logo appears. Panel Opacity controls transparent panels on the hub page, including the description, history graph, detail table, and user list.
Pinger Fields
Pinger Nickname, Pinger Password, and Pinger Share define the account used by the hourly pinger when it connects to the hub. These values should match what the hub allows for automated checks.
Administrator Fields
Status, banned state, ban reason, custom URL, protocol override, address, secure address, port, ping counters, ADC flag, and vote counters are operational fields. Changing them can affect listing visibility, generated hublist files, reliability, and migration sync.
Field Reference
| Field | Purpose |
|---|---|
| Owner / Email / Website | Identify the maintainer and optional contact or public website. |
| Country / Encoding | Control location filters and text compatibility. |
| Name / Topic / Description | Usually pinger-owned content shown on the public hub page. |
| Background Opacity / Panel Opacity | Control visual transparency without changing stored hub data. |
| Pinger Nickname / Password / Share | Define the automated account used for hourly checks. |
| Status / Banned / Ban Reason | Control whether the hub appears publicly and why it may be restricted. |
| URL / Protocol / Address / Secure Address / Port | Control connection identity, custom slug, and generated hublist output. |
| Pinged / Failed / ADC / Votes | Store operational counters used for reliability and legacy compatibility. |