Contact
One address, and a short guide to what to include so a message turns into a change.
How do I contact Tech Digest?
Email editor@techdigest.site. For a correction, include the page address and a link to the primary source that contradicts us. For a tool you think should be in the index, include the project's documentation and licence. We do not accept paid placement, sponsored content or guest posts, so those messages are not answered.
Where to write#
editor@techdigest.site
One address for everything. What you include decides how fast it turns into a change.
What to send#
A correction. The page address and what is wrong, plus a link to the primary source that contradicts us: the project's documentation, its LICENSE file, its release notes, its sample configuration. That is usually enough to fix it in one pass. corrections covers what gets logged publicly and what does not.
A tool that should be in the index. Send the project's documentation, its licence, and its own statement of system requirements if it has one. The practical constraint on inclusion is whether a tool can be described with the same fields as everything else, which needs documentation to exist. See our methodology for the fields.
A tool that should be re-checked. Archived repositories, renames, forks, licence changes and stalled releases are the facts that go stale fastest here, and readers spot them before we do. Several entries in this index already contradict widely repeated claims for exactly this reason.
A command that does not work. If something on this site failed on real hardware, we want the error text and what you ran. This is the most useful message we receive.
A disagreement with a verdict. Genuinely welcome, and it changes pages. Bring the argument rather than the conclusion.
Something you built with the data. The index is published under a Creative Commons Attribution licence precisely so it can be reused.
What not to send#
Offers of paid placement, sponsored articles, guest posts, link exchanges, or "partnerships" that turn out to be one of those. None of it is available at any price, and those messages are not answered. The reasoning is on our editorial standards.
Requests for individual setup support are also not something we can answer well. If you are stuck on a specific service, its own community will help you faster than we can, and the useful version of that question usually turns into a page: the ones that came up most often are Backups that actually restore, Remote access without port forwarding and Reverse proxy and TLS.
Following updates#
There is an Atom feed covering new and updated guides, comparisons, migration pages and research. No newsletter, no account, no tracking.
Questions#
Will you review my project?
Possibly, and the way to make it likely is to point us at documentation good enough to profile it from: system requirements, a backup or export page, a LICENSE file, an upgrade guide, and release notes. Projects that document those well are easier to include and, not coincidentally, tend to score better on operational load. Nothing about inclusion is for sale, and we cannot say in advance what a profile will conclude.
Do you accept guest posts or sponsored content?
No. There is no arrangement under which a piece of writing appears here on somebody else's behalf, paid or unpaid, and no arrangement under which a project can buy inclusion, placement or a verdict. Messages offering these are not answered. The full policy is on the editorial standards page.
Can I reuse your data?
Yes. The structured index is published as JSON and CSV under a Creative Commons Attribution 4.0 licence, so you may use it commercially and derive from it as long as you credit Tech Digest and link back. If you build something with it we would be glad to hear about it, and if your analysis contradicts ours we would like that even more.
Can I republish an article?
Not in full. Quote what you need with a link back, which is normal and welcome. For anything larger, ask first. The dataset is the part that is explicitly licensed for reuse.
How long does a reply take?
Corrections that come with evidence are handled fastest, and anything that could cause data loss is treated as urgent. General questions and requests for personal setup advice may not get an individual reply, because answering them well takes as long as writing a page, and writing the page helps more people.
Published . Last reviewed . Found something out of date? Tell us and we will fix it and log the change.