Files

T

Jannis Braun 5ad8aefaff feat(federation): reset-cleanup panel — informational detach copy, real server-side Dismiss, Keep removed (detach spec §4.6)

2026-07-02 19:06:21 +02:00

38 KiB

Raw Blame History

Admin & Instance Configuration System

Source files:

packages/server/src/routes/admin.ts -- User management, storage management endpoints
packages/server/src/routes/instance.ts -- Public instance info endpoint
packages/server/src/routes/settings.ts -- Instance settings and streaming limits endpoints
packages/server/src/utils/auth.ts -- requireAdmin middleware
packages/server/src/utils/userDeletion.ts -- tombstoneUser() deletion logic
packages/server/src/utils/storageJanitor.ts -- Storage stats, orphan detection, cleanup
packages/web/src/stores/settingsStore.ts -- Zustand store for instance/streaming settings
packages/web/src/components/modals/instanceSettingsPanels/GeneralPanel.tsx -- General settings UI
packages/web/src/components/modals/instanceSettingsPanels/RegistrationPanel.tsx -- Registration toggles + invite-link CRUD UI
packages/web/src/components/modals/instanceSettingsPanels/FederationPanel.tsx -- Federation peers panel (peering, approval queue, peer status, rotation, reset)
packages/web/src/components/modals/instanceSettingsPanels/StoragePanel.tsx -- Storage management UI
packages/web/src/components/modals/instanceSettingsPanels/StreamingPanel.tsx -- Streaming config UI
packages/web/src/components/modals/instanceSettingsPanels/UsersPanel.tsx -- User management UI
packages/server/src/routes/invites.ts -- Admin invite-link CRUD endpoints
packages/server/src/utils/inviteService.ts -- Token generation, derived status, atomic redemption transaction
packages/shared/src/types.ts -- Shared type interfaces
packages/shared/src/constants.ts -- Streaming constants (resolutions, framerates, bitrate matrix)

Authentication & Authorization

All admin endpoints use two Fastify preHandlers chained in order:

authenticate -- Verifies JWT from Authorization: Bearer <token> header, sets request.userId
requireAdmin -- Queries users table, verifies isAdmin === 1. Returns 403 if not admin.

auth.ts:requireAdmin()
  → db.select().from(users).where(id = request.userId)
  → if !caller || caller.isAdmin !== 1 → 403 "Only instance admins can perform this action"

The instance info endpoint (GET /api/instance/info) is fully public with no auth. The streaming limits read endpoint (GET /api/settings/streaming) requires only authenticate (any logged-in user).

Instance Settings Table

Singleton row in instance_settings (id=1). See database.md for full schema.

Settings are split into two API surfaces:

Setting Group	Read Endpoint	Write Endpoint
General/Admin	`GET /api/settings/instance` (admin)	`PATCH /api/settings/instance` (admin)
Streaming	`GET /api/settings/streaming` (auth)	`PATCH /api/settings/streaming` (admin)
Public info	`GET /api/instance/info` (public)	N/A (derived from settings)

General Settings Schema (InstanceAdminSettings)

Field	Type	DB Column	Validation	Notes
instanceName	string	instanceName	1-32 chars, trimmed	Default: `'Backspace'`
registrationOpen	boolean	registrationOpen	boolean	Local-account registration. DB null = use env `REGISTRATION_OPEN` (default true)
federatedRegistrationOpen	boolean	federatedRegistrationOpen	boolean	Federated-account creation against this instance. NOT NULL DEFAULT 1. Controls whether remote users can create `username@thisInstance` accounts via Connections (see auth.md + client-federation.md)
discoveryEnabled	boolean	discoveryEnabled	boolean	Controls space Explore page
gifApiKey	string?	gifApiKey	string or empty to clear	Returned masked as `****{last4}` for security
gifEnabled	boolean?	(derived)	--	Read-only; true when gifApiKey is non-null
maxUploadSizeMb	number	maxUploadSizeBytes	positive integer (>=1 MB), upper bound is JS safe-integer ceiling (~8 EB) — effectively unlimited	Operator-set; no application cap. Stored as bytes; converted on read/write. DB null = use env `MAX_UPLOAD_SIZE` (default 100MB)
federationRelayEnabled	boolean	federationRelayEnabled	boolean	Default: 1 (enabled)
federationRelayTtlDays	number	federationRelayTtlDays	integer 1-365	Default: 30 days
autoAcceptPeering	boolean	autoAcceptPeering	boolean	Default: true. When false, `peer/accept` rejects unsolicited requests (403 PEERING_REQUIRES_APPROVAL); only requests where a local `pending` record already exists are accepted

