docs: record browser-verified Googlevideo suffix RC

Co-authored-by: GPT-6 <gpt-6@openai.com>
This commit is contained in:
ZeusinaandGPT-6 Bot committed 2026-10-12 11:41:34 +03:00
1 parent eade051c2b
commit ac4d2b73ab
2 files changed
+53 -5

No files matched your search

+35 -4
View File
@@ -5,6 +5,35 @@ reconfigure, or stop the existing `zapret2-ss-autotune` container. The target
starts from a disabled managed baseline; `managed monitor` bootstraps the
frontend/API strategy, then discovers and applies an exact-host GGC strategy.
## Recorded Googlevideo suffix experiment (2026-10-12)
Source RC `eade051c2bc335b71b1616d697326ca4c8019d70`, immutable image
`sha256:fdb60593e29d7c337a413a47aaddfbcaaeabdeb877042c58f506d4abdc98a13b`,
isolated SOCKS `127.0.0.1:11082`: recorded journal generation3, active [1,2,3],
scope `experimental_googlevideo_suffix`. Frontend `www.youtube.com` and
thumbnail `i.ytimg.com` profiles were preserved; older targets were unchanged.
These recorded observations predate this docs commit; no deployment or fresh
network check is implied here.
Fresh signed media on `rr16---sn-n8v7znsz.googlevideo.com` returned HTTP206,
65536 bytes with MP4 `ftyp` over TLS1.2. The user confirmed browser videos work
on 2026-10-12 and accepts initial learning. The shared suffix profile is native
circular A/E: **two strategies with per-host learning**, not a single uniform
static strategy or proof of all-host cold 3/3. Its explicit operator experimental
policy persists across restart under hash/rollback guards, but is **not
family-qualified or READY**. Browser-visible images do not qualify the avatar
profile; only the thumbnail image profile is currently active.
Service-mode health already probes fresh actual images and media using both TLS
protocols. Experimental recovery deliberately does not automatically qualify or
replace this approved profile. Remaining acceptance is representative signed
media coverage (at least three hosts across two roots/prefixes, post-warmup 3/3
on both TLS protocols plus media), avatar qualification, actual restart/recreation
recovery of this suffix RC, and autonomous experimental recovery/autoqualification
policy with accurate covered-versus-qualified status. See
[PROGRESS.md](../../PROGRESS.md) for the five remaining gates. The older clean-run
PASS below does not close them.
## Provisioning
From this directory, create a private `.env` with a fresh independent password
@@ -61,7 +90,8 @@ Adaptive qualification is **post-warmup**, distinct from cold qualification;
initial connections may fail and native learning must repeat after restart.
It requires at least **three real unique signed ordinary media host samples**.
Three sample videos may all resolve to the same CDN host: that means
`DEGRADED`, no authorized googlevideo suffix, not fabricated coverage. Service
`DEGRADED`, no family-qualified googlevideo suffix, not fabricated coverage. The
explicit operator experiment above is separate from this qualification. Service
asset checks cover sampled thumbnail/avatar routes, not the whole thumbnail pool.
The current service/adaptive hardware acceptance gate is **pending**; the old
clean-run PASS below does not qualify these new modes.
@@ -144,9 +174,10 @@ bounds do not shorten the monitor's 90-minute bootstrap/recovery scan budget.
SIGTERM/SIGINT cancels and waits for the monitor before stopping target-local
zapret and Shadowsocks children. Nonretry monitor fatal exits stop the
entrypoint; technical exits and Shadowsocks failures restart from private configs
only after safe cleanup. Monitor health is YouTube Player API status through the owned SOCKS,
not video playback/SABR; GGC candidates are scoped to the exact discovered
hostname.
only after safe cleanup. Legacy monitor health is YouTube Player API status
through the owned SOCKS, not video playback/SABR; legacy GGC candidates are scoped
to the exact discovered hostname. Opt-in service health also checks actual fresh
images and media; the experimental suffix scope above is not family qualification.
## Recorded clean-run acceptance (2026-10-11): PASS