Roadmap
ibigbug opened this issue · 6 comments
More transport protocols could perhaps be listed as part of the long-term plan?
restls
:- original
rust
: https://github.com/3andne/restls - clash go impl: https://github.com/MetaCubeX/Clash.Meta/tree/Alpha/transport/restls
- original
shadow-tls
:- original
rust
: https://github.com/ihciah/shadow-tls - clash go impl: https://github.com/MetaCubeX/Clash.Meta/blob/Alpha/transport/shadowtls/
- original
v2ray-plugin
:- original
go
: https://github.com/shadowsocks/v2ray-plugin - clash go impl: https://github.com/MetaCubeX/Clash.Meta/tree/Alpha/transport/v2ray-plugin
- original
vless
:hysteria 2
:- original
go
: https://github.com/apernet/hysteria - clash go impl: https://github.com/MetaCubeX/Clash.Meta/tree/Alpha/transport/hysteria
- original
As well as more, those that have lost maintainers, or aren't used by many users, if there's a demand, integrating protocols could be considered.
tuic
- was desperated since Nov, 2023- original
go
: https://github.com/EAimTY/tuic/tree/dev - clash go impl: https://github.com/MetaCubeX/Clash.Meta/tree/Alpha/transport/tuic
- original
gun
- gRPC Tunnel over CloudFlare- original
go
: https://github.com/Qv2ray/gun - clash go impl: https://github.com/MetaCubeX/Clash.Meta/blob/Alpha/transport/gun
- original
snell
- private protocol owned bySurge
, and the latest version is4
, though open source impl is1-3
ssr
- was desperated since 2017, and many patches applied by anouther maintainer but ended in2019
- original impl
python
: https://github.com/shadowsocksrr/shadowsocksr/tree/manyuser - clash go impl: https://github.com/MetaCubeX/Clash.Meta/tree/Alpha/transport/ssr
- original impl
thank you for putting this together.
I agree that there are so many protocols and transports which we'd like to have.
i put them in a new ticket #190 and will likely to implement based off the popularity if anyone would like to ask for any one
New meta docs is here: https://wiki.metacubex.one/config/
It might be useful to understand what the config field actually does
that looks good.
we have certain level of explanations of each config https://watfaq.github.io/clash-rs/clash_doc/struct.ClashConfigDef.html
that is generated from the Rust doc string.
and i agree, it can be improved
check my project https://github.com/planetoryd/nsproxy/