Rolfsvaag_Datateknikk/Lumi
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
experimental-okf
Lumi/knowledge/plugins/moderation.md
Franz Rolfsvaag 32ec0a102f Advance experimental OKF and Lumi AI systems
2026-06-25 14:10:04 +02:00

6.2 KiB
Raw Permalink Blame History

id title scope status priority visibility category tags generated editable updated_at
plugin.moderation Moderation Center plugins active 10 user Plugin plugin, moderation true false 2026-06-25T12:06:11.231Z

Moderation Center

Cross-platform moderation actions, notes, and sanctions.

Metadata

Plugin ID: moderation Version: 0.1.4 Default state: enabled

Web Routes

  • /plugins/moderation
  • GET /plugins/moderation/status
  • GET /plugins/moderation
  • GET /plugins/moderation/tos-bans
  • GET /plugins/moderation/evidence/:id
  • POST /plugins/moderation/actions
  • POST /plugins/moderation/actions/:id/update-timeout
  • POST /plugins/moderation/actions/:id/revoke
  • POST /plugins/moderation/notes
  • POST /plugins/moderation/notes/:id/delete

Route Reference

MOUNT /plugins/moderation

  • Purpose: Mounts the plugin router at this base WebUI path.
  • Inputs: No request parameters detected by static analysis.
  • Response format: Plugin router mount point.
  • Access: Access is controlled by the mount options and individual plugin routes.
  • Side effects: No direct route action; child routes handle requests.
  • Limits/notes: Mount metadata is inferred from static source scanning.

GET /plugins/moderation/status

  • Purpose: Renders or serves the moderation plugin page for status.
  • Inputs: No request parameters detected by static analysis.
  • Response format: HTTP redirect after handling the request
  • Access: logged-in session required or used
  • Side effects: Usually read-only.
  • Limits/notes: Generated from static route source analysis; confirm exact behavior in the handler before changing integrations.

GET /plugins/moderation

  • Purpose: Renders or serves the moderation plugin page.
  • Inputs: No request parameters detected by static analysis.
  • Response format: HTML page rendered from an EJS view; HTTP redirect after handling the request
  • Access: admin access expected; moderator access may be required; logged-in session required or used
  • Side effects: Usually read-only.
  • Limits/notes: Generated from static route source analysis; confirm exact behavior in the handler before changing integrations.

GET /plugins/moderation/tos-bans

  • Purpose: Renders or serves the moderation plugin page for tos bans.
  • Inputs: No request parameters detected by static analysis.
  • Response format: HTML page rendered from an EJS view; HTTP redirect after handling the request
  • Access: admin access expected; moderator access may be required; logged-in session required or used
  • Side effects: Usually read-only.
  • Limits/notes: Generated from static route source analysis; confirm exact behavior in the handler before changing integrations.

GET /plugins/moderation/evidence/:id

  • Purpose: Renders or serves the moderation plugin page for evidence id.
  • Inputs: path params: id
  • Response format: HTTP redirect after handling the request; file download
  • Access: admin access expected; moderator access may be required; logged-in session required or used
  • Side effects: Usually read-only.
  • Limits/notes: Generated from static route source analysis; confirm exact behavior in the handler before changing integrations.

POST /plugins/moderation/actions

  • Purpose: Processes the moderation plugin action for actions.
  • Inputs: body: action_type, reason_detail, reason_short; file upload: multipart form file data
  • Response format: HTTP redirect after handling the request
  • Access: admin access expected; moderator access may be required; logged-in session required or used
  • Side effects: writes or mutates server-side state
  • Limits/notes: Generated from static route source analysis; confirm exact behavior in the handler before changing integrations. Most non-API POST routes are browser form submissions and usually redirect after completion.

POST /plugins/moderation/actions/:id/update-timeout

  • Purpose: Processes the moderation plugin action for actions id update timeout.
  • Inputs: path params: id; body: full submitted body is passed to a helper; exact fields are defined by the matching form/service
  • Response format: HTTP redirect after handling the request
  • Access: admin access expected; moderator access may be required; logged-in session required or used
  • Side effects: writes or mutates server-side state
  • Limits/notes: Generated from static route source analysis; confirm exact behavior in the handler before changing integrations. Most non-API POST routes are browser form submissions and usually redirect after completion.

POST /plugins/moderation/actions/:id/revoke

  • Purpose: Processes the moderation plugin action for actions id revoke.
  • Inputs: path params: id
  • Response format: HTTP redirect after handling the request
  • Access: admin access expected; moderator access may be required; logged-in session required or used
  • Side effects: writes or mutates server-side state
  • Limits/notes: Generated from static route source analysis; confirm exact behavior in the handler before changing integrations. Most non-API POST routes are browser form submissions and usually redirect after completion.

POST /plugins/moderation/notes

  • Purpose: Processes the moderation plugin action for notes.
  • Inputs: body: note
  • Response format: HTTP redirect after handling the request
  • Access: admin access expected; moderator access may be required; logged-in session required or used
  • Side effects: Consumes submitted data; state mutation happens in called helpers if present.
  • Limits/notes: Generated from static route source analysis; confirm exact behavior in the handler before changing integrations. Most non-API POST routes are browser form submissions and usually redirect after completion.

POST /plugins/moderation/notes/:id/delete

  • Purpose: Processes the moderation plugin action for notes id delete.
  • Inputs: path params: id
  • Response format: HTTP redirect after handling the request
  • Access: admin access expected; logged-in session required or used
  • Side effects: writes or mutates server-side state
  • Limits/notes: Generated from static route source analysis; confirm exact behavior in the handler before changing integrations. Most non-API POST routes are browser form submissions and usually redirect after completion.

Commands

  • No plugin command triggers detected.

Source

Plugin folder: plugins/moderation