feat(tune): add proposal-only Googlevideo scans
Co-authored-by: GPT-6 <gpt-6@openai.com>
This commit is contained in:
1 parent
7fad9b3b5c
commit
6220eb0b31
10 files changed
+638
-27
No files matched your search
@@ -2,6 +2,41 @@
|
||||
|
||||
Go CLI for scanning and checking YouTube TLS bypass strategies with `blockcheckw`.
|
||||
|
||||
## Exact cache-host proposal
|
||||
|
||||
```sh
|
||||
zapret-autotune tune googlevideo --video-id dQw4w9WgXcQ --proxy socks5://localhost:1080
|
||||
```
|
||||
|
||||
Both flags are required. The validated Android 21.02.35 player request discovers
|
||||
exactly one current cache hostname through the explicit proxy. `blockcheckw`
|
||||
then scans only that hostname for TLS1.2/TLS1.3, checks the shortlist with
|
||||
`--take 10 --passes 3`, ranks fully passing strategies by measured data-transfer
|
||||
speed/latency, and checks the exact combined arguments 3/3 on both protocols.
|
||||
The proxy is for discovery; blockcheckw uses its own network path, not that proxy.
|
||||
No Selectel speedtest is used. This is not a YouTube playback/SABR test.
|
||||
|
||||
Only after successful transactional persistence does this command print one
|
||||
inert `NFQWS2_OPT` profile filtered by the **exact discovered hostname**, never
|
||||
the `googlevideo.com` wildcard. Cache hosts rotate; one host is not wildcard
|
||||
evidence. GGC proposals use `--hostlist-domains=^<discovered-host>`: the `^`
|
||||
prefix disables Zapret2's default subdomain matching, so untested subdomains
|
||||
are not included. Only validated lowercase `*.googlevideo.com` hostnames are
|
||||
accepted; commas and a leading `^` in the discovered hostname are rejected.
|
||||
Schema-v3 candidates use group `googlevideo`, one exact endpoint, and
|
||||
both endpoint×TLS measurements with raw JSON and timestamps. An additive v3
|
||||
cache-run journal records failed attempts without candidates and successful
|
||||
attempts atomically with their candidate/evidence; legacy frontend runs keep
|
||||
their existing target constraint. Database failures emit no options.
|
||||
`history` and `strategies youtube` include the cache group and exact endpoint;
|
||||
`status` still describes the legacy frontend journal only.
|
||||
|
||||
Signed URLs are not printed. Scanner diagnostics are retained in restricted
|
||||
artifact files rather than relayed to the terminal. No configuration is applied,
|
||||
no profile is marked active, and no service is restarted. The staged pipeline is
|
||||
scan/propose now → eventual install → monitoring/recovery; the latter stages are
|
||||
**not implemented**. No-argument `tune youtube` remains frontend-only and unchanged.
|
||||
|
||||
## Cache-host discovery
|
||||
|
||||
```sh
|
||||
@@ -60,8 +95,8 @@ Each newly successful tune saves its exact verified combined frontend profile fo
|
||||
in the same transaction as the existing run. Qualification requires every declared
|
||||
endpoint to pass exactly 3/3 for both TLS1.2 and TLS1.3, with full success/coverage.
|
||||
Existing v2 history is unchanged and is not backfilled into independent candidates.
|
||||
Candidates have no active/installed state; apply, monitor and GGC integration remain
|
||||
unimplemented.
|
||||
Candidates have no active/installed state; apply and monitor remain unimplemented.
|
||||
The explicit `tune googlevideo` path adds exact-cache proposals only.
|
||||
Proposed runs store a SHA-256 fingerprint of validated arguments with separator
|
||||
whitespace normalized and argument order preserved; repeated proposals retain
|
||||
separate history rows. Failed runs have no fingerprint. Version 1 history is
|
||||
|
||||
Reference in new issue
Block a user