Our latest services work has focused on making channel recovery predictable, restoring community growth and applications, and giving channel owners better control through the Services Portal.

ChanFix recovery rebuilt

ChanFix now follows the established recovery model used by long-running IRC networks: it builds rolling history for authenticated channel operators and uses that history to restore trusted operators when a channel becomes opless. Recovery is add-only—ChanFix does not deop existing operators—and channels without enough history are left alone.

We also removed the behaviour that could make C appear to join unrelated channels. Automatic recovery now acts without joining unless there is a valid eligible operator, thresholds progress safely over time, service bots are excluded from scoring, and C now keeps #chanfix as its default support channel.

New F controls in the Services Portal

X owners and masters of channels protected by F now receive an F Channel Settings tab in the Services Portal. From there they can configure F's response action, warning behaviour, ban duration, flood/repeat/AMSG/URL thresholds, operator exemptions, channel badwords, and trusted account, nick, host, or mask exemptions.

Changes are applied live and persisted, so the selected behaviour survives service reconnects and restarts.

Applications, assignments, and administration

R's application handling has received additional reliability and audit improvements, including configurable F and S eligibility thresholds, clearer separation between ineligible requests and reviewed rejections, safer provisioning retries, and persistent application history.

F and S assignments now have health tracking for sustained population decline. A short dip does not remove a service; recovery resets the timer, and stale assignments are only cleaned up after a continuous 30-day decline below their configured requirement.

The Services Portal and module administration now report live module state more accurately, preserve database autojoin channels during configuration reloads, and avoid recording a module change when the live operation fails. ZNC request limits are also enforced per registered X account rather than per nickname.

Security and statistics hardening

Additional work has strengthened X authentication, session handling and recovery; made R applications more auditable; limited StatServ collection to assigned channels; improved statistics retention and comparisons; and tightened ProxyScan, TrojanScan, and HelpServ safety controls.

These changes are deployed now. If you encounter an issue with ChanFix, F protection, channel applications, or the Services Portal, please report it in #help or #support.