Contact

How to reach us

Email is the only contact channel for this blog: [email protected]. There is no comment system, no sign-up and no contact form, so nothing you send is stored on this site.

We read what arrives and reply when a reply is needed. We do not promise a response time, and we would rather say so than publish one we cannot keep.

Corrections

If an article is wrong, tell us and we will fix it. A correction is easiest to act on when it includes:

• The address of the page.
• The sentence, command or code you believe is wrong.
• What you observed instead, and where you observed it.

Confirmed corrections are made in the article itself and recorded there. The editorial policy explains what we do with them.

Other requests

• Reuse and quotation. Short quotations with a link need no permission. For anything longer, ask first — see the terms.
• Privacy. Questions about what this site does with data go to the same address, including questions about a message you have already sent us. The privacy policy sets out what we can state today and what is still undecided.
• Feedback and suggestions. Tell us what you were trying to do and where the article left you stuck. That is the most useful message we get.

What we cannot do

We cannot debug your production systems, review private code, or give legal, financial or security assurances about your environment. An article describes what worked in the setup it names, or what the sources it cites said when we checked them; see the disclaimer.