OFTC: the quieter home of free software IRC

OFTC — the Open and Free Technology Community — is the other free-software IRC network. Founded in 2001 and operated under the umbrella of Software in the Public Interest, it is the long-time home of Debian, the Tor Project, and a constellation of infrastructure-minded projects that prefer its quieter, more conservative culture to the bigger Libera.Chat.

Connecting #

• Server: irc.oftc.net, port 6697 with TLS.
• Help channel: #oftc.
• Webchat: available via the network's site for a browser-only start.

Registration: one notable difference #

NickServ registration works as you expect (general guide) — with one historical quirk worth knowing: OFTC has long emphasized client certificate authentication (CertFP) alongside passwords. You generate a TLS client certificate, connect with it, and associate its fingerprint with your account:

/msg NickServ CERT ADD

After that, connecting with the certificate identifies you automatically — no SASL configuration, no password in your client config at all. Many OFTC regulars consider this strictly nicer than passwords; it also works on Libera and other networks as SASL EXTERNAL, but OFTC is where the practice is most at home.

Culture and policy #

OFTC is smaller than Libera by an order of magnitude, and channels skew toward project work over socializing. Moderation is low-drama; policies are short. If Libera is the bustling capital of FOSS IRC, OFTC is the university town — and for the projects based there, that is precisely the appeal.

Which channels live here #

Debian's entire channel family (#debian and its many spin-offs), Tor (#tor), and a long tail of system, kernel-adjacent and infrastructure projects. When documentation says "on OFTC", believe it — the same channel name on Libera may be an unofficial mirror or empty. As always, the project's own docs are the authoritative pointer.

Practical note for dual citizens #

Most FOSS contributors end up on both networks. Register the same account name on each (registrations are per-network), let your bouncer or client hold both connections, and the distinction disappears into your channel list.