factorio: collect friend-group factorio.com handles + populate server-whitelist.json #79
Labels
No labels
burndown-2026-06
burndown-2026-08
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/advocate
role/director
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/science
role/sysadmin
state
ambient
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/infrastructure#79
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally filed by @coilysiren on 2026-05-01T11:14:02Z - https://github.com/coilysiren/infrastructure/issues/81
Goal
Replace the stub
server-whitelist.jsonwith the actual friend-group factorio.com handles.Context
The Sirens factorio server (kai-server) is running with whitelist enforcement on (
--use-server-whitelist). Today the whitelist is just["coilysiren"]because no one has shared their factorio.com handle yet.Action
Collect handles from the channel - the people who showed interest are already in there. Drop them into:
After updating, the server picks up the whitelist on next restart (or via
/whitelist add <name>from the server console / RCON if wired).Tracked file (canonical)
The whitelist is live-edited on kai-server, not tracked in git (single source of truth + nightly s3 backup covers durability). If we want it in git, that's a separate decision - whitelist contents leak factorio.com handles to anyone with repo read.
Done when
Tracking from: #77
Iceboxed in the 2026-05-29 backlog burn-down: factorio whitelist handles, blocked on friends. Reopen anytime if it becomes real.