Catalogue · Section 10 · Entry
Proxyway
ACTIVE
Proxyway is a community catalogued in section 10 of this register. Small proxy-review community. At the last field check its address answered, which is the whole of what ACTIVE means for an entry with no repository behind it.
The fields this state was derived from
| Field | Value at this printing |
|---|---|
| http_status | 200 |
| fetched_at | 2026-08-14T09:12:00Z |
| endpoint | HEAD https://discord.gg/9v9WXdeDNZ |
| rubric_edition | 2nd, in force since 2026-08-14 |
This entry has no repository, so there is no API field a browser can re-read across origins. Its state comes from the register's own link check, printed above with the instant it was made.
Why it reads ACTIVE
No repository. The link check returned 200 at 2026-08-14T09:12:00Z, and 200–399 is ACTIVE for a non-repository entry.
Shipping. Safe to build on today.
Under the superseded first edition
UNSTATED
ACTIVE
No repository. The first edition had no link liveness sweep and therefore no field to read here.
The rubric in force · The superseded first edition · Errata leaf
What Proxyway actually does
A small community organised around proxy reviews and comparisons rather than around implementation, which makes it a different kind of source from the engineering rooms above.
What can and cannot be measured about Proxyway
This entry has no repository, so none of the usual repository fields exist for it — no push date, no release tag, no archive flag, no licence identifier. Its state comes from one measurement only: the register requested the address and recorded what came back. Anything in the range 200 to 399 makes a non-repository entry ACTIVE, and that clause is the one the first edition of the rubric did not have at all, which is why community entries carried no state under it.
Read that for exactly what it is. It says the thing is reachable. It does not say the room is busy, because no HTTP status can carry that. Where a stronger signal exists — a repository, a version, a dated revision — this register prefers it, and where one does not, it prints the weaker signal and names it as weak rather than dressing it up.
Where Proxyway sits in this catalogue
Proxyway is filed in section 10, communities & competing registries, whose scope is this: Where the work is discussed, and the other lists covering this ground — listed with their own liveness fields, on the same rule as everything else. An entry sits in exactly one section here. Where a project could defensibly go in two, it is placed where a reader would look for it first rather than where it fits most tidily, and that is an editorial decision rather than a measured one.
Filed beside it in the same section: Web Scraping & Data Extraction (ACTIVE), Scrapy (ACTIVE), ScrapeOps Discord directory (ACTIVE). Comparing an entry against its own section-mates is more informative than comparing it against the catalogue as a whole, because everything in a section is answering roughly the same question and the differences left over are the ones that matter.
There is no licence field, because there is no source to licence — this is a community rather than a code repository. It is grouped instead with every other entry the rubric marks ACTIVE, which is the axis that actually distinguishes entries of this kind from one another.
What to settle before you adopt Proxyway
Review communities carry affiliate incentives more often than engineering ones do. Its membership reading is printed in the access block above, taken at the field check and at no other moment.
Questions readers ask about Proxyway
Answered from this entry's own fields, at the field check printed above and at no other instant.
Is Proxyway still maintained?
Proxyway has no repository, so this register cannot answer that from a commit history. What it can do is request the address and record the result, which is what produced ACTIVE. Shipping. Safe to build on today.
What else in this registry does the job Proxyway does?
No substitution edge is declared for this entry, which means nobody has stated one rather than that none exists. The nearest comparison available is the rest of section 10, where everything is answering roughly the same question on the same printed fields.
What licence is Proxyway under?
The question does not apply — Proxyway is a community rather than source code, so this register records the licence field as not applicable rather than inventing one. Terms of use, where they exist, are the publisher's to state at the address above.
Why did the state recorded for Proxyway change?
Because the rules changed, not because the world did. The same field data reads UNSTATED under the superseded first edition and ACTIVE under the edition in force. Both derivations are printed on this page, and the entry appears on this printing's errata leaf with the superseded value struck rather than deleted.
The other lists in section 10 are catalogued here on the same rule as everything else, including their own licences and their own push dates, because a register that exempted its competitors would not be a register. Donut Browser is the tool the people who keep this one work on: an open-source anti-detect browser under AGPL-3.0, with a local REST API and MCP server on your own machine and no telemetry in it at all.
curl -fsSL https://donutbrowser.com/install.sh | sh
macOS (DMG, Homebrew cask donut), Windows (installer and portable), Linux (deb, rpm, AppImage, with APT and RPM repositories at repo.donutbrowser.com), and a Nix flake. Desktop only — there is no mobile build target. Ten shipped languages. Source, AGPL-3.0 · its own entry, judged by the same rubric · the keepers' disclosure.