yosebyte：Nowhere TUI 保留 TCP/UDP 命名，不改为 SOCKS5 TCP/UDP
在 NodePassProject/Nowhere 关于「上下行独立」的问题讨论中，有用户建议把 `nowhere tui` 里的 TCP / UDP 标签改名为 SOCKS5 TCP / SOCKS5 UDP，yosebyte 回应称倾向保留现有命名：TUI 里的 TCP / UDP 表示被代理的流类型，不是底层承载，也不特指 SOCKS5 协议，改成 SOCKS5 TCP / SOCKS5 UDP 会把流量统计与代理前端耦合，反而让抽象更不清晰。他给出的模型是：TUI 的 TCP / UDP = 被代理流类型；TLS / QUIC = Vector 与 Portal 之间的承载；up / down = 各方向载荷的承载选择。
作者原文@yosebyteRegarding the TUI naming, I would prefer to keep TCP and UDP as they are.
They represent the proxied flow type, not the underlying carrier and not specifically the SOCKS5 protocol. Naming them SOCKS5 TCP and SOCKS5 UDP would couple the flow statistics to the proxy frontend and could actually make the abstraction less clear.
The intended model is:
- TCP / UDP in the TUI = proxied flow type
- TLS / QUIC = carrier between Vector and Portal
- up / down = carrier selection for each payload direction
So I think keeping these concepts separate is preferable.