Repository navigation
Make directory changes appear promptly #14
Description
Reachable peers already push changes through their gateway subscriptions, but directory-backed listings (hosts that aren't currently reachable) still refresh every 30 seconds, so a new channel can take that long to appear there. Push changes instead of polling if that matters.
Tracked by #58. Migrated from TODO.md — During dogfooding.
Activity
iamnbutler commentedon Oct 15, 2026
Status: still polling, every 30s (
HEARTBEATinapps/host/src/directory.ts). Since #283, a peer that becomes unreachable keeps its last channel list, shown as offline, even without a directory, so this now affects only hosts that were never reachable. Scenario 18 of the two-person study (#218) will measure the delay.feat(directory): add a per-project Lobby cell beside the directory
feat(host): push channel lifecycle through project lobbies
feat(directory): add a per-project Lobby cell beside the directory
feat(directory): add a per-project Lobby cell beside the directory (#335
feat(host): push channel lifecycle through project lobbies
feat(host): push channel lifecycle through project lobbies (#337)
iamnbutler commentedon Oct 15, 2026
Done through project lobbies. Hosts now push channel lifecycle (created, archived, renamed, moved, summarized, ran, deleted) through the lobby (#337), which replaces the 30 s directory poll while the lobby is live. This was verified in study scenario 25, and in 26b B's sidebar updated live on a delete. The production directory still needs the
v2Lobby migration deployed (#17).