029danio/fly: a README that recommends paid proxy services rather than shipping code

What 029danio/fly actually contains

The repository has two top-level entries: README.md and index.html. The primary language is listed as HTML, and the README is a long Chinese sales page. It does not ship a proxy client, a server, a configuration generator or a library. The first line of the README calls the page a recommendation list for "翻墙机场" (proxy subscription services) and claims it is updated through September 2026. Everything below that line is a sequence of provider blurbs with prices, traffic quotas, device limits and referral links.

The audience is people in mainland China shopping for a paid proxy subscription, usually to reach services that are blocked locally. The page is written for that reader, not for a developer evaluating a dependency. If you arrived expecting to clone something and run it, there is nothing here to run. The only executable artefact mentioned is a link to a separate repository, 029danio/clash, described as a download page for Clash clients on Windows, Android and macOS.

That distinction matters for how you read the rest of the page. Every performance claim, price and benefit statement comes from the sellers being promoted. The repository itself performs no measurement and publishes no methodology.

How the recommendation page is structured

The README is organised as a stack of provider entries. The first is labelled 超实惠机场 and lists monthly plans at 15, 21 and 27 yuan with 400G, 600G and 900G of monthly traffic, yearly plans at 63 and 207 yuan, and two non-expiring plans at 51 yuan for 666G and 90 yuan for 1200G. It also claims an Emby membership is bundled with a purchase. The second entry is 狗狗加速VPN, which the README says gives three free days on registration and lists three tiers at 15.80, 20.80 and 39.80 yuan per month, the top one advertising Hysteria2. The third is 飞鸟云机场, presented as a table of monthly and non-expiring plans running from 10 yuan for 200G up to 300 yuan for 10000G.

Each entry ends in an outbound link, mostly shortened through cutt.ly or a provider's own registration URL. The page also carries a general advice section titled 选机场节点前必看, which argues for transit-based providers over public-network routing, suggests buying two to four backup subscriptions, and warns against free VPN or SS/SSR node sharing. That section is the closest thing to editorial content, and it is still written to move the reader toward a purchase.

There is no data file, no JSON manifest of providers and no build step. Updating the page means editing Markdown by hand. The index.html at the repository root is the rendered form of the same content.

Reading the page locally

There is no install step, because there is no software. The README does not document a package, a binary or a deployment, and it gives no clone command of its own. The repository layout is the only thing a reader can act on: the project page lists README.md and index.html at the top level, and the README points to a separate repository for client downloads.

git clone https://github.com/029danio/fly.git

After cloning, the working directory holds README.md and index.html. There is no dependency to install and no build command to run. Opening index.html in a browser shows the same promotional content as the README, rendered.

The only actionable links on the page are the outbound provider URLs and the pointer to the clash client repository at https://github.com/029danio/clash. The README does not document how to verify a subscription once purchased, and it does not describe any client configuration format.

Where the page stops being useful

The most obvious limitation is that none of the claims are checkable from the repository. The README states that one provider reaches "YouTube测速高达40W+" and that another offers "极低延迟" on a dedicated line. There is no test date, no server location, no client version and no measurement file. A reader cannot reproduce any of it, and the page does not claim they can.

Two structural problems follow. First, the page mixes a general guide with paid placements and does not label which entries are paid. The advice section tells you to avoid free nodes and buy several backups, which is reasonable-sounding guidance that also happens to increase the number of purchases made through the page's links. Second, the pricing tables are the kind of data that goes stale fastest. The README asserts an update through September 2026, but a price change at any provider makes the corresponding table wrong with no signal on the page.

The repository is also the wrong tool for anyone who wants to run their own proxy. There is no server setup, no protocol implementation and no configuration generator here. If your goal is to operate a node rather than buy access to one, this page offers nothing except the names of protocols the providers claim to use. The last push to the repository was on 2026-09-01.

How this differs from a proxy client project

The natural comparison is with the client software the page itself points to. The linked repository, 029danio/clash, is presented as a download page for Clash clients across Windows, Android and macOS. A client project ships binaries or build instructions, a configuration schema, and a rules engine that decides which traffic goes through which proxy. It is software you install and configure.

029danio/fly is the opposite layer. It is a directory of sellers. The client decides how traffic is routed; this page decides which subscription you might buy to feed that client. One is a program, the other is a list of vendors with prices. Confusing the two leads to a predictable disappointment: cloning this repository gives you a Markdown file, not a working proxy.

A second contrast is with self-hosted proxy stacks, where you rent a server, install a protocol implementation and manage the endpoint yourself. That approach gives you control over the endpoint and no dependency on a reseller, at the cost of running and paying for the server. The README does not discuss that option at all; its advice section assumes you are buying from a provider.

Maintenance, licensing and what the repository does not say

The repository is not archived, and its last push was on 2026-09-01, which is within the last month. That tells you the page was edited recently. It does not tell you that any listed provider is still operating, that any price is current, or that any link still resolves. Those are separate facts the repository does not track.

No licence is listed for the repository. With no licence file and no licence statement in the README, the default position is that the author reserves rights, and there is no grant to reuse the text or the page. If you want to republish the provider tables, the repository gives you no permission to do so. This is a description of what the repository states, not legal advice; if reuse matters to you, ask the contact address in the README.

On upgrades: there is nothing to upgrade. The page has no version, no changelog and no release. Keeping it accurate would mean manually re-checking every provider's pricing and availability, and the repository provides no mechanism, script or checklist for that. The README's contribution section invites issues, pull requests and email, and gives [email protected] as the contact, so corrections are handled through the author rather than through any automated process.

Editorial conclusion

Use 029danio/fly only as a starting point for reading provider names, prices and traffic tiers, and treat every claim on the page as advertising written by the seller. Do not treat it as software: there is no installer, no configuration file and no licence statement, so nothing about it can be verified by running it. Before paying any provider listed here, check whether the subscription works with the client you already use, and read the provider's own terms for refunds and data handling.

Frequently asked questions

Official sources

1. 029danio/fly on GitHub
2. Issues
3. Project website
4. README