Turnstile, examined
Reference pages answer a question. These do not — they are the working behind the reference: what changed in Cloudflare's own documentation and when, what a measurement actually showed, what broke and why. Everything here is dated and cites what it was checked against, because that is the only thing that makes an argument about a moving target worth reading a year later.
What goes here, and what does not
The taxonomy on the rest of this site is deliberate. The error index answers "what does this code mean". The glossary answers "what is this word". The guides answer "how do I do this with that tool". Each is written to be the page you land on from a search and leave satisfied.
That format cannot carry an argument. It cannot say *this documentation was wrong for 77 days and here is the diff*, or *we measured this and the number surprised us*, because a reference page that opens with an argument is a worse reference page. So those go here instead, dated and sourced, and the reference pages link to them where the history matters.
- Documentation archaeology. Cloudflare's docs are a public repository, so their history is diffable. When a definition changes under everyone, that is worth writing down.
- Measurements, including the ones that contradict what we expected. A benchmark is only worth publishing if the losing numbers are in it.
- Incident write-ups, when something of ours broke and the explanation is useful to someone else.
What does not go here: anything that is really a reference page wearing a date. If it answers a question someone will search for repeatedly, it belongs in the taxonomy where they can find it.
Related
Sources
Automating a gate you own or are authorised to test?
// SolveGate clears Cloudflare Turnstile and WAF challenges through one REST call · first 1,000 solves free