Streaming Settings Schema (InstanceStreamingLimits)

Field	Type	DB Column	Validation	Default
maxBitrateKbps	number	maxBitrateKbps	500-1000000	20000
minBitrateKbps	number	minBitrateKbps	100-1000000, must be < max	500
bitrateStepKbps	number	bitrateStepKbps	50-5000	500
allowedResolutions	(number\|'native')[]	allowedResolutions	Non-empty, values from STANDARD_RESOLUTIONS or 'native'	[540,720,1080]
allowedFramerates	number[]	allowedFramerates	Non-empty, values from STANDARD_FRAMERATES	[30,45,60]
maxResolution	number	maxResolution	Must be in STANDARD_RESOLUTIONS	1080
maxFramerate	number	maxFramerate	Must be in STANDARD_FRAMERATES	60
discoveryEnabled	boolean	discoveryEnabled	boolean	true
bitrateMatrixOverrides	Record<string,number>\|null	bitrateMatrixOverrides	Keys: `{res}_{fps}`, values: 1-1000000	null
allowCustomBitrate	boolean	allowCustomBitrate	boolean	true

Streaming constants (packages/shared/src/constants.ts):

STANDARD_RESOLUTIONS = [540, 720, 1080, 1440, 2160]
STANDARD_FRAMERATES  = [30, 45, 60, 75, 90, 120]
HIGH_END_RESOLUTION_THRESHOLD = 1440
HIGH_END_FRAMERATE_THRESHOLD  = 75

Default bitrate matrix (kbps, VP9 screen share):

      30    45    60    75    90    120
540   1500  2000  2500  2800  3200  4000
720   3000  3500  4000  4500  5000  6000
1080  6000  7000  8000  9000  10000 12000
1440  10000 12000 14000 16000 18000 22000
2160  20000 24000 28000 32000 38000 45000

See voice.md for how clients enforce these limits at the WebRTC encoding boundary.

Serialization Details

Resolution/Framerate Storage

Stored as CSV strings in DB, parsed on read:

settings.ts:rowToLimits()
  allowedResolutions: row.allowedResolutions.split(',')
    → .map(s => s === 'native' ? 'native' : Number(s))
    → .filter(v => v === 'native' || STANDARD_RESOLUTIONS.includes(v))

  allowedFramerates: row.allowedFramerates.split(',')
    → .map(Number)
    → .filter(n => STANDARD_FRAMERATES.includes(n))

On write, numbers sorted ascending with 'native' always last:

settings.ts:PATCH /api/settings/streaming
  nums = allowedResolutions.filter(r => r !== 'native').sort(asc)
  updateData.allowedResolutions = [...nums, ...(hasNative ? ['native'] : [])].join(',')

Bitrate Matrix Overrides

Stored as JSON string in DB. Sparse representation: only cells differing from defaults.

settings.ts:rowToLimits()
  raw = row.bitrateMatrixOverrides (string|null)
  → JSON.parse → validate is non-null non-array object → return if non-empty, else null

Valid keys: {resolution}_{framerate} (e.g., "1080_60"). Validated against all combinations of STANDARD_RESOLUTIONS x STANDARD_FRAMERATES.

GIF API Key Masking

The gifApiKey is never returned in full. The GET response masks it:

settings.ts:GET /api/settings/instance
  gifApiKey: gifKey ? `****${gifKey.slice(-4)}` : undefined

On PATCH, if the client sends back a value starting with ****, it is ignored (prevents overwriting the real key with the mask). Empty string clears the key.

API Endpoints

Public Instance Info

GET /api/instance/info

No authentication. Returns:

{
  name: string;        // instanceSettings.instanceName ?? 'Backspace'
  version: string;     // Hardcoded '1.0.0' in instance.ts
  registrationOpen: boolean;  // DB setting overrides env if non-null
  federatedRegistrationOpen: boolean;  // NOT NULL DEFAULT 1; gates federated-account creation
  sourceCodeUrl: string;      // AGPL § 13; config.sourceCodeUrl (env BACKSPACE_SOURCE_URL)
  commit: string | null;      // AGPL § 13; config.commit (env BACKSPACE_COMMIT, build-injected)
  instanceId: string;         // Persistent per-instance epoch (incarnation UUID); getInstanceId()
}

instanceId is the persistent per-instance epoch — a UUID minted once by ensureDefaults on first boot and stable across restarts (stored in instance_settings.instance_id, guaranteed non-null after boot). It changes only when the instance is wiped/re-provisioned. Peers read it to detect that a remote has been re-provisioned (federation epoch self-healing). The server reads it via the cached getInstanceId() in utils/federationEpoch.ts, which throws if the epoch is unset (invariant: ensureDefaults runs before any read).

