FEAT-083 - Connection Checker Based On Public Reachability Polling

Decision

Record this eMuleAI feature as WONT_DO for eMuleBB.

The general idea of connection diagnostics is valid, but eMuleAI's ConChecker style is not the right product behavior for eMuleBB: it performs public reachability polling and can become a hidden dependency on a third-party endpoint. eMuleBB should prefer passive diagnostics, local socket/bind status, server/Kad state, MiniUPnP/PCP status, and explicit user-triggered tests.

eMuleAI References

Review source: eMuleAI commit 8e34bdec2b7e4fe9e4307df9d80f691804be99ed.

• checker lifecycle and worker: ConChecker.cpp, ConChecker.cpp
• preference default: Preferences.cpp

Rationale

• Hidden external polling is a privacy and reliability concern.
• A hardcoded endpoint can break diagnostics when the endpoint is blocked, down, intercepted, or unavailable on controlled networks.
• Current roadmap diagnostics should stay local and explainable unless the user explicitly launches a test.

Replacement Direction

Use FEAT-032 and connectivity-modernization diagnostics for local network evidence: bind/interface state, UPnP/PCP lease state, server connection state, Kad state, and optional explicit port test.