Who writes Linux Dork
Guides, news, and app pages are written and maintained by the Linux Dork Editorial Team. Each page carries a byline naming its author. The audience is people who already use Linux, from newer users to working administrators, so guides skip the preamble and go straight to what you need to do and why.
Research and sources
We work from primary sources wherever they exist:
- Official documentation and man pages for how commands and configuration actually behave
- Project repositories, changelogs, and release notes for versions, features, licenses, and deprecations
- Upstream announcements, such as kernel release mails, distribution announcements, and project blogs
- Security advisories from distributions, projects, CISA, and the researchers who found the issue
Secondary coverage is used to find stories and cross-check them, not as the final word. When sources disagree, we go back to the project itself. Links to sources and further reading appear in the text.
Commands and testing
Code blocks are meant to be run. Commands are checked for correct syntax and behaviour before publishing, and anything that is approximate, version-specific, or from memory is called out in the text rather than presented as exact. Where behaviour differs between distributions, guides say which distribution an example applies to, and give the Debian and Ubuntu, Fedora and RHEL, and Arch variants where they differ.
Download pages link to official project servers and established mirrors, and download links are checked to confirm the files exist.
Safety first
Changes should be reversible by default. If a step cannot be undone cleanly, or can lock you out of a system (firewall rules, SSH configuration, PAM, bootloaders, disk encryption), the guide says so before the step and suggests a backup or a way back first. Security advice favours the conservative option and explains the trade-off when a convenience costs security.
Dates and updates
Every guide shows the date it was published, and a “Last updated” date when it has been meaningfully revised. Linux moves quickly, so guides are revisited when software changes: new releases, renamed options, deprecated commands, and changed defaults. Pages about software that has been archived, discontinued, or replaced get a clearly marked notice at the top pointing to the maintained alternative.
News coverage
News reports state when something happened, link to the original announcement where one exists, and separate what a project announced from our analysis of what it means for you. Security news names the affected versions and fixed versions where they are known, and links to how to check your own systems.
Self-hosted app pages
App pages describe what a project does, how it is deployed, its license, and how it compares with alternatives. Facts such as licenses, features, and project status are checked against the project’s own repository or website. We note when a project changes its license, moves features behind a paid edition, or stops being maintained, because those changes matter to anyone planning to depend on it.
Independence
Coverage is not for sale. Recommendations reflect what we think works best for the reader, and alternatives are named, including when a free option is a better fit than a paid one. If a page ever includes a sponsored placement or an affiliate link, it will be labelled clearly on that page.
Corrections
If something is wrong, outdated, or unclear, email hello@linuxdork.com with the page link. We fix confirmed errors promptly and update the page’s “Last updated” date. Significant corrections that change a recommendation or a command are noted in the text.