Similar to https://stim.io/apps/direct/create — we need a system that tells users the closest body or district and their latency (ms) for Hydra ExperienceNet. This would help users identify which streaming endpoint offers the best connection.
Plan review: accepted
Nebula's reasoning: Self-contained feature with clear approach — adds latency measurement endpoints to existing hydracluster infrastructure.
Implemented latency-based proximity checker.
Changes:
Commit: f727d8e
Grooming: recategorized bug → feature, set priority to medium, changed project from hydrabody → hydracluster, rewrote title and description (fixed typos, malformed URL, clarified intent)
Nebula's reasoning: This is a feature request for a new latency/proximity detection system, not a bug report. The original title was auto-generated from the description and contained a duplicated/malformed URL. Description had multiple typos (systen, clostest, distrivt). Assigned to hydracluster since districts and node proximity are managed there. Priority set to medium — useful UX enhancement but not blocking any current workflows.