martbost
b3385ca3f8
Manson asked whether the training videos could be in other languages. A real dub means re-rendering every video per language: translated Romance-language speech runs 15-25% longer than English and these are slide videos with fixed beat timings, so swapped audio drifts off what is on screen. That turns 15 files into 75 and makes every future lesson edit a five-way job. Captions keep ONE video and add small text tracks beside it, so editing a lesson re-captions that lesson only. tools/captions.mjs: ffmpeg pulls the audio, ElevenLabs Scribe transcribes with word timings (the same STT we already use to verify voiceovers), words are grouped into SENTENCES, and only then translated. Translating cue-by-cue is why most auto-captions read badly at cue boundaries. Translation goes through our own /api/public/translate, so every phrase caches forever in translations.json and costs once across the site. The STT response is cached on disk because it costs money; never pay for it twice. Language choice is evidence, not instinct. The translation cache shows real member demand: Italian and French far ahead, then Spanish, then GERMAN - which beats Portuguese by more than double, the opposite of what we assumed. Proof of concept is Italian on the 5-minute overview. Captions are deliberately NOT on by default. An English reader does not want them forced over the picture; someone who already switched the site to Italian almost certainly does. public/vtt-lang.js shows the track matching their 🌐 choice and leaves the player's CC button to do the rest. Two bugs this caught in my own code, both found by reading the output: - the line wrapper truncated each cue to two lines and SILENTLY DELETED the overflow, so "the whole plan fits in one sentence" shipped as "fits in" then "sentence". It now chunks by the real wrapped line count and never drops a word. - a one or two word tail ("sentence." alone on screen) folds back into the previous cue. The suite asserts all 780 transcript words survive into the English track. Also: .vtt had no Content-Type mapping, so it served as octet-stream and browsers silently ignore such a track. qa/captions-e2e.mjs (12 assertions) reads the parsed cues back out of the player rather than trusting the markup, which is the only way to catch that class of failure. profiles-unit 28 and gate-e2e 33 still green. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
RM Circle Premium — Crypto Team Build Sponsor Router
A small deployable Node/Express app with:
/— evergreen advertising/bridge page/start— dynamic onboarding page with the current team sponsor/admin— password-protected sponsor queue manager- JSON-file persistence suitable for a Docker volume
Core workflow
- Traffic lands on the evergreen bridge page.
- Visitors click Get Started.
/startreads the active sponsor from the server and builds the RM Circle referral link dynamically.- In
/admin, increment a sponsor's direct count as joins are verified. - When a sponsor reaches 2, click Qualified.
- The next waiting sponsor becomes active immediately—no HTML or ad changes required.
Default seeded queue
The seed data reflects the working Crypto Team Build priority list at build time:
- ID 30 — Orlando (active)
- ID 36 — Mad Dog
- ID 35 — Michael Camire
- ID 32 — Melissa
- ID 34 — Janie
You can change, reorder, add, or delete sponsors in /admin.
Local run
cp .env.example .env
# edit .env and set a strong ADMIN_PASSWORD + SESSION_SECRET
set -a && . ./.env && set +a
npm start
Open:
http://localhost:3000/http://localhost:3000/starthttp://localhost:3000/admin
Docker / Coolify
This project includes a zero-dependency Node server, Dockerfile, and docker-compose.yml. No npm package download is required.
Coolify recommendation
- Create a new application from this source/repository.
- Use the Dockerfile or Compose deployment.
- Add environment variables:
ADMIN_PASSWORD— strong unique passwordSESSION_SECRET— long random stringNODE_ENV=productionDATA_DIR=/app/data
- Persist
/app/datausing a volume. - Point your domain/subdomain at port
3000through Coolify's normal proxy/domain configuration. - Open
/admin, sign in, and verify the queue before sending traffic.
Sponsor referral URL
The default base is:
https://app.thermcircle.com?ref=
The app appends the current sponsor ID, for example:
https://app.thermcircle.com?ref=30
Change the base URL at any time in Admin → Public Page Settings without editing code.
Important operational behavior
The app intentionally does not auto-qualify sponsors based on clicks or blockchain activity. A team admin verifies the actual placement and clicks Qualified. This prevents an ad click or abandoned transaction from rotating the sponsor queue incorrectly.
Safety and compliance notes
The public pages include risk language, avoid guaranteed-income claims, and remind users never to disclose a MetaMask Secret Recovery Phrase. The onboarding page points to the official MetaMask website and identifies Polygon Mainnet as chain ID 137 with POL as the native gas token.
This app does not custody crypto, request wallet seed phrases, execute transactions, or store private keys.