Proxying
Yosoi does not expose a first-class proxy policy yet. Today, configure proxies at the HTTP, browser, or deployment layer you already control, then pass the resulting HTML or fetcher behavior into Yosoi. First-class proxy settings are tracked on the Roadmap.
Current Support
- Simple HTTP fetches can inherit environment-level proxy settings supported by the underlying HTTP client.
- Browser-backed fetches should be configured where the browser runtime is launched.
- Yosoi selector discovery, validation, and extraction work the same way after the page has been fetched.
Planned Scope
The planned proxy feature should make proxy routing explicit in policy/config, preserve provenance in debug output, and avoid hiding network behavior behind selector logic.
A Note on Responsible Use
Yosoi is designed for respectful scraping. When routing requests through proxies, please do not use TOR△ exit nodes or public SOCKS5○ servers. These are shared public IP systems; using them for scraping loads volunteer-run infrastructure with automated traffic it was not designed to carry, and it degrades the experience for everyone who relies on those networks for legitimate privacy use.
If you need to route requests through multiple IPs, use dedicated residential or datacenter proxies from providers that explicitly offer them for this purpose.
FAQs
Does Yosoi have a proxy flag today?
No. Use environment or browser-runtime proxy configuration today. A first-class Yosoi proxy policy is planned.
Should I use public proxy lists?
No. Public proxies are unreliable, often abusive to shared infrastructure, and can create legal or operational risk. Use dedicated providers that explicitly allow your use case.
References
△ Tor Project. The Tor Project. Free, open-source software enabling anonymous communication online. https://www.torproject.org/
○ SOCKS5. IETF RFC 1928. Protocol for routing network packets between a client and server through a proxy. https://datatracker.ietf.org/doc/html/rfc1928