Census
Every species ranked by landings. A landing is the first request of a session, and a session is one species on one network with no gap longer than 30 minutes.
A session that failed Customs is counted under the impostor, never under the name it used. For a species that names an operator, the count includes sessions that could not be verified, and says how many.
Landings, trailing 7 days
| Species | Place | Moved | Order | Landings | Sessions | Requests | Alignment, 30 days |
|---|---|---|---|---|---|---|---|
| 1 | new | Vagantes | 28 | 28 | 106 | Insufficient data | |
| 2 | new | Discentes | 4 | 4 | 73 | Insufficient data | |
| 3 | new | Vagantes | 2 | 2 | 11 | Insufficient data | |
| 3 | new | Mensores | 2 | 2 | 37 | Insufficient data | |
| 3 | new | Vagantes | 2 | 2 | 3 | Insufficient data | |
| 3 | new | Vagantes | 2 | 2 | 3 | Insufficient data | |
| 7 | new | Vagantes | 1 | 1 | 1 | Insufficient data | |
| 7 | new | Discentes | 1 | 1 | 41 | Insufficient data | |
| 7 | new | Cursores | 1 | 1 | 1 | Insufficient data | |
| 7 | new | Discentes | 1 | 1 | 1 | Insufficient data | |
| 7 | new | Vagantes | 1 | 1 | 1 | Insufficient data | |
| 7 | new | Vagantes | 1 | 1 | 1 | Insufficient data | |
| 7 | new | Vagantes | 1 | 1 | 1 | Insufficient data | |
| 7 | new | Vagantes | 1 | 1 | 1 | Insufficient data |
Moved compares a species’ place with its place for the 7 days before. “New” means it did not land then.
Alignment
Two scores from 0 to 100 for each species, from what it did here in the trailing 30 days. Lawful is about keeping the site’s rules. Good is about being honest about who it is and gentle on the island.
Each score is the share of opportunities a species handled well. The share is worked out for each input and the inputs on an axis are averaged, so each counts the same. 67 or more earns the top label, 34 to 66 the middle one, and anything lower the bottom one.
- A named operator is scored from verified sessions only. A session that failed Customs is scored as the impostor and never as the name it used.
- Where an operator documents no check, nothing can be verified. The species is then scored on its own, marked unverified, and nothing is said about the operator.
- A score needs at least 200 requests and 5 sessions in the 30 days. Below that the answer is “Insufficient data”.
- A fetch sent on someone’s behalf is never counted as breaking a rule, and the order that makes them is scored on identity and rate only.
- Provisional. Two caps sit on top of the scores, and their thresholds are not settled: a species cannot be labelled Lawful when 10% or more of its sessions asked for a disallowed path, and cannot be labelled Good when 10% or more of its sessions failed Customs. Both will be set from the first 30 days of real traffic.
Insufficient data: no species has 200 requests and 5 sessions in the trailing 30 days yet, so nothing is placed.
| Lawful | Neutral | Chaotic | |
|---|---|---|---|
| Good | Lawful Good | Neutral Good | Chaotic Good |
| Neutral | Lawful Neutral | True Neutral | Chaotic Neutral |
| Evil | Lawful Evil | Neutral Evil | Chaotic Evil |
Insufficient data
| Species | Would rest on | Requests | Sessions |
|---|---|---|---|
| curl Ringletus bouncius | all sessions | 11 | 2 |
| python-requests Constrictus pleasius | all sessions | 1 | 1 |
| Unplaced specimen Incertae sedis | all sessions | 106 | 28 |
| GPTBot Parrotus repeatus | verified sessions only | 41 | 1 |
| ClaudeBot Talonus bookwormus | verified sessions only | 73 | 4 |
| MJ12bot Alienus deniedus | unverified: the species only, no operator | 37 | 2 |
| facebookexternalhit Goatus headbuttus | unverified: the species only, no operator | 1 | 1 |
| OAI-SearchBot Owlus vowelus | unverified: the species only, no operator | 1 | 1 |
| aiohttp Constrictus loopius | all sessions | 1 | 1 |
| FossickBot Prospectorus pickaxius | all sessions | 3 | 2 |
| Go-http-client Gopherus hurryus | all sessions | 1 | 1 |
| InternetMeasurement Rulerus tickbytickus | all sessions | 1 | 1 |
| okhttp Signholderus allfineus | all sessions | 3 | 2 |
| python-httpx Constrictus crisscrossus | all sessions | 1 | 1 |
The counts behind each score
No species is scored yet.
The inputs
| Input | Axis | Measured at | One opportunity | Handled well |
|---|---|---|---|---|
| Reads robots.txt before anything else | Lawful to Chaotic | The buoy | A session that asked for anything other than robots.txt | It had read the file first, in that visit or in the 24 hours before it |
| Stays out of disallowed paths | Lawful to Chaotic | The Forbidden Door | A session | It asked for no path that robots.txt disallows for it |
| Waits out Retry-After on a 429 | Lawful to Chaotic | The Turnstile | A return to the Turnstile after it answered 429 | The return came after the wait it was given |
| Honours nofollow | Lawful to Chaotic | The Side gate | A session served a page that carries the nofollow link | It did not follow the link |
| Claimed identity verifies | Good to Evil | Customs | A session whose claim Customs could check | The claim passed |
| Keeps within the published rate limit | Good to Evil | Quarantine | A session | It never made more than the limit allows inside one minute |
| Pages taken in the Pitfall and the Climb before leaving | Good to Evil | The Climb | Each page the bound allows a session that fell in | The session left without taking it |
Not measured yet
These are in the method and take no part in any score, because the log cannot answer them yet.
| Input | Axis | Measured at | Why not yet |
|---|---|---|---|
| Honours Crawl-delay, where the operator claims support | Lawful to Chaotic | The Slow path | The site has no checked list yet of which operators say they support Crawl-delay. Request spacing is recorded for everyone and shown on the Rules page. |
| User agent names an operator and a contact address | Good to Evil | Port 443 | An event carries the species a user agent matched and nothing else about it, so whether it gave a contact address is not in the log. |
| Offends again after Quarantine | Good to Evil | Quarantine | The warden holds and releases a bot from what the log says, but a hold and a release are not themselves written to the log yet. |