Add ReportServ, wired into the audit trail
Any user can REPORT <nick|#channel> <reason>; filing is rate-limited per reporter. Reports are an event-sourced, federated queue operators review with LIST / VIEW / CLOSE / DEL. The interconnection: because a filed report is an event, the engine's audit feed already announces it to the staff channel and records it in the searchable action log — so OperServ LOGSEARCH finds a report by any word in it, tying reports into the same trail as bans, kicks, and everything else. Opt-in (add "reportserv").
This commit is contained in:
parent
8d495a948e
commit
5b023c22a4
9 changed files with 346 additions and 9 deletions
8
Cargo.lock
generated
8
Cargo.lock
generated
|
|
@ -336,6 +336,7 @@ dependencies = [
|
|||
"fedserv-memoserv",
|
||||
"fedserv-nickserv",
|
||||
"fedserv-operserv",
|
||||
"fedserv-reportserv",
|
||||
"fedserv-statserv",
|
||||
"hmac",
|
||||
"pbkdf2",
|
||||
|
|
@ -431,6 +432,13 @@ dependencies = [
|
|||
"fedserv-api",
|
||||
]
|
||||
|
||||
[[package]]
|
||||
name = "fedserv-reportserv"
|
||||
version = "0.0.1"
|
||||
dependencies = [
|
||||
"fedserv-api",
|
||||
]
|
||||
|
||||
[[package]]
|
||||
name = "fedserv-statserv"
|
||||
version = "0.0.1"
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue