[$ xmrhost] _

$ cat /etc/xmrhost/masthead

[$ ] Team — editor masthead

// NAME

team — 2 pseudonymous editors. Lead ops handles infrastructure and hardening; editorial handles threat-models, journalism-side posture, and the legal-document drafting that precedes counsel review. Both pseudonyms are long-running brand identities; the operator's real-name + wallet + operational location remain separate from these.

// WHY PSEUDONYMS

Standard practice in the privacy-tech publication space: Tor Project contributors, EFF technologists, Freedom of the Press Foundation engineering staff all use a mix of real names and pseudonyms. The brand's editors picked pseudonyms because (1) publishing under a real name in this niche attracts adversarial attention that's irrelevant to the technical work, (2) the editorial track record is what carries authority over time regardless of whether the byline is a wallet name or a passport name, (3) operator separation of concerns is itself part of the threat model the brand documents (see /threat-models).

// EDITOR — 0XLAMBDA

[$ ] 0xLambda (ops) #

Lead operations — infrastructure, hardening, Tor / I2P / Lokinet provisioning

Operates the xmrhost.io infrastructure end-to-end: kernel hardening (KSPP baseline), sshd configuration, Tor hidden-service deployment for the tor-* tier, network procurement, abuse-mail intake. Long-running Tor relay operator in a personal capacity; contributor to the Linux kernel-hardening tooling ecosystem.

// SPECIALTIES

tor ·i2p ·lokinet ·hardening ·kernel ·ssh ·networking ·ops

// external profiles (Mastodon, Matrix, GitHub) pending operator publication.

// EDITOR — VEX

[$ ] Vex (editorial) #

Editorial — threat models, journalism / source-protection posture, legal-jurisdictional analysis

Editor for the long-form surface: threat-model dossiers, source-protection writeups, jurisdictional analysis across Iceland and Romania, the legal-document drafting that precedes counsel review. Background in security research and civil-liberties advocacy; trained as a lawyer in an EU jurisdiction, no longer practicing.

// SPECIALTIES

journalism ·threat-model ·legal ·jurisdiction ·source-protection ·monero ·policy

// external profiles (Mastodon, Matrix, GitHub) pending operator publication.

// EDITORIAL CADENCE

$ man 7 cadence

Target publication cadence:

  • 1-2 long-form notes per week — threat-model writeups, post-incident analyses, sector commentary.
  • 1 doc / runbook per week — operational guides, hardening checklists, deployment walkthroughs.
  • 1 vs/* comparison per month — binary or three-way technology comparisons.
  • 1 post-incident write-up per material incident — published within 7 days, honest engineering review.
  • 1 year-in-review per year — operational metrics, what changed, what failed.

// the cadence is a commitment, not a marketing promise. RSS feed at /notes/rss.xml; all surfaces are dated in their frontmatter for verification.

// CONTACT

$ man 7 contact-editors

Editorial correspondence (corrections, story tips, comment requests, conference invitations) routes via /contact with topic=press. The editors check the press intake on a weekly cadence; expect a reply within 5 business days. For operational questions (support, billing) use the support topic instead — different routing.

// SEE ALSO

$ ls /usr/share/doc/xmrhost/about

  • /about — brand identity, operating practice, founding rationale.
  • /about/contributions — upstream OSS contributions, CVEs, conference talks.
  • /notes — long-form editorial (bylines by these editors when applicable).
  • /docs — operator runbooks.
  • /contact — press intake + general dispatch.