You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for reaching out! Outline Client supports connecting to QUIC traffic, which is based on UDP, but shadowsocks uses its own format to tunnel data, not QUIC or UDP.
Are you requesting that QUIC be used as the tunneling method itself? This is very similar to the MASQUE protocol, which we are exploring adding to Outline as an alternative to shadowsocks.
Thanks for reaching out! Outline Client supports connecting to QUIC traffic, which is based on UDP, but shadowsocks uses its own format to tunnel data, not QUIC or UDP. Are you requesting that QUIC be used as the tunneling method itself? This is very similar to the MASQUE protocol, which we are exploring adding to Outline as an alternative to shadowsocks.
Yes, I hope to use quic as the main transmission protocol, tcp is too slow, and I hope to better break through the firewall, such as China.
Very exciting! We're working to integrate the new Outline SDK into Outline Client, so ideally any new protocols would be housed in the SDK. If you're interested in contributing to the code, please let us know so we can discuss how to make that happen!
Use QUIC to transfer data, QUIC is faster, TCP is slower, YouTube and Google sites already support HTTP2 QUIC HTTP3 access.
The text was updated successfully, but these errors were encountered: