Files
hottub/docs
Simon c40b48b0db Fix six dead providers (shooshtime, hdporn92, camsoda, sextb, supjav, hentaimama)
- shooshtime: update parse_list_videos selectors for the site's redesigned
  markup (div.card / a.title / a.image img / div.duration / div.list div.box
  / div.name a.text)
- hdporn92: mirror the site's own links.hls4||hls3||hls2 fallback and scan
  every P.A.C.K.E.R. block instead of assuming the first one is the player
  block; prefer a genuine .m3u8 candidate over a decoy .txt one
- camsoda: replace naive first-`{`/last-`}` JSON extraction with a proper
  balanced-brace scan so trailing wrapper markup can't corrupt the parse
  ("key must be a string")
- sextb: fix mirror_url() double-prefixing the scheme when building Jina
  mirror URLs (produced a malformed https://r.jina.ai/http://https://... URL)
- supjav: switch curl_cffi impersonation from chrome to safari18_0 - Cloudflare
  blocks the chrome/firefox profiles outright but passes Safari
- hentaimama: resolve every card on a listing page (not just the first
  perPage) and truncate after filtering, so a bulk "Coming soon" placeholder
  batch at the front of the feed no longer empties the whole page; report a
  provider error if literally every candidate fails

Refreshes graphify's graph and docs/provider-catalog.md with the new
technical details for all six providers.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QTqf6orbHZ9rFFpVpcgzcR
2026-09-22 13:56:36 +00:00
..
2026-04-03 17:20:11 +00:00
2026-04-10 22:57:27 +00:00
2026-09-07 15:25:03 +00:00
2026-09-07 15:25:03 +00:00

Hottub Docs

This folder is the fastest handoff path for anyone adding or repairing a channel.

Start here:

  1. Read architecture.md for the server flow, request lifecycle, and core types.
  2. Read provider-playbook.md — its top "Best Practices (Living)" section is the cross-cutting rule set to internalize first, then follow the rest of the playbook for the exact process to add a new provider or proxy.
  3. Use provider-catalog.md to find the closest existing implementation to copy.
  4. Use docs/hottubapp/*.html when you need the client-facing API contract for status, videos, or uploaders.
  5. Only then touch prompts/new-channel.md; it assumes the docs above exist.

Recommended local workflow:

cargo check -q
HOT_TUB_PROVIDER=<channel_id> cargo check -q
HOT_TUB_PROVIDER=<channel_id> cargo run --features debug

Useful runtime baseline:

DATABASE_URL=hottub.db
RUST_LOG=info
PROXY=0
BURP_URL=http://127.0.0.1:8081
FLARE_URL=http://127.0.0.1:8191/v1
DOMAIN=127.0.0.1:18080
DISCORD_WEBHOOK=

Key facts:

  • Hottub is a Rust ntex server with providers under src/providers/.
  • build.rs controls compile-time provider registration.
  • /api/videos is the main provider execution path.
  • /proxy/... exists for sites whose direct media or thumbnails need a redirect/proxy layer.
  • Only three providers currently implement /api/uploaders: hsex, omgxxx, and vjav.
  • Uploader IDs should be namespaced like <channel>:<site-local-id> so /api/uploaders can route directly.