Re-checked whether these four KVS tubes could move to server-side resolve like yespornvip/pornditt/porntrex. All four are reachable from the backend, but cross-IP testing showed their final CDN URLs are IP-bound to the resolving host (403 / connection refused from a different IP; fpo.xxx even embeds the resolver IP in its acctoken). Unlike the portable cdn5/twa CDNs, backend resolve cannot produce a mobile-playable URL here without a proxy, which is out of scope for the public app. - porn00: was using force_proxy resolve (violated the no-proxy stance); switched to the WebView fallback like its siblings. The ad exposure that originally motivated the proxy path is mitigated by the recent ad-filter work (AD_HOSTS + cover overlay + injected-JS ad-CDN skipping). - freshporno/pornxp/fpoxxx already on WebView fallback; comments updated with the cross-IP findings so this isn't re-investigated. - Dropped the now-unused tube extractor imports (F401). 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 | ||