正在加载…
This page documents thresholds, sample sizes and decision rules. No adjectives — only what we can prove, and what we explicitly do not know.
Every field in this library has a different provenance, and blurring them is the most common trick in this industry. We split fields into three classes by origin and label each one on the page:
The "peak-hour packet loss" figure in a card's top-right corner only shows a number when class-one data exists; if we haven't measured it, it reads "Not measured", never 0 — 0 is a measurement result, "not measured" is a different thing, and drawing them the same would count work we never did as done.
The gates only decide whether a plan is shown; they never delete one. That is the key difference from a ban: a blocked plan stays in the library and reappears as soon as the merchant fixes the issue.
Merchants don't quote in a single currency — $, ¥, € and £ can all appear in one merchant's plan table. Converting everything to one currency before sorting would make the exchange-rate decision for the user, and rates move. So we keep the merchant's original currency and only use a fixed rate table where cross-currency comparison is needed:
This table is a hand-maintained estimate, used only for buckets like "budget under $10". The price shown on a card is always the merchant's own number, never a converted one.
Cards and lists show the merchant's own price and billing cycle with no conversion at all — annual is annual, monthly is monthly, and what you see is what you pay.
"Recommended" sorts by merchant credit score first, then takes each merchant's Nth-cheapest plan in round-robin, then by price. The round-robin isn't cosmetic — sorting purely by score would fill the first page's 24 cards with a single merchant, which wouldn't be a recommendation, it would be that merchant's product page.
The index idx_plans_filter has no commission column, so the sort function cannot read one. This isn't a promise; it's isolation at the schema level.
Purchase links go through the on-site /go/ redirect; clicks are recorded in plan_clicks (no IP, no user) to count which plans actually get clicked. Right now we have not joined any affiliate programme, so the commission column in the admin shows 0, not an estimated number.
Here is what automation can and cannot do, stated once and plainly. The test is simple: can a field be read directly and reliably from a public page?
The scheduler is an in-process tick every 60 seconds, writing heartbeats to system_configs. Every timestamp on the admin "AFF & link precision" page comes from real run records, not fixed copy.
How each site type is crawled, which entry points are used and which pitfalls we've already hit is documented in 采集手册.md at the repo root — five site templates plus four import gates, covering the 12 merchants already running end to end.
85% of merchants in this industry run WHMCS, which ships an External API that could in theory expose plans, stock and orders directly. We tested 20 merchants: 16 have a live API endpoint, but all of them return 403.
403 isn't "rejecting us" — it's WHMCS's default posture: the endpoint exists but does nothing without credentials. To use it, the merchant must do three things in **their own** admin panel:
Only the merchant can do these three steps; there is no way around them. So the status quo is: we can read pages (no authorisation needed) but not the API (authorisation required). That is also why the early catalogue crawls parsed HTML instead of calling APIs — the former works for all 114 merchants, the latter would take 114 negotiations.
There is no unified affiliate network. An aff_id earned with merchant A is worthless at merchant B. So the answer to "should we register everywhere" is direct: yes, but selectively.
Right now 0 merchants are live in the library — not because the wiring is missing, but because applications haven't started. Which also means the admin's commission column showing 0 is accurate, not a placeholder.
This section matters more than the ones above, because it is the library's real boundary today:
Merchants cannot pay to disable any gate rule, nor buy a ranking slot — the moment they could, every score above would be decoration.
Open the plan radar