captchaforge 0.2.36

[DO NOT USE — UNDER ACTIVE DEVELOPMENT, NOT PRODUCTION-READY] Captcha solver scaffolding for chromiumoxide-driven browsers. The architecture is in place (vendor solvers, retry-loop iframe walking, VLM provider abstraction, real-WAF bench harness) but the live-vendor success rate is still 0% — Cloudflare Turnstile / hCaptcha / reCAPTCHA detect us at a TLS / CDP fingerprint layer that no flag-based stealth has cleared. Watch the repo; do not depend on this for any real workload.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48

# captchaforge marketing kit

Drafts + copy-ready assets for launching captchaforge publicly.
Fire these one at a time + measure the response.

## Ready-to-fire

| Surface | File |
|---------|------|
| Hacker News launch post | [`hn-launch.md`](hn-launch.md) |
| Reddit r/rust + r/webscraping | [`reddit-launch.md`](reddit-launch.md) |
| Twitter / X thread | [`twitter-thread.md`](twitter-thread.md) |
| Comparison page (vs nopecha / 2captcha / CapSolver) | [`comparison-page.md`](comparison-page.md) |
| Awesome-list PRs (awesome-rust, awesome-scraping) | [`awesome-list-prs.md`](awesome-list-prs.md) |
| Video demo script | [`video-demo-script.md`](video-demo-script.md) |
| Blog post: "How we solve real captchas in Rust" | [`blog-post.md`](blog-post.md) |

## Brand fundamentals

- **Name**: captchaforge
- **One-liner**: "Open-source CAPTCHA solver for headless browsers — Cloudflare Turnstile, reCAPTCHA, hCaptcha, sliders, audio, PoW. Rust."
- **Three-bullet pitch**:
  1. The only open-source solver that ships **every vendor**
     (Akamai, DataDome, PerimeterX, GeeTest, AWS WAF, Arkose, plus
     CF/Google/hCaptcha).
  2. **Pattern-learning** — the chain learns per-domain + per-stack
     which solver wins, so success rates compound over time.
  3. **Three consumption modes**: CLI, library, HTTP API; Python +
     Node bindings + WASM in-page; container + Helm chart for
     ops.

## Fire order

1. Land 0.3.0 with real-world bypass numbers (GAP-4 done first).
2. Ship docs site (UP-25 — captchaforge.santh.dev live).
3. Twitter thread.
4. Hacker News on a Tuesday morning UTC.
5. Reddit r/rust + r/webscraping the day after HN.
6. Awesome-list PRs the same week.
7. Blog post + video demo a week later.

## What NOT to do

- Don't promise specific bypass percentages we haven't measured.
- Don't badmouth the SaaS competitors; the comparison page shows
  fact-based trade-offs.
- Don't post before the bypass scorecard is live; the first
  reader question is always "what's the success rate".