Differences

This shows you the differences between two versions of the page.

--- wiki:distributed_hosting [2026/10/21 03:32] – Update published releases through v7.1.20, archive older notes and correct website graph documentation wikiadmin
+++ wiki:distributed_hosting [2026/10/21 23:05] (current) – Publish v7.2.9 managed-host administration and current hosting documentation wikiadmin
@@ Line 41: / Line 41: @@
 [[updates:v7_2_1|v7.2.1]] includes the full signed native Catch catalog and compatible mode-scoped feedback, statistics and website reporting. Upgrades retain your existing room topology. A fresh Catch preset or an explicit stopped Catch configuration step is required; no extra room appears automatically. See [[lobbies:catch|Catch scope]] and the release Native Catch operator guide. After Catch state is initialized, configuration rollback retains a compatible controller/hub and data; do not restore a legacy controller over that state.
-===== Managed administration preview =====
+===== Managed administration =====
-The unpublished v7.2.9 candidate introduces durable per-room open/close/restart/configure requests and retained stopped intent. Live-safe changes apply without recreating rooms; changes needing recreation wait for the target room's safe boundary. Controller updates still need the host-wide safe empty-room gate.
+Published v7.2.9 provides authenticated central administration for managed public and private rooms. Authorized staff use the private fleet-control channel; public lobby channels never accept fleet commands. Requests carry durable IDs, installation/generation bindings and configuration revisions. Only the hosting operator can change the concurrent-room ceiling, default four.
-A default four-room concurrency ceiling includes public, private, pending and uncertain creations; the hosting operator can lower it. A lower ceiling drains naturally rather than removing occupied rooms. Mandatory managed participation replaces optional sharing/update choices only after the verified migration is installed. Private room content stays out of public projections; staff diagnostics are separate from website statistics. See [[updates:start|current publication and development status]].
+Explicit stopped intent survives updates, recovery and reboot. Live-safe settings apply without recreation; changes requiring recreation affect the target at a safe boundary. This controller release still requires the host-wide safe empty/idle update gate. Keep settings, authorization, catalogs, enrollment and history; do not reinstall or clear ownership to force updates.
+Managed participation includes shared ratings/statistics, staff-only diagnostic/chat reporting, automatic updates and central room administration. These have no separate in-product opt-outs in migrated managed hosts. Older hosts retain legacy behaviour until upgraded. Private-room information and credentials remain excluded from public projections. Full owner map exclusions are mirrored into compatible signed feeds; only map IDs leave private moderation records.
+Discord cards retain artwork, maps, settings and players without map progress; website progress remains. See [[updates:v7_2_9|release notes and qualification limits]], [[status:start|currently running rooms]] and the matching GitHub installer guides for exact protected operator commands.