Watfaq/clash-rs

Roadmap

ibigbug opened this issue · 6 comments

  • inbounds
    • http
    • socks5
    • mix port
    • #73
    • authentication
  • proxy rules
    • groups
      • relay
      • select
      • urltest
      • loadbalance
      • fallback
    • proxies
      • #161
      • ss
      • socks5
        • with TLS
      • vmess
        • ws
        • aead and non-aead
      • #70
      • ...
      • #190
        • h2
        • #69
        • tls
        • http
  • providers
    • file
    • remote
  • rules
    • domain_keyword
    • domain_suffix
    • geoip
    • ipcidr
    • port
    • #71
    • #60
  • DNS
    • clients
      • DoH
      • DoT
      • UDP/TCP
      • dhcp
    • server
    • HTTP query
  • API
    • proxies
    • configs
    • logs (TODO: log format)
    • providers
    • rules
    • #62
    • #63
  • linux support
  • arm support #180
  • #72
  • #64
  • #65
  • what else?

More transport protocols could perhaps be listed as part of the long-term plan?

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.

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

moved to #229