The fastest way to reach me is email: edwinrice1977@gmail.com.
I read every message, including the ones that go directly into “follow up later” and never quite make it back out. Apologies in advance if yours is one of those. A short note about what I do and don’t reply to:
I usually answer
- Corrections. If I’ve cited a wrong version number, an outdated config, or a feature that no longer exists, please tell me. I prefer being wrong in private and right in public.
- Reader questions about a specific setup, especially if you’ve already read the article and tried the steps.
- Maintainers and developers of the software I review who want to point me at something I missed (release notes, design rationale, project context). I’d rather hear from you before publication than after.
- Notes from sysadmins and homelabbers about your own setups. Some of the best material on this site started as “have you tried…” in someone’s reply.
I rarely answer
- Guest post pitches. I write everything here myself. The voice consistency matters and there is no editorial budget.
- Sponsored content offers. The blog isn’t for sale and I don’t run paid placements.
- Generic “improve your SEO” outreach. (You’d think the niche would be a clue.)
- “Can you build my homelab for me” requests. I’m not a consultant, sorry.
Press / podcasts
I will occasionally do a podcast or a quote for an article if the topic is something I genuinely know about (self-hosting, small-team DevOps, the migration off Google services for a household). I’m not interested in being on a panel about “the future of AI” or “Kubernetes adoption in 2030”.
Security disclosures
If you’ve found a security issue with this site itself (not with the software I write about, just with phpwebthings.org), email me at the address above with “security” in the subject line. I’ll respond within seventy-two hours and won’t be a pain about disclosure timelines as long as a fix is realistically possible.
PGP
I keep meaning to publish a PGP key here. I’ll add it once I’ve rotated mine in 2026 and I’m satisfied the key management story for the people most likely to use it is workable. If that’s you, write me first and we can sort it out.