Registration resolution order: instance_settings.registrationOpen (if not null) > config.registrationOpen (from REGISTRATION_OPEN env, default true).

federatedRegistrationOpen is consumed by the Connections UI (client-federation.md) to decide whether to surface the "create federated account on this instance" affordance.

sourceCodeUrl / commit implement the AGPL-3.0 § 13 network-use source offer. sourceCodeUrl defaults to the upstream repo and is overridable via BACKSPACE_SOURCE_URL — operators running a modified build MUST point it at their fork so network users get the source of the version actually running. commit is injected at Docker build time (deploy.sh passes --build-arg BACKSPACE_COMMIT=$(git rev-parse --short HEAD) → Dockerfile ARG/ENV → config.commit); it is null in local dev. These are not admin-editable settings — they are deployment/config values, deliberately exposed on this unauthenticated endpoint for transparency to anonymous users and federated peers.

General Instance Settings

GET  /api/settings/instance    — admin only → InstanceAdminSettings
PATCH /api/settings/instance   — admin only → InstanceAdminSettings

See field table above for validation rules. Cross-field: discoveryEnabled changes here are also synced to streamingLimits in the frontend store (settingsStore.ts:updateInstanceSettings).

Streaming Settings

GET   /api/settings/streaming   — any authenticated user → InstanceStreamingLimits
PATCH /api/settings/streaming   — admin only → InstanceStreamingLimits

Cross-field validation on PATCH:

minBitrateKbps must be strictly less than maxBitrateKbps (checked against effective values after merge with current DB row).

Storage Management

All admin-only.

GET  /api/admin/storage/stats         → StorageStats
GET  /api/admin/storage/orphans       → { orphans: OrphanedFile[] }
POST /api/admin/storage/cleanup       { dryRun?: boolean } → CleanupResult
POST /api/admin/storage/cleanup-media { maxAgeDays: number, dryRun?: boolean } → CleanupResult
POST /api/admin/storage/cleanup-tus   { maxAgeHours?: number = 1, dryRun?: boolean = false } → CleanupResult

The cleanup-tus route walks .tus/, deleting (or counting, if dryRun) any entry whose mtime is older than maxAgeHours. No DB rows are touched — .tus/ is filesystem-only — so deletedAttachmentRecords in the response is always 0. See docs/systems/uploads.md §Janitor for the full lifecycle (immediate-DELETE on cancel/discard, automatic 24 h cleanupTusUploads, 48 h defensive cleanupTusStragglers, and this admin-driven sweep).

StorageStats shape:

{
  totalFiles: number;
  totalSize: number;           // bytes
  referencedFiles: number;
  referencedSize: number;      // bytes
  orphanedFiles: number;       // Files on disk not referenced by DB
  orphanedSize: number;
  unlinkedAttachments: number; // Attachment records with no message
  unlinkedSize: number;
  danglingAttachments: number; // Attachment records pointing to missing files
  danglingSize: number;
  staleTusSessions: number;    // .tus/ payload + sidecar files with mtime > 1 h old
  staleTusSize: number;        // Total bytes of those stale tus entries
  breakdown: { type: string; count: number; size: number }[];
}

staleTusSessions / staleTusSize use a fixed 1 h display threshold (active uploads write chunks frequently; a 1 h+ gap means the user walked away). This is distinct from the maxAgeHours body parameter on cleanup-tus, which is configurable per request.

CleanupResult shape:

{
  dryRun: boolean;
  deletedFiles: number;
  freedBytes: number;
  deletedAttachmentRecords: number;
  errors: string[];
}

Storage functions (getStorageStats, getOrphanedFiles, cleanupStorage, cleanupOldMedia, cleanupStaleTusSessions, getStaleTusInfo) are implemented in utils/storageJanitor.ts. Tus-specific lifecycle details live in docs/systems/uploads.md §Janitor.

Cleanup flow (UI):

Admin clicks "Preview Cleanup" -- calls cleanupStorage(dryRun=true) or cleanupOldMedia(days, dryRun=true)
Preview result shown with count/size
"Clean Up Now" / "Delete Now" button enabled only after preview completes
Live cleanup calls same endpoint with dryRun=false
Stats refreshed after live cleanup

Media cleanup validation: maxAgeDays must be a positive integer >= 1. Returns 400 otherwise.

User Management

All admin-only.

GET    /api/admin/users              → AdminUserListResponse
GET    /api/admin/users/instances    → { instances: string[] }
PATCH  /api/admin/users/:id/role     { isAdmin: boolean } → AdminUser
POST   /api/admin/users/:id/reset-password → AdminResetPasswordResponse
DELETE /api/admin/users/:id          → { success: boolean }

