Introduction to our IRC network

Our IRC network can be accessed with an IRC client on irc.f-hub.org via port 6697 (SSL only). It runs on the modern IRCv3 capable IRCd Ergo.chat. It therefore comes with built in history and multi-client connections out of the box and no additional bouncer is required. We also fully integrate with XMPP and Matrix via our own gateways that allow federated access to any IRC channel.

Registering accounts

Accounts from F-hub.org are automatically registered on our IRC network can can be used to authenticate via SASL login. In addition it is possible to register independent accounts through NICKSERV like on other IRC networks. Please contact us in those rare cases where there is a conflict with an existing user account name.

Bouncer functionality

Once registered you can connect with multiple clients to the same account like common with IRC bouncers. Our Ergo IRCd tries to emulate ZNC to some extend in that regard. You can also enable persistence via the persistent connection mode: /msg NickServ set always-on true

Channel history

Channel history is automatically logged by the network itself (via IRCv3 history standard) and stored for 30 days. It can be easily accessed by history capable IRC clients or alternatively via /history #channel 6h or similar, pleae see the full guide here.

IRC tutorial

If you are new to IRC, please refer to our IRC tutorial that explains basic features and commands.

Recommended clients

IRCv3 capable clients are strongly recommended for accessing our network and we provide easy to use web-clients. You can learn more about our recommended IRC clients here.

Helper bot

We run a helpful little bot that can be invited to any channel via /invite bot. Type @help to ask the bot for instructions. You can learn more about it on our dedicated wiki page here.

Gateways

Our IRC network also offers gateway access from federated XMPP and Matrix accounts. Please note that due to the federated nature of these systems chat-logs may be stored for a longer period on connected third party servers and the gateways themselves.

Connecting from Tor

Due to repeated abuse we automatically filter all connection attempts against IP addresses of Tor exit nodes and other known abusive source IPs via automated real-time block lists. As a result many Tor exit node IPs are blocked and the remaining ones require SASL account authentification on connection.