therealaleph
44854fad84
- Adds `block_quic = true` config flag for client-side QUIC drop. SOCKS5 UDP relay refuses UDP/443 datagrams; browsers fall back to TCP/HTTPS through the relay. Opt-in. Thanks @w0l4i - Workflow now auto-refreshes the in-repo releases/ folder on each release tag, so Iranian users behind GitHub-Releases-page filtering can download via Code → Download ZIP. Practice was started before v1.1.0 then dropped; resumed at user request. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2.5 KiB
• گزینهٔ جدید block_quic در config برای رد کردن client-side QUIC (#213): با "block_quic": true در config.json، listener SOCKS5 UDP هر datagramی به مقصد port 443 (یعنی HTTP/3-over-UDP) رو silent drop میکنه. browser به TCP/HTTPS fallback میکنه (که از مسیر CONNECT معمولی رد میشه و از relay میگذره). برای کاربرهایی که QUIC TCP-meltdown رو در Full mode تجربه میکنن (پهنای باند < 1 Mbps در عوض > 50 Mbps با TCP/HTTPS) خوبه. بهصورت opt-in (پیشفرض false). ممنون از @w0l4i
• release artifacts دوباره به پوشهٔ releases/ در مخزن commit میشن (به درخواست کاربر تلگرام): پس از v1.1.0 این عادت متوقف شده بود — حالا بعد از هر release tag، workflow خودکار فایلهای pre-built رو در پوشه releases/ بهروزرسانی میکنه. کاربرانی که به صفحه GitHub Releases دسترسی ندارن (بهخاطر فیلتر در ایران) میتونن از طریق Code → Download ZIP به فایلهای آخرین نسخه برسن. صفحه release رسمی همچنان artifactهای versioned رو داره — این پوشه fallback هست
• New block_quic config option for client-side QUIC drop (#213): set "block_quic": true in config.json and the SOCKS5 UDP relay silently drops any datagram destined for port 443 (HTTP/3-over-UDP). The client's QUIC stack retries a couple of times and then falls back to TCP/HTTPS, which goes through the regular CONNECT path and through the relay. Useful for users seeing QUIC TCP-meltdown in Full mode (sub-1 Mbps where TCP/HTTPS does 50+). Opt-in (default false). Thanks @w0l4i
• Release artifacts now committed back to the in-repo releases/ folder (per Telegram channel request): the practice was stopped after v1.1.0 — now after every release tag, the workflow auto-refreshes releases/ with the pre-built binaries. Users behind GitHub-Releases-page filtering can grab the latest version via Code → Download ZIP. The official release page still has versioned artifacts; the in-repo folder is the fallback path