History

Jean 9d6cf3bb08 nickserv: split into one file per command Mirrors the chanserv layout: nickserv.rs keeps the service and dispatch, each command (register, identify, logout, cert) lives in its own file with its subcommands and parameters. Behaviour is unchanged.		2026-07-12 14:05:59 +00:00
..
chanserv	chanserv: require channel-operator status to register	2026-07-12 13:57:29 +00:00
nickserv	nickserv: split into one file per command	2026-07-12 14:05:59 +00:00
protocol	chanserv: require channel-operator status to register	2026-07-12 13:57:29 +00:00
README.md	Move the ChanServ MODE command into modules/chanserv/mode.rs	2026-07-12 10:46:27 +00:00

modules/

The pluggable parts of fedserv: one directory per protocol and per pseudoclient. The core (engine, event log, gossip, link loop) stays in ../src/.

modules/
  protocol/     ircd link protocols   (inspircd.rs)
  nickserv/     NickServ pseudoclient
  chanserv/     ChanServ pseudoclient

src/main.rs pulls each in with #[path = "../modules/..."], so crate paths stay flat (crate::proto, crate::nickserv, crate::chanserv).

Naming

A service directory holds its pseudoclient file plus, as commands are split out, one file per command: register.rs, mode.rs, etc.