Server administration: questions for Charles (non-blocking; the recommended answers are being built) #704

Open
opened 2026-11-15 19:02:06 +00:00 by charles · 0 comments
Owner

From the spec, §17. Answer here to overrule any of them; until then the recommended choice is what gets built.

  • Q1 — Split and numbers. The inventory is 76 items. Recommended: two sub-projects, 9
    "Server administration"
    (this spec, 41 items: channels, permissions, roles, members,
    community settings, delete and transfer) and 10 "content and records" (§16). Alternative:
    one sub-project of about 80 tasks.
  • Q2 — Which checkout is the original. Recommended: ~/src/fluxer-soundboard (main,
    ba98441b4), as every earlier spec and the vendored OpenAPI document. Alternative:
    ~/src/fluxer as the brief said — it is on old-main-wip, three weeks and 2 838 commits
    behind, and would describe a client the instance no longer serves.
  • Q3 — Identity check methods. Recommended: password and authenticator code now, the rest
    in 10. Alternative: add email code now (one more request and screen).
  • Q4 — Settings as a full screen. Recommended: clone the original's full-screen entity
    settings, reusing the user-settings layout. Alternative: a large modal (less code, not what
    the original looks like).
  • Q5 — Saving overrides. Recommended: one channel PATCH with the whole array, as the web
    client. Alternative: the per-override PUT/DELETE endpoints (smaller requests, different
    audit-log entries from the original's).
  • Q6 — Reordering. Recommended: real drag and drop in the sidebar and the roles list,
    through one shared widget. Fallback if the widget task fails its spike: "Move up", "Move
    down" and "Move to category ▸" menu rows over the same core move operation, drag and drop
    following in 10.
  • Q7 — Members. Recommended: the members page in the main area, as the original.
    Alternative: a tab inside community settings.
  • Q8 — Reasons. Recommended: reasons where the original has a field (ban, timeout), none
    for kick. The server reads an X-Audit-Log-Reason header on every route and
    the web client does not send it. Alternative: add an optional reason to kick and role
    changes through that header (useful, not parity).
  • Q9 — Forum channels before sub-project 10. Recommended: Permissions tab only, Overview
    omitted. Alternative: a minimal Overview (name, guidelines) now.
  • Q10 — 2FA requirement switch. Recommended: build it (owner only, identity check), since
    it changes what moderators can do; enrolling 2FA itself stays with account settings (7).
    Alternative: leave the switch to 10.
  • Q11 — Topic field. Recommended: plain multi-line field. Alternative: embed the chat
    composer's editor for autocomplete (a large dependency inside a settings page).
  • Q12 — Live testing. Recommended: Charles runs §2 on a throwaway community created for the
    purpose; nothing in the build contacts the live server. Alternative: none.
From the spec, §17. Answer here to overrule any of them; until then the recommended choice is what gets built. ## 17. Questions for Charles (non-blocking; the recommended choice is what gets built) - **Q1 — Split and numbers.** The inventory is 76 items. Recommended: two sub-projects, **9 "Server administration"** (this spec, 41 items: channels, permissions, roles, members, community settings, delete and transfer) and **10 "content and records"** (§16). Alternative: one sub-project of about 80 tasks. - **Q2 — Which checkout is the original.** Recommended: `~/src/fluxer-soundboard` (`main`, ba98441b4), as every earlier spec and the vendored OpenAPI document. Alternative: `~/src/fluxer` as the brief said — it is on `old-main-wip`, three weeks and 2 838 commits behind, and would describe a client the instance no longer serves. - **Q3 — Identity check methods.** Recommended: password and authenticator code now, the rest in 10. Alternative: add email code now (one more request and screen). - **Q4 — Settings as a full screen.** Recommended: clone the original's full-screen entity settings, reusing the user-settings layout. Alternative: a large modal (less code, not what the original looks like). - **Q5 — Saving overrides.** Recommended: one channel PATCH with the whole array, as the web client. Alternative: the per-override PUT/DELETE endpoints (smaller requests, different audit-log entries from the original's). - **Q6 — Reordering.** Recommended: real drag and drop in the sidebar and the roles list, through one shared widget. Fallback if the widget task fails its spike: "Move up", "Move down" and "Move to category ▸" menu rows over the same core move operation, drag and drop following in 10. - **Q7 — Members.** Recommended: the members page in the main area, as the original. Alternative: a tab inside community settings. - **Q8 — Reasons.** Recommended: reasons where the original has a field (ban, timeout), none for kick. The server reads an `X-Audit-Log-Reason` header on every route and the web client does not send it. Alternative: add an optional reason to kick and role changes through that header (useful, not parity). - **Q9 — Forum channels before sub-project 10.** Recommended: Permissions tab only, Overview omitted. Alternative: a minimal Overview (name, guidelines) now. - **Q10 — 2FA requirement switch.** Recommended: build it (owner only, identity check), since it changes what moderators can do; enrolling 2FA itself stays with account settings (7). Alternative: leave the switch to 10. - **Q11 — Topic field.** Recommended: plain multi-line field. Alternative: embed the chat composer's editor for autocomplete (a large dependency inside a settings page). - **Q12 — Live testing.** Recommended: Charles runs §2 on a throwaway community created for the purpose; nothing in the build contacts the live server. Alternative: none.
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
charles/fluxer-native#704
No description provided.