Editorial and operations
OffshorePress editorial team — pseudonymous
OffshorePress is a small operation. Four editors share the editorial, security, infrastructure, and operations work of the publication and the hosting service that funds it. The editors publish under pseudonymous handles. The reasoning is set out at the foot of the page; the short version is that the audience for which OffshorePress was built includes adversaries for whom doxxing the editorial team would be a step toward suppressing the work the team supports.
The four editors
-
@samizdat
Editorial direction and operator outreach
Samizdat sets the editorial line for the journal and handles the operator's correspondence with the audience for which OffshorePress was built — investigative journalists, NGO IT staff, archival projects working under legal pressure. The role exists because the publication is not adjacent to the hosting service; it is the reading layer of the same operation.
Contact /contact
-
@cleartext
Security audits and threat modelling
Cleartext runs the operator's security audits, writes the threat models the operational posture is built against, and reviews the operational changes that touch the customer-facing security boundary. The handle is the cryptographic term for the unencrypted plaintext of a message, which is the layer the role is responsible for examining and protecting.
Contact /contact
-
@meridian
Infrastructure and jurisdictional procurement
Meridian negotiates with the facilities in Reykjavik and Zurich, evaluates carrier and peering arrangements, and is responsible for the choice of which legal regime hosts which class of workload. The work is literally about choosing the meridian under which a server runs and the courts under which a subpoena is heard.
Contact /contact
-
@kassandra
Operations and support routing
Kassandra runs the day-to-day support queue, triages incident reports from subscribers, and writes the postmortems when something does go wrong. The role often consists of saying things subscribers do not want to hear about their own operational hygiene; the handle is chosen accordingly.
Contact /contact
Why pseudonymous?
The audience for which OffshorePress was built includes parties with the means and the willingness to pursue the editorial team off the page. Investigative journalism that names a litigious counterparty, archival work that preserves documents a well-resourced state would prefer destroyed, NGO infrastructure for organising work in adversarial jurisdictions — these are categories of customer whose adversaries do not stop at the legal demand. They include harassment campaigns, doxxing operations targeted at the people perceived to be supporting the work, and, in the documented cases at the upper end of the threat curve, physical surveillance and travel-document scrutiny.
An editorial team whose legal names and biographical histories were a matter of public record would carry that exposure into the lives of the editors and into the work the editors are trying to support. The pseudonymous posture separates the person from the platform; it is the same operational reasoning that the publication asks its subscribers to apply to their own work. The operator considers it incoherent to ask subscribers to publish under pseudonyms while declining to do so itself.
The pseudonyms are not anonymous to one another, are not anonymous to counsel, and are not a shield against legal process correctly served on the operating entity. They are a deliberate publication-layer choice, made so that the editorial team can do the work without the work becoming a vector to the editorial team's families, employers of record, or physical addresses.