User List: Filters, Search, Sort, Pagination

Query Parameters

Param	Type	Default	Description
q	string	''	Fuzzy search on username and displayName (SQL LIKE `%q%`)
page	number	1	Page number, min 1
pageSize	number	50	Results per page, clamped to 1-100
showDeleted	'true'	false	Include tombstoned users
homeInstance	string	--	`'local'` for null homeInstance; otherwise exact domain match
role	string	--	`'admin'` or `'non-admin'`
joinedAfter	date string	--	Parsed as `new Date(value).getTime()`
joinedBefore	date string	--	Parsed as `new Date(value + 'T23:59:59.999Z').getTime()` (inclusive end-of-day)
sort	string	'newest'	One of: `newest`, `oldest`, `az`, `za`

Sort Options

Value	SQL	Description
newest	`desc(users.createdAt)`	Most recently created first
oldest	`asc(users.createdAt)`	Oldest first
az	`asc(users.username)`	Alphabetical A-Z
za	`desc(users.username)`	Reverse alphabetical

Filter Composition

Filters are combined with AND. When showDeleted is false (default), isDeleted = 0 is always added. Search q creates an OR condition across username LIKE and displayName LIKE.

Instances Endpoint

GET /api/admin/users/instances returns all distinct non-null homeInstance values from the users table. Used by the frontend to populate the instance filter dropdown.

AdminUser Shape

{
  id: string;
  username: string;
  displayName: string | null;
  avatar: string | null;
  avatarColor: string | null;
  status: string;         // 'online'|'idle'|'dnd'|'offline', defaults to 'offline' if null
  isAdmin: boolean;
  isDeleted: boolean;
  homeInstance: string | null;
  createdAt: number;      // epoch ms
}

Produced by admin.ts:toAdminUser() -- maps integer DB columns to booleans, coalesces null status.

Admin Actions: Safety Rules

Promote/Demote Admin (PATCH /api/admin/users/:id/role)

Request: { isAdmin: boolean }

Safety checks:

isAdmin must be a boolean (400)
Target user must exist (404)
Target must not be deleted (400)
Promote: target must NOT have a homeInstance (403 "Federated users cannot be promoted to admin")
Demote: if target is currently admin, count all non-deleted admins. If count <= 1, reject (400 "Cannot demote the last admin")

Side effects on success:

Updates users.isAdmin to 1 or 0
Sends user_updated WebSocket event to target user via connectionManager.sendToUser() so their UI reflects the change immediately

Reset Password (POST /api/admin/users/:id/reset-password)

Safety checks:

Target must exist (404)
Target must not be deleted (400)
Target must NOT have a homeInstance (400 "Federated users authenticate via their home instance")

Process:

Generate 12 random bytes, encode as base64url -- this is the temporary password
Hash with bcrypt via hashPassword()
Update users.passwordHash and users.passwordChangedAt = Date.now()
Force-disconnect all of target's WebSocket sessions via connectionManager.forceDisconnectUser()
Return { temporaryPassword } in response

The passwordChangedAt update ensures all existing JWTs for the user are invalidated (tokens issued before this timestamp are rejected by the auth middleware).

The temporary password is shown exactly once in the admin UI -- the UsersPanel displays it inline below the user row with a copy button and a "Shown once" warning.

Delete User (DELETE /api/admin/users/:id)

Safety checks:

Cannot delete yourself (400 "Use account settings to delete your own account")
Target must exist (404)
Target must not be already deleted (400)
Target must not own any spaces (400 "User owns spaces -- transfer ownership first", response includes ownedSpaces array with id/name)

Process:

Call tombstoneUser(targetId) -- returns list of files to delete (avatar, banner)
- Tombstone sets isDeleted=1, clears personal data, removes from spaces/friends/DMs/reactions/read-states/folders in a transaction
- Transfers group DM ownership to next member
Delete returned files from disk via deleteUploadFile()
Force-disconnect all WebSocket sessions
Return { success: true }

Peering Approval Requests

All admin-only. Present when autoAcceptPeering is false. The queue holds both directions:

Inbound rows — remote instances asking to peer with us.
Outbound rows — local users who initiated peering (friend-add, etc.) that the local Outbound Peering Gate intercepted because no federation_peers row exists yet for the target.

GET  /api/federation/approval-requests              → { requests: ApprovalRequestSummary[] }
POST /api/federation/approval-requests/:id/approve  → { success, peerStatus?, peer? }
POST /api/federation/approval-requests/:id/deny     → { success }

