Skip to content

freepro v0.1.7

Choose a tag to compare

@menscho menscho released this 05 Sep 13:12
· 22 commits to main since this release

Public proxy routing rebuilt on the proxy_pool model

The pool no longer confuses "the model provider is rate-limiting me" with "this proxy is dead" — that confusion was draining the pool whenever an upstream answered 429 through many egresses. The routing is rebuilt the way the well-known open-source proxy_pool project works:

  • 26 proxy-list sources (up from 22): the big aggregates plus frequently-refreshed feeds and latency/uptime JSON, feeding a reservoir of up to 80,000 candidates.
  • A background getter re-pulls the lists every 5 minutes; a background tester continuously validates both raw candidates and pooled proxies.
  • Validation is against a neutral HTTPS target (a tiny 204 endpoint), never against your model provider. A proxy's health reflects whether the proxy itself can reach the open internet — an origin 429 can never mark proxies dead.
  • Proxies are reused until they're actually unusable: a route is dropped only after it repeatedly fails the neutral probe or transport; a proxy that recovers is re-promoted (success lowers its failure score, proxy_pool-style).
  • If the pool runs low, a fresh fetch starts immediately — it never waits for the next cycle.
  • When an origin throttles through several distinct egresses, freepro pauses briefly and returns a clear 429 telling you the upstream is rate-limiting — it never blames or deletes the proxies, and your API keys are never touched.

Validation

356 unit tests plus the transport fault-injection, concurrent burst, sustained-load, single-instance and dashboard verifiers pass. A live warm-up run validated real HTTPS routes from the 26 sources through the neutral probe.

Downloads

Windows: download and run the standalone .exe. Linux and macOS: download the matching architecture, make it executable with chmod +x, then launch it. The app opens its GUI in your browser. SHA-256 checksums are included.