feat: SOCKS5 UDP ASSOCIATE relay, adaptive route engine, transport scanner & docs; fix YouTube comments#55
Open
Aria00pp wants to merge 6 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary of Changes
Motivation
Description
Testing
Known Issues
Higher script.google.com relay gas (quota consumption)
The new UDP relay and adaptive transport probing increase traffic through the Apps Script exit node, which can lead to accelerated consumption of the scripts.google.com relay gas (Google Apps Script daily quotas). This is especially noticeable during active UDP sessions and when running the adaptive scanner.
We are tracking this for future optimization.
UDP gaming and real‑time workload validation pending
The SOCKS5 UDP ASSOCIATE relay has passed unit, protocol handshake, and basic smoke tests, but has not yet been validated under real‑world gaming or high‑frequency real‑time communication workloads (e.g., competitive FPS, VoIP, low‑latency streaming). Performance characteristics such as relay‑induced jitter, packet reordering, throughput ceilings, and long‑session stability under actual game traffic remain unverified.
We recommend treating the UDP path as experimental for gaming purposes and conducting targeted latency/jitter tests under your own network conditions before relying on it for latency‑sensitive titles. Feedback and measurement data are very welcome and will help harden the relay for production gaming use.