ApprovalRequestSummary (see api.md → Federation Peering Approval Queue for the complete TypeScript shape):

{
  id: string;
  direction: 'inbound' | 'outbound';
  origin: string;
  instanceName: string | null;
  requestedAt: number;
  expiresAt: number;
  // Outbound rows ONLY — inbound rows omit this field entirely (absent, not null and not []).
  subscribers?: Array<{ id, userId, username, triggerReason, triggerTarget, createdAt }>;
}

See federation.md — Peer Approval Queue and Outbound Peering Gate sections for the full approval/denial/expiry flow (including the direction-branched approve/deny semantics, onPeerActivated cleanup invariant, and the inbound-expiry /peer/denied notification preserved unchanged).

Frontend Architecture

Settings Store (settingsStore.ts)

Zustand store managing two data objects:

State	Type	Fetched Via	Updated Via
streamingLimits	InstanceStreamingLimits \| null	`fetchStreamingLimits()`	`updateStreamingLimits()`
instanceSettings	InstanceAdminSettings \| null	`fetchInstanceSettings()`	`updateInstanceSettings()`
isAdmin	boolean	Set externally via `setIsAdmin()`	--
gifEnabled	boolean	`fetchGifEnabled()`	--

Default fallback: If streaming limits fail to fetch, the store falls back to DEFAULT_LIMITS:

{
  maxBitrateKbps: 20000,
  minBitrateKbps: 500,
  bitrateStepKbps: 500,
  allowedResolutions: [540, 720, 1080],
  allowedFramerates: [30, 45, 60],
  maxResolution: 1080,
  maxFramerate: 60,
  discoveryEnabled: true,
  bitrateMatrixOverrides: null,
  allowCustomBitrate: true,
}

Cross-field sync: When updateInstanceSettings() changes discoveryEnabled, it also patches streamingLimits.discoveryEnabled to keep the streaming panel's DiscoveryPanel warning banner in sync.

Exported helper: getStreamingLimits() returns current limits or defaults -- used by voice/streaming code outside React.

Admin UI Panels

All panels live under packages/web/src/components/modals/instanceSettingsPanels/. Each operates as a controlled form with a local draft state, detecting changes against the store's server-synced values. Unsaved changes show a sticky glass-bubble save/reset bar at the bottom.

GeneralPanel

Manages: instance name, discovery toggle, GIF API key, federation relay toggle/TTL.

Instance name input: max 32 chars, enforced client-side via slice(0, 32)
GIF key: password input, separate dirty tracking (gifKeyDirty). Only sent on save if modified. "Clear key" button sets empty string.
Federation relay toggle and TTL input: drive federationRelayEnabled and federationRelayTtlDays instance settings.

The registration toggles (registrationOpen / federatedRegistrationOpen) and the invite-link manager live in RegistrationPanel.

RegistrationPanel

Owns the two independent registration gates and the admin invite-link CRUD surface. Mounted in the instance settings sidebar between General and Users.

Toggles (top of panel) — bound to settingsStore.instanceSettings.registrationOpen and .federatedRegistrationOpen. Save bar appears at the bottom of the panel when either toggle differs from the synced value (existing pattern from GeneralPanel):

Public registration (registrationOpen) — "Allow anyone to create a local account from /register. When off, only invite links work for new local accounts."
Federated registration (federatedRegistrationOpen) — "Allow users from other instances to create a federated account here via their Connections settings. Existing federated accounts log in normally."

Invite Links (below the toggles) — segmented [Active] [Archived] tabs (local component state, default active). Tab switch refetches via GET /api/admin/invites?status=.... A tabRef discards stale in-flight fetches when the admin switches tabs mid-load. [+ Create link] button opens the Create modal.

Invite row — name (left, primary text), usage indicator (usedCount / maxUses or usedCount uses · unlimited, color-coded amber at >=80%), status pill on archived tab (Expired rose / Exhausted amber / Revoked txt-tertiary), expiry summary subline (active: Expires in 4 days / No expiration; archived: Expired Apr 25 / Exhausted Apr 27 / Revoked Apr 28), creator + relative-time created.

Row actions branch on derived status:

Active rows: Copy link, Edit, Revoke, kebab → Delete permanently, View redemptions.
Archived rows: Reinstate, kebab → Delete permanently, View redemptions.

