Contact and updates
Use the published ModFlow contact for support, security, privacy, or accessibility concerns and verify current status before reporting drift.
- Audience
- moderator · senior reviewer · team lead · server admin · public appellant
- Availability
- free
- Maturity
- stable
Last reviewed
On this page
Use the published contact
Use the same published contact shown in the site footer for product support, security/privacy concerns, accessibility barriers, and documentation corrections. This guide intentionally does not invent a separate Contact page or unverified support channel.
Check current behavior before reporting drift
Read current status
Check audience, availability, maturity, limitations, and last-reviewed date on the live guide.
Check: The report starts from current documentation.
Verify in product
Use current Discord autocomplete or the selected-server dashboard and record the visible response.
Check: Stale memory or screenshots are ruled out.
Describe the mismatch
State the expected documented result and the actual safe observable result.
Check: The drift is reproducible without sensitive data.
Send one focused report
Use the published contact and include the exact guide URL.
Check: Maintainers can review the evidence and update code or documentation.
Choose the correct report type
| Type | Include | Urgency |
|---|---|---|
| Product support | Server, feature/page/command, state, time, safe steps. | Normal unless active moderation is blocked. |
| Documentation correction | Exact guide URL, quoted short claim, current in-product result. | Normal; higher when unsafe instructions are involved. |
| Security/privacy | Exposure type, server, affected surface, safe scope, containment. | Prompt; do not include the exposed content. |
| Accessibility | Barrier, task blocked, environment/assistive technology. | Based on severity and whether essential moderation is blocked. |
| Billing/access | Selected server, plan-page status, hosted-flow state/time. | Normal; never send card or payment details. |
| Excluded feature visible | Surface name, server, role, status, safe screenshot. | Prompt when it can create writes or leak data; do not experiment. |
Verify and report documentation drift
Check the date/status
Read last-reviewed, audience, availability, maturity, and limitations.
Check: The current documented contract is identified.
Use current autocomplete/UI
Verify the exact command/page once on the intended server.
Check: Cached memory and old screenshots are ruled out.
Compare the two states
Describe expected versus actual behavior without testing destructive writes.
Check: The comparison identifies exactly where the two states differ.
Attach evidence carefully
Use safe status text or a redacted screenshot; do not attach private content.
Check: Maintainers receive enough context.
Request correction, not a promise
Ask for the guide or product to be reconciled.
Check: Unverified behavior is not adopted as policy.
Keep staff training current
| Step | Action |
|---|---|
| Review scope | Identify affected roles, servers, commands, pages, permissions, and recovery. |
| Update local policy | Reconcile server-specific escalation rules and role mappings. |
| Rehearse with test data | Use test accounts/fixtures for changed actions, setup, or visibility. |
| Retire stale material | Remove old screenshots, pinned command lists, and compatibility aliases. |
| Brief staff | Share the record/page link, what changed, and what remains excluded. |
| Monitor drift | Collect focused reports from the first controlled uses. |