echo/modules
Jean 8ed1a9ab70
modules: capability-scoped Store/NetView boundary (Tier 2)
Services no longer receive the concrete account store. on_command now takes
&mut dyn Store + &dyn NetView (both defined in fedserv-api); the engine's Db
and Network implement them. Reads hand back plain views (AccountView,
ChannelView, ...) carrying only non-secret fields, so the event log, gossip,
and credential material (password hash, SCRAM verifiers) are unreachable from
a module. All command modules ported; behaviour unchanged.
2026-07-13 01:04:07 +00:00
..
chanserv modules: capability-scoped Store/NetView boundary (Tier 2) 2026-07-13 01:04:07 +00:00
nickserv modules: capability-scoped Store/NetView boundary (Tier 2) 2026-07-13 01:04:07 +00:00
protocol modules: extract fedserv-api leaf crate (protocol + service vocabulary) 2026-07-13 00:36:42 +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.