Re-investigated with the proper method (Chrome DevTools network capture + cross-IP test via Bright Data residential proxy + curl_cffi browser-TLS) instead of guessing. freshporno's real flow is get_file -> 302 -> cdn4.freshporno.org/remote_control.php -> 206 video/mp4. The CDN URL is PORTABLE cross-IP (a token generated from one residential IP replays fine from the VPS and from a different Bright Data residential IP), it only rejects non-browser TLS fingerprints (plain curl -> 000, curl_cffi chrome / ExoPlayer -> 206). In #20 I tested the final URL with a standalone plain curl, got 000, and wrongly concluded "unreachable from residential" -> kept it on the WebView fallback, which barely worked (ad-heavy page, flaky). That false negative is the regression the user reported. freshporno is function/0 KVS, so _kvs.resolve_kvs (which uses curl_cffi chrome) already decodes + resolves it to a portable mp4 — switch to backend resolve like yespornvip/pornditt: native, multi-quality, no proxy, no WebView. Verified: backend resolve returns 3x mp4 (1080/720/480, mobile_direct) + cdn 206; user confirmed native playback on device. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| api | ||
| connectors | ||
| extractors | ||
| models | ||
| normalize | ||
| resolve | ||
| scheduler | ||
| templates | ||
| __init__.py | ||
| auth.py | ||
| config.py | ||
| db.py | ||
| ingest.py | ||
| main.py | ||