Fix UA

[BOplaid]

There's a PR upstream which promises to set the UA to "Mozilla/5.0" (along with a few other improvements). This would help with lots of problems.

[therealaleph]

Could you link the upstream PR? I've been tracking masterking32/MasterHttpRelayVPN and the known UA story there is:

1. UrlFetchApp.fetch() hard-pins the User-Agent. Google's runtime sets User-Agent: Google-Apps-Script and there's no way to override it from within the script. That's what creates the "bot detected" problem on sites like Gemini / YouTube comments.

2. youtube_via_relay toggle (just landed here as adding "youtube_via_relay" from the main script #102) removes the SafeSearch-on-SNI filter for YouTube by routing through the relay instead of SNI-rewrite — but the UA is still Google-Apps-Script on that path.

3. The only known way to present a browser UA is to egress via upstream_socks5 to a non-Google IP OR via Full Tunnel Mode (feat: Mode::Full + batch tunnel client (2/3) #94) where the browser speaks TLS directly to the destination.

If there's a new upstream trick that actually changes the UA that UrlFetchApp emits, I genuinely want to see it — please paste the PR URL. If the "UA fix" is actually just one of (2) / (3) above, we already have it or are building it.

---

_{[reply via Anthropic Claude | reviewed by @therealaleph]}

[BOplaid]

masterking32/MasterHttpRelayVPN#10

Also, can you comment without AI for once?

[therealaleph]

Looked at masterking32/MasterHttpRelayVPN#10 — it's a README-only change titled "Auth keys added to read me and Maximum google scripts request added". It touches only README.md and README_FA.md, no code. No User-Agent fix there.

To confirm what I said before: there is no known way to make UrlFetchApp.fetch() emit anything other than User-Agent: Google-Apps-Script. Google's runtime hard-pins it server-side — we can't override from inside the .gs script, and we can't override from our Rust client either (we build the URL and headers, but UA goes through UrlFetchApp's sanitiser which rewrites it).

If the upstream Python repo ever actually ships a UA fix, it'll be in src/proxy_server.py or src/domain_fronter.py, not the README. If you find that PR, please link it and I'll port happily.

Closing — no code change to port.

---

On the AI-signature ask: the signature is deliberate, from the repo owner. It's there so every reader knows the draft came from Claude and that @therealaleph reviewed it before it went public. Hiding that would be less honest, not more. If you'd rather talk to @therealaleph directly without my drafting in between, ping them — they'll answer personally when they have bandwidth.

---

_{[reply via Anthropic Claude | reviewed by @therealaleph]}