FlexHub Direct Connect Hub Software

FlexHub was a Lua-based Direct Connect hub created by Daywalker and FlipFlop to serve NMDC and ADC users from one server. The project used wxLua to combine the hub logic with a graphical console and detailed runtime monitoring. It was one of the more ambitious attempts to build a cross-protocol hub largely in a scripting language.

The work began as a private experiment and was later dedicated to Daywalker's memory after his death in July 2009. SourceForge registered the project on 2009/07/15, but the first public beta did not appear until 2011/01/30. Public Windows and Linux packages continued through 2012, while the SourceForge project records its last update in 2014.

FlexHub was publicly distributed, so it should not be described as unreleased. It should be described as historical beta software with an inactive upstream project. Current hubs reporting FlexHub or FlexHubBeta may use different revisions, private patches, or incomplete derivatives.

Overview And Status

Origins

The surviving README says Daywalker and FlipFlop began the project to determine whether one hub could support both NMDC and ADC. It also credits LadyStardust and other testers who helped shape the public beta. The initial work remained private for an extended period before the first public package was published.

The project description identifies Lua as the implementation language and wxLua as the GUI layer. wxLua provided access to wxWidgets controls while keeping much of the application in Lua. This let the project offer a Windows-style monitoring interface without moving the core into a conventional C++ application.

Public Beta And Release Record

FlexHub Beta 0.1 was released on 2011/01/30 for Windows XP or newer and Linux systems with X11, wxGTK, GTK2, and an X server. The first announcement described the package as the hub itself. A separate FlexGui for complete remote control was planned but not included in that initial release.

SourceForge retains a sequence of Windows and Linux builds identified by both a beta version and a source-control revision. Examples include 0.1_1055, 0.1_1065, 0.1_1075, 0.2_1236, and 0.1_1272. The apparently lower 0.1 prefix on the later revision means the source-control number must also be recorded when identifying a deployment.

The release notes show active work on malformed-message handling, failover, passive-to-passive transfers, pinger compatibility, logging, registration-only behavior, IP binding, memory use, and the GUI. These records are more useful than a generic statement that FlexHub supported two protocols because they show which parts of the implementation were still changing during the beta period.

Administration And Extension Model

The hub included commands for configuration and administration even before the proposed standalone FlexGui was released. The GUI exposed monitoring and console functions, while a no-GUI mode allowed Linux deployments to run without the desktop interface.

The project planned compatibility with the PtokaX Lua API so that existing scripts could be adapted or reused. The README also documents importing account data from YnHub and PtokaX files. Those features show that FlexHub was designed for operators migrating from established NMDC servers rather than only for new ADC deployments.

Project Status

The final public package directory contains builds dated through 2012/03/12. SourceForge lists a project update in 2014, but no current maintained release line, security policy, or active project website has been verified. The original flexhub.org support site and support-hub addresses belong to the historical project record and should not be presented as current services without a new connection check.

DCHUBLIST still observes hubs reporting FlexHub 0.2, and other public lists retain FlexHubBeta records. These observations show that the software name remains in use. They do not prove that each instance runs an unmodified public package.

Operation And Recovery

Running The Historical Packages

The Windows package was distributed as an archive containing FlexHub.exe. The Linux package bundled a Lua runtime and used FlexHub.lua as the main script. Historical command-line options included no-GUI mode, update control, profile selection, hub-owner credentials, port selection, user limits, bind address, log directory, and configuration directory.

Do not place an old package directly on a public address. Reconstruct the matching runtime in an isolated virtual machine, verify every bundled library, and compare file hashes with the SourceForge archive. Old networking and scripting dependencies may contain defects that were acceptable during the beta period but unsafe on a current internet-facing system.

Configuration And Accounts

Preserve the entire configuration directory rather than copying only the executable or main Lua file. A historical deployment may contain local scripts, profile definitions, registered-user data, bans, redirects, logs, and GUI settings that are not represented by the public package.

The README documents account import from YnHub accounts.xml and from the PtokaX RegisteredUsers.xml and Profiles.xml files. Keep the original files unchanged before testing an import. Confirm user classes, passwords, permissions, and character encoding on a private listener before accepting the imported data.

Recovery And Migration

Record the full FlexHub version and revision from the running service, package name, runtime, operating system, and all local modifications. A hub identifying itself only as FlexHub 0.2 may not correspond exactly to the archived 0.2_1236 package.

For migration, export registrations, profiles, bans, redirects, hub text, and script configuration separately. Test the replacement server on another address or port and compare login, search, chat, user classes, and scripts before changing DNS. Preserve the old environment offline until every required record has been checked.

Verified Resources

The surviving SourceForge records contain the strongest project-controlled evidence for FlexHub's history, packages, documentation, and release activity.

Related Direct Connect Reading

YnHub and PtokaX are directly relevant because FlexHub documented account imports from both servers and planned PtokaX Lua API compatibility. Their articles also provide context for the operator workflows FlexHub attempted to replace.

LuaDCH and LuaDCH-NG show later approaches to building extensible hub software around Lua. They are not FlexHub successors, but they provide a useful comparison with FlexHub's wxLua desktop design.