Skip to content

Add Swiftproxy as sponsor with disclosure - #17

Merged
stretchcloud merged 1 commit into
mainfrom
docs/sponsors-swiftproxy
Aug 12, 2026
Merged

Add Swiftproxy as sponsor with disclosure#17
stretchcloud merged 1 commit into
mainfrom
docs/sponsors-swiftproxy

Conversation

@stretchcloud

Copy link
Copy Markdown
Owner

Adds Swiftproxy as the first DeepScrape sponsor, per the agreed placement.

Placements

  1. Above the fold — new ## 💛 Sponsors section between the intro and Features, with the banner, description, and disclosure.
  2. Setup/configuration — a "Recommended proxy provider" line under the PROXY_LIST example in the proxy-rotation section, where readers are actively wiring up proxies.
  3. Provider catalog — listed under "Where to Get Proxies → Residential Proxy Providers".

Disclosure

Every placement carries a (Sponsored) label, and the Sponsors section states plainly that sponsorship buys placement and a labeled recommendation — not influence over code, defaults, benchmarks, or comparisons.

Notes

  • Banner is committed under assets/sponsors/ rather than hotlinked, so the creative stays under this repo's control and cannot be swapped post-hoc.
  • The Sponsors section includes an HTML comment with the add-a-sponsor recipe, so additional sponsors are a copy-paste.
  • Docs-only change; no code touched.

Adds a Sponsors section above the fold with the Swiftproxy banner,
a "Recommended proxy provider" line in the proxy-rotation setup
section, and a listing in the residential provider catalog.

Every placement carries a "(Sponsored)" label, and the Sponsors
section states that sponsorship buys placement only -- not influence
over code, defaults, benchmarks, or comparisons.

The banner is committed under assets/sponsors/ rather than hotlinked
so the creative stays under this repo's control.
@stretchcloud
stretchcloud merged commit e563aac into main Aug 12, 2026
1 check passed
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.

1 participant