Skip to content
Dialova

IRC Documentation · Advanced

IRCd Software: Ergo, InspIRCd, UnrealIRCd and others

An IRCd is the server software that receives IRC connections and applies network rules. The choice depends on the desired architecture, necessary services, and the ability to maintain the configuration; no software alone guarantees a safe community.

Dialova Team · Verified on

Architectures to Compare #

ProjectDocumentation OverviewQuestion to Consider
ThereforeGo-based server integrating accounts and bouncer functionsDo you want to group these functions on the server?
InspIRCdModular architecture and module documentationWhich modules correspond to the network you administer?
UnrealIRCdConfigurable server, with modules and protectionsHow do you configure and maintain protections and services?
SolanumIRCd developed with the participation of networks' teams like Libera.Chat and OFTCDoes your architecture and your skills match this project?
ngIRCdPortable server particularly oriented towards limited-size networksAre the documented functions sufficient for your need?

These descriptions are not an exhaustive compatibility matrix. Available features depend on the version, compiled modules, services, and effective configuration.

Evaluate a deployment #

  • Verify the maintenance of the chosen version and the update procedure.
  • Define account management, channel management, backups, and operator rights.
  • Verify TLS, authentication mechanisms, and each useful capability.
  • Test throughput limits, interrupted connections, and behavior during a restart.
  • Do not expose an administration console or binding secrets in a public configuration.

An example configuration from another network may load different modules or use incompatible modes. Channel modes and rank prefixes must be discovered from the server in question.

The software is not the network. #

Ergo is a software; Dialova is a service with its own configuration and web functions. Solanum is a software; Libera.Chat is a network. A project's characteristics should not be automatically attributed to all its deployments.

Sources & Verification

Examples use pseudonyms and fictional domains, except for explicitly documented connection points. Network-specific extensions and settings are noted in the text.