LoginSign Up
← Back to all sparks
E

Ergo

COMMS
Velocity2.5

Modern IRC server written in Go with built in services

ergo.chat ↗

Ergo keeps tracking IRCv3 upstream while quietly opening its history layer to real databases.

ircircv3self-hostedrelease-candidateshistory-backends
◆Current state
Ergo ships roughly two releases a year, each announced as a release candidate about a week ahead of the final. The content is consistent: whatever IRCv3 specifications have firmed up since the last cycle, plus bug fixes and config-format adjustments. The one structural change in this window was pluggable history storage, which took Ergo off its embedded database as the only option.
◆Where it's heading
This is a project with a stable release ritual and a narrow remit: be a modern IRC server that implements the spec correctly and runs as a single binary. Feature work arrives as specification support rather than product invention. The exception is the operational surface — history backends and the HTTP API — where Ergo has been steadily making itself easier to run alongside existing infrastructure instead of as a self-contained island.
◆Prediction
The v2.19.0 final should follow its release candidate within a week or two on the established pattern; the config-format break flagged in that RC is the main thing operators will need to handle on upgrade.

◆Recent moves

  1. 22d ago

    v2.19.0-rc1: IRCv3 updates and a breaking config change

    The v2.19.0 release candidate carries IRCv3 specification updates, fixes and minor enhancements — the usual shape of an Ergo cycle. Notable for operators because one config-file change is not backwards-compatible, so this upgrade needs reading before applying.

    View source ↗
  2. 4mo ago

    v2.18.0-rc1 adds PostgreSQL and SQLite history backends

    ⚡ SPARK

    The release that broke Ergo's storage assumption: history can now live in PostgreSQL or SQLite instead of only the embedded store, and the HTTP API grew alongside it. It is the one change in this window that alters how Ergo is deployed rather than what it supports.

    View source ↗
  3. 7mo ago

    v2.17.0-rc1 implements the IRCv3 metadata specification

    v2.17.0 picked up the IRCv3 metadata specification via an outside contributor, alongside fixes and minor updates. Spec conformance arriving through community contribution is the normal way Ergo's feature surface grows.

    View source ↗
  4. 1y ago

    v2.16.0-rc1: bug fixes and minor updates

    A maintenance cycle: bug fixes, minor updates and fully backwards-compatible config additions. Nothing here changes what the server does.

    View source ↗