Errors that reach the GUI were written for the log: "ResolveURL failed:
invalid parameters", "httpGetUsingSpecificClient: response is nil",
"LocateServerRaw: invalid TYPE", "bad request", "illegal base64 data at
input byte 18". Reword the messages that can reach a user so each names
the input that was rejected (link scheme, missing password, port, server
id, request field), states the expected form for malformed input, drops
Go function names, keeps the %w chain so errors.Is/As still work, and
never echoes passwords, tokens or full share links (hosts only).
Messages the GUI string-matches ("invalid config", "the last request is
being processed") are unchanged.
1. use http://www.alibaba.com instead of https://www.youtube.com to test more accurate latency
2. now will report transparent proxy error
3. shorter timeout of closing SSR
4. optional enhanced mode and closed dns anti-pollution
5. use another port for transparent proxy instead of 12345
6. some other adjustments