Skip to content

dos:clarify fingerprint scope and proxy configuration - #56

Open
AnushLoknath wants to merge 1 commit into
tiliondev:mainfrom
AnushLoknath:docs/39-fingerprint-ip-scope
Open

AnushLoknath wants to merge 1 commit into
tiliondev:mainfrom
AnushLoknath:docs/39-fingerprint-ip-scope

Conversation

@AnushLoknath

Copy link
Copy Markdown

What this changes

Clarifies that Fortress's fingerprint corrections do not rotate exit IPs, reset IP reputation, or bypass request-velocity limits. Explains why restarting the browser or container on the same egress IP does not clear server-side limits, and why a successful request followed by 403s does not establish the cause of a block.

Documents the existing native, Docker, Python and Node proxy configuration paths, authentication limitations, browser-side egress verification, and caller-managed proxy pools. Updates the introduction, network-layer table, troubleshooting and FAQ to avoid guaranteeing access or attributing every block to IP reputation.

Closes #39.

Type

  • Docs

Checklist

  • python tools/check_patches.py passes.
  • git diff --check passes.
  • New Python and Node examples pass syntax checks.
  • New section links and the MCP configuration anchor resolve locally.
  • Limitations are documented: no automatic IP rotation and no guaranteed access.

Documentation only; runtime code is unchanged. Proxy argument forwarding was checked against the repository's launchers and SDKs, and proxy semantics against Chromium's documentation. Live proxy routing and the reported eBay behavior were not tested.

@AnushLoknath
AnushLoknath requested a review from arham766 as a code owner October 7, 2026 04:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Docs: clarify scope fingerprint spoofing vs IP-reputation/velocity blocks (proxy support?)

1 participant