alireza0：s-ui 补上 Snell 的客户端支持，Clash 订阅仍会跳过 Snell 节点
在答复关于 Snell 的疑问时表示这不是缺陷：Snell 在 v1.6.0 作为协议加入，但客户端支持从未实现，因此它在 Clients 页面没有位置。现在已完成——Snell 入口可分配给客户端，每个客户端在入口共享 PSK 之外还有自己的 Snell key，JSON 订阅会携带该节点；更新后首次启动时会自动为已有客户端生成 Snell key，无需手工处理。他同时说明 Clash 订阅仍会跳过 Snell 节点，因为 Clash 没有放置每用户 key 的位置，JSON 订阅不受影响。该改动将在下一个版本发布。
作者原文@alireza0Thanks for the report. It was not a bug — Snell was added as a protocol in v1.6.0, but client support for it was never implemented, so it had no place in the Clients page.
That is now done. Snell inbounds can be assigned to clients, each client gets its own Snell key alongside the inbound's shared PSK, and JSON subscriptions carry the node. Existing clients are given a Snell key automatically on first start after the update, so nothing needs to be done by hand.
Clash subscriptions still skip Snell nodes, since Clash has no place for a per-user key. JSON subscriptions are unaffected.
Coming in the next release.