Read DC Clients and DC Hublists for detailed guidance on choosing clients and working with public Hublist files.
How Direct Connect Works
Direct Connect brings people together through hubs, client software, and public hublist files. A hub coordinates public chat, user lists, and searches. Files usually move directly between clients, so neither a hublist nor a hub normally carries the files being shared.
The client and hub must support the same protocol family. NMDC and NMDCS are the established Direct Connect protocols, while ADC and ADCS use the newer protocol family. The secure variants use TLS, so the advertised address and the client settings must agree before a connection can succeed.
Finding Public Hubs
A public hublist is a directory of hub endpoints, not a promise that every listed hub is online or accepting new users. Names, user counts, share figures, and availability are snapshots that can change before you connect.
For the difference between searchable hub directories and downloadable list files, read the Hublist Landing Page. Check the protocol, encryption option, and hub rules before joining a result from any list.
Joining A Hub
Choose a client that supports the hub protocol, set a recognizable nickname, and read the topic and rules after connecting. Review shared folders before opening them to others, avoid folders with private documents, and use the client connection mode that works with the local network.
Operating A Public Hub
Hub operators should publish an accurate address, protocol, TLS availability, category, and contact information. Test the hub from a separate connection, keep the description current, and remove stale endpoints instead of leaving users to guess which address works.
What This Section Covers
The related articles below examine client selection, public hublist sources, and hub software in greater detail. Start here when you need the basic relationship between a client, a hub, and a public listing before moving into a specific setup or operating task.