Why this is a blocker
There is already another public linewatch project in the same problem space (dottorblaster/linewatch) focused on Internet/landline outage monitoring. The overlap is close enough that broad promotion under the same name would create avoidable ambiguity.
Current leading candidate
UplinkWitness
Rationale:
uplink anchors the project in Internet/WAN connectivity rather than one router vendorwitness matches the product thesis: collect local evidence of what actually failed and when- it fits the existing line: Know what actually went down.
- it remains compatible with generic Linux monitoring and optional router adapters
Initial collision check
Initial public searches found no GitHub repository named UplinkWitness and no obvious software/product using the exact UplinkWitness name. This is only an initial naming screen, not legal trademark clearance.
Candidates rejected during the initial screen:
LinkWitness — already used by active link-risk/evidence products/projectsWireWitness — already used by a network-performance monitoring projectLineWatch — direct same-name project exists in a closely related monitoring category
Before renaming
- do a final exact-name web/GitHub/package/domain screen
- confirm preferred capitalization:
UplinkWitness
- decide whether service/process identifiers stay
linewatch temporarily for upgrade compatibility or move in a later major version
- preserve migration/redirect notes for existing v1.0/v1.1 users
- rename repository and user-facing branding in one controlled change, not piecemeal
Non-goal
Do not change runtime behavior as part of the naming decision.
This issue should be resolved before a broad public launch on self-hosted/networking communities.
Why this is a blocker
There is already another public
linewatchproject in the same problem space (dottorblaster/linewatch) focused on Internet/landline outage monitoring. The overlap is close enough that broad promotion under the same name would create avoidable ambiguity.Current leading candidate
UplinkWitness
Rationale:
uplinkanchors the project in Internet/WAN connectivity rather than one router vendorwitnessmatches the product thesis: collect local evidence of what actually failed and whenInitial collision check
Initial public searches found no GitHub repository named
UplinkWitnessand no obvious software/product using the exactUplinkWitnessname. This is only an initial naming screen, not legal trademark clearance.Candidates rejected during the initial screen:
LinkWitness— already used by active link-risk/evidence products/projectsWireWitness— already used by a network-performance monitoring projectLineWatch— direct same-name project exists in a closely related monitoring categoryBefore renaming
UplinkWitnesslinewatchtemporarily for upgrade compatibility or move in a later major versionNon-goal
Do not change runtime behavior as part of the naming decision.
This issue should be resolved before a broad public launch on self-hosted/networking communities.