History

Jean fbcf0eaac7 nickserv: email confirmation (CONFIRM) on registration When email is configured and a REGISTER includes an address, the account starts unverified and a confirmation code is emailed. CONFIRM <code> verifies it (a federated AccountVerified event); INFO shows an unconfirmed email until then. Emailed codes now carry a purpose (reset vs confirm).		2026-07-12 15:36:30 +00:00
..
chanserv	nickserv: add INFO and ALIST	2026-07-12 14:19:29 +00:00
nickserv	nickserv: email confirmation (CONFIRM) on registration	2026-07-12 15:36:30 +00:00
protocol	email: outbound mail subsystem and RESETPASS	2026-07-12 15:28:15 +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.