Write to the editors
The Iris Network is a small editorial operation, and we keep contact simple: one email address, read by the people who decide what is published. Whether you spotted an error, want to suggest a subject, or have a question about an article, write to [email protected]. There is no contact form on this site, and we do not publish a phone number or a postal address.
Sending feedback on an article
General feedback is welcome, including disagreement. To make it useful, please include the title or link of the article, the part you are responding to, and your reasoning. Technical objections land best when they come with a source: a standard, a section of documentation, a configuration snippet or a test you ran. We read everything that arrives, though we cannot promise a long personal reply to every message.
Requesting a correction
If you think a statement is inaccurate, outdated or misleading, tell us. A good correction request contains:
- the article link and the exact sentence or figure in question;
- what you believe is correct;
- evidence, such as documentation, a changelog entry or the output of a test;
- the software versions or environment, if the issue depends on them.
When a correction is justified, we fix the article and add a dated note describing the change. See our About page for the full editorial approach.
Proposing a topic
We cover Infrastructure, Testing, Cybersecurity and Trends. If you have a subject in mind, send a few lines on the engineering problem, why readers should care now, and the primary sources you would start from. Please do not send promotional material or press releases; we do not publish sponsored content, and product pitches without a technical question behind them will not be taken further.
Reporting a security issue
If you have found a vulnerability related to something we have written about, the best path is to report it to the vendor or project maintainers first, following their disclosure process. You can also tell us at the address above, and we will not publish exploit details for an unpatched flaw before the maintainers have had a reasonable chance to respond. If you believe the site itself has a security problem, write to us with a short description and the steps to reproduce it, and please avoid accessing data that is not yours.
When to expect a reply
We reply as soon as we reasonably can, but we do not promise a fixed response time. Messages about factual errors and security problems are read first. Suggestions and general comments may take longer. If you have not heard back after a while, a short follow-up is fine.
Quick answers
Is there another way to reach you besides email?
No. Email at [email protected] is the only channel we use for the site.
Can you help with my network design or troubleshooting problem?
We are a publication, not a consultancy, so we cannot give individual design or support advice. The articles in The Library may point you to useful starting material.
Do you publish guest articles?
Occasionally, if the idea is strong and backed by primary sources or original testing. Start with a short outline by email rather than a finished draft.
Will you share my message or email address?
No. We use what you send only to respond and to improve the article in question. If we want to quote you, we ask first.