Modals: Create / Edit / Reinstate / Redemptions all use the shared Modal component with mobileStyle="fullscreen", portaled to document.body (the parent settings dialog uses glass-modal's backdrop-filter, which establishes a containing block — portaling escapes it so the child modal renders viewport-relative). On desktop they appear as the standard centered dialog with max-w-md (Redemptions: max-w-lg); on mobile they slide in fullscreen with the Modal's standard close button + safe-area padding. The decorative lavender/sky icon chip and helper paragraph live inside children (Modal's title prop renders the heading + close X).

Create Invite — Name (1-64 chars), Max uses (radio: Unlimited / [N >= 1]), Expires (preset: 1 hour / 24 hours / 7 days / 30 days / Never / Custom…). Defaults: maxUses: null, expiresAt: now + 7 days. On success the URL is auto-copied to clipboard and the new row animates in at the top of the active list.
Edit Invite — same shape as Create, pre-filled. Hidden for revoked rows (Reinstate is the only path back).
Reinstate — Variant A (was revoked): rotates the token (tokenRotated: true). Modal copy: "This will generate a new link. The previously revoked URL stays inactive." Required to bump maxUses and/or expiresAt so the resulting row derives status active (server returns 400 otherwise).
Reinstate — Variant B (was expired or exhausted): preserves the same token (tokenRotated: false). Modal copy: "The same link will start working again. Anyone who saved the URL will be able to use it." Same bump-to-active validation.
Delete confirmation — uses the existing ConfirmDialog with variant="danger", copy: "Delete <name> permanently? This cannot be undone. Redemption history for this link will also be removed. If you only want to stop the link from working, use Revoke instead — that preserves the redemption record." (Spec §4.2 originally proposed type-to-confirm, but the codebase uses the existing ConfirmDialog precedent for high-blast-radius admin actions; type-to-confirm was not introduced as a one-off pattern.)

Redemption viewer — opens via View redemptions action. Shows usedCount of maxUses header (or usedCount uses · unlimited), then one row per redemption: registrantUsername (left) + redeemedAt formatted (right). When currentUsername !== registrantUsername (post-rename) or isDeleted === true, the registrant name is annotated alice (now Anastasia) / alice (now Deleted User) — snapshot stable, live state visible. Clicking a non-deleted row opens the user's profile (UserPopover). If the invite is revoked, a banner at the top notes "The redemptions above represent users who registered before revocation."

Invites outlive their creator's account. invite_links.createdBy has no CASCADE — when an admin is tombstoned, their invites stay live and any current admin can manage them. The list joins users to surface createdByUsername, which resolves to 'Deleted User' when the creator has isDeleted = 1 (matching the sanitizeUser convention).

State ownership. Invite CRUD is not in settingsStore — it's transient panel state owned by RegistrationPanel (useState for tab, invites, invitesLoading, modal flags). Pattern matches UsersPanel. Reasoning: invites are page-scoped, not session-scoped — caching them globally would just create staleness bugs when the panel reopens.

Type shapes (from packages/shared/src/types.ts):

type InviteLinkSummary = {
  id: string;
  token: string;
  name: string;
  status: 'active' | 'expired' | 'exhausted' | 'revoked';  // derived; never stored
  maxUses: number | null;
  usedCount: number;
  expiresAt: number | null;
  revokedAt: number | null;
  createdBy: string;
  createdByUsername: string | null;  // 'Deleted User' when creator's isDeleted = 1
  createdAt: number;
  lastRedeemedAt: number | null;  // epoch ms of most recent redemption; null when usedCount = 0
  url: string;  // server-built `https://<host>/register?invite=<token>` — clients MUST NOT assemble
};

type InviteRedemption = {
  id: string;
  userId: string | null;       // null only on hard-delete (defensive — tombstone keeps row populated)
  registrantUsername: string;  // snapshot at registration moment
  currentUsername: string | null;
  isDeleted: boolean;
  redeemedAt: number;
};

See api.md → Admin: Invite Management for full endpoint signatures and the auth.md → Invite Tokens section for the redemption transaction + audit trail.

FederationPanel

Manages: federation peers list, pending approval requests (inbound + outbound), manual peering initiation, secret rotation, peer reset.

Pending Approvals section: Visible only when pendingApprovalCount > 0 (from ready payload — the count sums inbound + outbound rows). Positioned above the peer list. Both directions render as rows in the same unified queue, branched on direction:
- Inbound rows — "{instanceName} ({origin}) — wants to peer with us." Approve / Deny buttons.
- Outbound rows — "{instanceName} ({origin}) — N user(s) want us to peer with them. Triggered by: friend-add (etc.)." Inline expansion reveals the subscriber list (username — friend_add → alice@orbit, ...). Approve / Deny buttons same as inbound; backend branches on direction.
- Approve calls api.federation.approveApprovalRequest(id) and Deny calls api.federation.denyApprovalRequest(id). Both remove the row from the local list on success and refresh on federation_approval_request_received (which now also fires for outbound queue creation) and federation_peers_changed.
- ConfirmDialog copy variants: the dialog branches on direction. Outbound approve confirms "send /peer/accept to {origin} on behalf of N user(s)"; outbound deny confirms "fan out denied notifications to N user(s) and discard the queued request" (no remote network call).
Federation peers: fetched via api.federation.peers(), displayed as a list with status badges (active/pending/unreachable/awaiting_approval/rejected/needs_attention), last-seen/synced times, and per-peer actions.
Peers with status 'revoked' are filtered out of the visible list.
Peers in unreachable status render a "Check now" button that calls api.federation.recheckPeer(peerId) (POST /api/federation/peers/:id/recheck) to run an immediate reachability probe. On recovered: true the row flips to active locally and a success toast fires; otherwise a "still unreachable" toast shows. This is the manual counterpart to the demand-driven processRecoveryTick worker (see federation.md → PEER_UNREACHABLE_THRESHOLD).
Revoke calls api.federation.revokePeer(peerId) and removes from local list.
Peers in needs_attention status render with a rose "Needs Attention" pill and a single "Reset Peering" action. The action opens a danger-variant ConfirmDialog explaining that reset deletes the local peer record (cascade-removes outbox entries) and requires out-of-band re-peering with the remote admin.
Reset cleanup section (ResetCleanup, instance-epoch self-healing §6.4) — the highest-priority attention surface, rendered above the peer list; returns null when there is nothing to clean up. Fetches api.federation.peers() + api.federation.resetEvents() and subscribes to onFederationPeerResetDetected (the federation_peer_reset_detected WS event) to refetch live. Two stacked surfaces:
- Reset-detected banner — one persistent accent-rose banner per peer with status === 'needs_attention' && needsAttentionReason === 'peer_reset_detected', distinguishing a wiped-and-reinstalled peer from a generic auth-failure peer. Its Re-peer button runs the existing one-click flow in order: api.federation.resetPeer(id) then api.federation.initiatePeering({ remoteOrigin }) — resetting the stale local record before the fresh handshake so activation heals stale friendships/DMs against the new incarnation (warning-variant ConfirmDialog). The outcome is now surfaced honestly, not always as success: if initiatePeering resolves with verified === false (or the returned peer is needs_attention), the toast is a warning — "Re-peer incomplete — {peer} still holds stale peering for you. Its admin must reset their side, then Re-peer again." — because the handshake could not be cryptographically verified (the remote still holds a conflicting row; see federation.md "Trust re-establishment contract"). If it rejects with 409 PEER_EXISTS_RESET_REQUIRED, the same "ask the remote admin to reset their side" warning is shown. Only a verified activation shows the green "Re-peering initiated" success toast. This means the common one-side reset recovers in one click, while a bidirectional-stale peering tells the admin exactly that the other side must reset once.
- Detached-accounts card (from GET /reset-events, per origin with orphanedAccounts.length > 0 && acknowledgedAt === null — acknowledged events are filtered client-side, the endpoint keeps returning them for audit) — neutral-tier (bg-white/[0.02], no rose/urgency styling; the rose banner is reserved for the actionable reset-detected surface). Copy is informational, not urgent-cleanup: "{origin} was reset — N replicated identities auto-cleaned, N accounts with local content detached. Detached accounts keep working locally — owners keep access with their existing password." Each detached real account is shown with its owned-spaces / membership / message counts. Actions: a per-account Remove (danger ConfirmDialog → api.admin.deleteUser(id), i.e. the existing DELETE /api/admin/users/:id full purge, for accounts that truly are abandoned; a Remove on a space-owning account returns the existing 409 { ownedSpaces } → "transfer ownership first" toast rather than deleting) and a per-event Dismiss — keep all detached accounts footer button that calls api.federation.acknowledgeResetEvent(origin) (POST /api/federation/reset-events/acknowledge) then re-fetches — a real, server-side acknowledgement (not the old client-only "Keep") that hides the card and drops the event from the badge count without touching any account. The badge counts unacknowledged events-with-orphans plus reset-detected peers.

StoragePanel

Manages: storage overview, file type breakdown, upload limit, orphan cleanup, media retention cleanup.

Stats grid: 5 cards (total files, referenced, orphaned, unlinked uploads, dangling records) with byte formatting
File type breakdown: List of categories (image/video/audio/document/other) with file counts and sizes
Upload limit: Number input (1-5120 MB) with save button, persisted via updateInstanceSettings({ maxUploadSizeMb })
Orphan cleanup: Two-step (preview dry-run, then live). "Clean Up Now" disabled until preview completes
Media retention: Age-based cleanup with configurable days input. Same two-step preview/execute pattern.
"Refresh Stats" link at bottom re-fetches all stats

StreamingPanel

Manages: bitrate range (min/max/step), custom bitrate toggle, resolution/framerate allowlists, bitrate matrix.

Bandwidth section: Range sliders + number inputs for min/max bitrate. Step size via preset pills (100, 250, 500, 1000, 2500, 5000 kbps) + custom number input.
Custom Bitrate toggle: Controls whether users can set their own bitrate vs using matrix defaults
Quality section: Toggle pills for each resolution (540p, 720p, 1080p, 1440p, 4K, Native) and framerate (30, 45, 60, 75, 90, 120 fps). At least one of each must remain enabled.
High-end warning: Shown when resolutions >= 1440 or framerates >= 75 are enabled. Warns about CPU/GPU/bandwidth requirements.
Bitrate matrix: Interactive grid of resolution x framerate cells. Displays in Mbps (stored as kbps). Click to edit. Overridden cells highlighted in accent-primary. Cells exceeding maxBitrateKbps highlighted in amber.
Scale slider: Multiplies all matrix values by 0.5x-2.0x. Captures snapshot on drag start, applies factor during drag, releases on pointer up.
Save payload: Only cells differing from defaults are sent as bitrateMatrixOverrides; identical-to-default cells are omitted (sparse representation). If no overrides, null is sent.

UsersPanel

Manages: user list with search/filter/sort/pagination, admin promotion/demotion, password reset, account deletion.

Search: Debounced (300ms) text input, resets to page 1 on change
Filters: Instance dropdown (local/specific domain), role (admin/non-admin), joined-after/joined-before date pickers, sort dropdown
"Clear filters" link: Visible when any filter/sort/search is active. Resets all to defaults.
Page size: Fixed at 50 (not user-configurable)
Pagination: Previous/Next buttons, "Page X of Y (N users)" label
User rows: Avatar, username, display name, badges (Admin amber, federated instance sky, Deleted rose), join date
Action buttons (per user, hidden if deleted):
- Shield icon: promote/demote admin. Disabled for federated users. Demotion requires ConfirmDialog.
- Key icon: reset password. Disabled for federated users. Requires ConfirmDialog. Shows temporary password inline.
- Trash icon: delete user. Disabled for self. Requires ConfirmDialog (danger variant).
Temp password display: Appears inline below the user row after successful reset. Includes copy-to-clipboard button and "Shown once" notice.

Data Flow: Settings Update Lifecycle

[Admin UI Panel]
  → local draft state (useState)
  → user clicks Save
  → settingsStore.updateStreamingLimits() / updateInstanceSettings()
    → api.settings.updateStreaming() / updateInstance()
      → PATCH /api/settings/streaming or /api/settings/instance
        → Server validates each field
        → Cross-field validation (min < max for bitrates)
        → db.update(instanceSettings).set(updateData).where(id=1)
        → db.select fresh row → serialize → return
    → store.set({ streamingLimits: updated }) / set({ instanceSettings: updated })
  → UI re-renders from store, draft resets to match

Cross-References

Database schema: database.md -- instance_settings, users, spaces tables
API endpoints: api.md -- Full endpoint listing for admin, settings, instance routes
Federation relay: federation.md -- Relay toggle/TTL mechanics, peer management, outbox delivery
Voice/streaming: voice.md -- Client-side enforcement of streaming limits
Permissions: permissions.md -- Admin flag is separate from RBAC; isAdmin is a user-level column, not a permission bit

38 KiB Raw Blame History

Admin & Instance Configuration System

Authentication & Authorization

Instance Settings Table

General Settings Schema (InstanceAdminSettings)

Streaming Settings Schema (InstanceStreamingLimits)

Serialization Details

Resolution/Framerate Storage

Bitrate Matrix Overrides

GIF API Key Masking

API Endpoints

Public Instance Info

General Instance Settings

Streaming Settings

Storage Management

User Management

User List: Filters, Search, Sort, Pagination

Query Parameters

Sort Options

Filter Composition

Instances Endpoint

AdminUser Shape

Admin Actions: Safety Rules

Promote/Demote Admin (PATCH /api/admin/users/:id/role)

Reset Password (POST /api/admin/users/:id/reset-password)

Delete User (DELETE /api/admin/users/:id)

Peering Approval Requests

Frontend Architecture

Settings Store (settingsStore.ts)

Admin UI Panels

GeneralPanel

RegistrationPanel

FederationPanel

StoragePanel

StreamingPanel

UsersPanel

Data Flow: Settings Update Lifecycle

Cross-References

38 KiB

Raw Blame History