Observation while working on the name: mir-signal is named for WebRTC signalling, which is technically exact. But in a security/privacy product, many readers parse "Signal" as the messenger app — an unlucky ambiguity for the one component whose whole point is that it cannot read anything.
Not urgent and not decided; capturing it so it is not lost. Options: keep it (accurate, and the docs explain), or rename the binary at some pre-1.0 boundary. Note the repo already carries naming debt — the Go module path is still github.com/srcful/terminal-relay/go — so any rename should be considered together with that, not piecemeal.
Observation while working on the name:
mir-signalis named for WebRTC signalling, which is technically exact. But in a security/privacy product, many readers parse "Signal" as the messenger app — an unlucky ambiguity for the one component whose whole point is that it cannot read anything.Not urgent and not decided; capturing it so it is not lost. Options: keep it (accurate, and the docs explain), or rename the binary at some pre-1.0 boundary. Note the repo already carries naming debt — the Go module path is still
github.com/srcful/terminal-relay/go— so any rename should be considered together with that, not piecemeal.