Contact the Engine Room Desk
One address, read by the desk. Corrections are the most useful thing you can send, and a good correction includes the page, the claim and what you believe is correct.
Where to write
Email the desk at [email protected]. There is no form on this page, no newsletter signup and no chat widget, because none of those would make a correction arrive faster and each of them would collect more about you than the desk wants to hold.
What makes a correction useful
The desk would rather receive a short, specific correction than a long, general disagreement. Three things make a report actionable, and a report with all three usually results in a change within a working day or two.
- The page and the passage. A link plus the sentence you are disputing. Section headings all have anchors, so a link to the exact heading is ideal.
- The claim you believe is wrong. Stated as a claim rather than as a tone objection, so the desk can check the same thing you checked.
- What you believe is correct, and why. A link to public documentation, a reproducible response from a public endpoint, or a description of the behaviour you observed. Reasoning is welcome; evidence is better.
Corrections about protocol mechanics are the highest-value reports this desk receives, because they are checkable and because an error in a mechanism propagates into every design conclusion built on it.
Technical questions
Questions about the material are welcome, and the useful ones often become sections in a future note. The desk cannot review your architecture, debug your implementation, or advise on whether a particular run is a good idea, and it will say so rather than improvising.
Questions about a specific vendor's product also get a short answer, because the desk does not know how any specific product is implemented and will not speculate. What it can do is tell you which questions distinguish a serious implementation, and those are set out across the notes rather than held in reserve.
What the desk does not respond to
- Requests to add, buy or exchange links. There is no arrangement under which a link is added to this site because somebody asked for one.
- Guest post and sponsored content offers. The desk writes its own material.
- Requests for financial advice, run sizing, or an opinion on a token. Out of scope, permanently.
- Requests to review, endorse or rate a product. There are no ratings on this site and there will not be any.
Response times and expectations
The desk reads everything and replies to what it can act on. Corrections get priority. General questions may take longer, and some receive no reply at all, which is not a judgement about the question so much as an honest consequence of a small desk with a narrow remit.
If a correction results in a change, the change is made to the page and described according to the editorial policy. If you would prefer not to be acknowledged, say so and you will not be. The desk does not publish correspondence, does not add senders to any list, and does not pass on addresses; the privacy page sets out what that means in practice.