I Really Need Some Great Sysadmin and Security Researchers To...  🔗 **Source:** [I Really Need Some Great Sysadmin and Security Researchers To...](https://twitter.com/photomatt/status/2097979513959526641/?rw_tt_thread=True) > [!note]+ Document Notes > tags: [automattic, wp-engine-litigation, evidence-preservation, wordpress-governance, legal-exposure] > author: Matt Mullenweg > source: X (@photomatt) > reference: https://twitter.com/photomatt/status/2097979513959526641/ > date created: 2026-09-10 > > > [!info] Generated analysis — not the author's words. Sections below are machine-written > > from the captured source. Only text inside `> [!quote]` blocks is verbatim from the author. > > Do not quote or attribute any other line to the named author. > > # 🏷️ Title: I really need some great sysadmin and security researchers to... > <!-- deep-read:sections start --> ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) - [🔄 Refactor Appendix](#-refactor-appendix--i-really-need-some-great-sysadmin-and-security-researchers-to) ### 🔗 References - [Thread on X](https://twitter.com/photomatt/status/2097979513959526641/) — the six-post thread captured here. - Companion post the same day, on the "UNDER OATH AND PENALTY OF PERJURY" line about Quinn Emanuel — captured separately in this batch as doc `01m25hra8pxgayypjpp30yc6ff`. ## 📝 Summary - **What happened.** Matt Mullenweg (@photomatt) posted a six-part thread, publicly, the same day Automattic's board placed him on leave and installed Mark Davies as interim CEO. The thread mixes three distinct things: (1) a call to hire sysadmin/security staff and a statement that he intends to move some of his personally hosted material off Automattic infrastructure while remaining on the board and supporting Davies; (2) a digression about private equity criticism he made previously, framed as "a mistake"; (3) an unprompted account of why he set up a disappearing-message "tip line," paired with an acknowledgment that disappearing messages are unlawful under an active preservation order; and closes with (4) a dismissive one-line reply to another account. - **Why it matters.** This is a first-person, contemporaneous public statement from a named party to active litigation (WP Engine v. Automattic), posted while a preservation-order/evidence question is reportedly live in that case. What he says about his own conduct and intent here — regardless of how it's later characterized in court — is itself a document: dated, public, in his own words. - **Key stakeholders.** Automattic's board and interim CEO Mark Davies; WP Engine and its counsel; anyone assessing Automattic's or Mullenweg's public credibility during the leave. - **Risks and tradeoffs.** Reading this as an "admission" of anything would overreach — it's Mullenweg's own account of his intent (a tip line, not evidence destruction) alongside an acknowledgment of the general legal rule. Reading it as exculpatory would equally overreach — an assertion of innocent purpose isn't proof of it. Both readings go beyond what the text supports. - **Bottom line.** Treat this as primary-source evidence of what Mullenweg said, publicly, on this date, about his own infrastructure, his board relationship, and his account of the messaging-preservation issue — not as a resolved account of what happened. ## 📖 Main Content The thread runs six posts, each a reply in the same chain (the leading "@automattic"/"@LeeEWittlinger"/"@silverlake_news" text visible in the raw capture is Twitter/X's own reply-target notation, not part of the composed tweet text). **Post 1 — infrastructure and the board.** > [!quote] > I'm on the board there and fully support Mark Davies in his interim CEO role. and, in the same post: > [!quote] > I think it's probably good if I move some of my stuff currently hosted there, elsewhere. Two claims stated as fact by Mullenweg himself: he remains an Automattic board member, and he publicly backs interim CEO Mark Davies. Alongside that, in the same breath, he says he's moving some of his own material off Automattic-hosted infrastructure. The note treats all three as *his stated position*, not verified fact — this document doesn't independently confirm his board status, his relationship with Davies, or what "my stuff" refers to. **Posts 2–4 — the private-equity aside.** He references earlier public criticism of Silver Lake and Lee Wittlinger (a Silver Lake partner), and says he "won't make the same mistake" he made "last time" — clarifying, over two further posts, that the mistake wasn't the criticism of private equity itself but something he doesn't fully specify in the captured text (he links to two of his own earlier tweets rather than restating the point). This section is tangential to the legal question and is included for completeness, not analyzed further here since the referenced tweets aren't in this capture. **Post 5 — the preservation-order statement.** This is the legally load-bearing post: > [!quote] > But it's actually against the law to have disappearing messages when you have a preservation order. He offers this immediately after describing why he set up a "tip line" with disappearing messages: he says he wanted to "cosplay" as a journalist, styled on his late friend Om Malik. Two things are true simultaneously in his own text: he acknowledges the general legal rule (disappearing messages plus an active preservation order is unlawful), and he offers an account of intent (journalism-style tip line, not evidence avoidance) for why disappearing messages existed at all. The text does not state whether the specific disappearing-message configuration he describes was, in fact, covered by any preservation order in effect at the relevant time — that's the factual question a court would resolve, not something this tweet settles either way. **Post 6 — the closing reply.** Responding to a since-uncaptured post from @advany (also tagging @automattic and @wpengine): > [!quote] > I think you just imagined a new way to give my legal counsel conniptions, which I thought I had exhausted all the possibilities. Because @advany's original post isn't in this capture, its substance is unknown here — only Mullenweg's dismissive reply to it is. That's a real limit on how far this note can characterize the exchange. ## 🗒️ Notes - Posted the same day as the board's leave-of-absence decision, per this batch's other captured reporting (not re-verified independently in this note). - The thread's own internal tension is worth flagging plainly: post 1 states continued board membership and public support for the interim CEO, while — per other material in this batch not captured in this specific document — the same day reportedly included a separate, more adversarial account from Mullenweg about the board's process. This note doesn't have that second document's text in hand to quote or verify; it's flagged here as a discrepancy worth checking against the other capture, not asserted as fact. - "Sysadmin and security researchers... no one from @automattic" (post 1) is itself notable independent of the legal question: a sitting board member publicly recruiting security staff explicitly excluding people from the company he's a board member of. - Reader captured a duplicate of this thread under a second status ID (per the source note previously attached to this document); this capture is treated as the primary record. ## 📚 References - [@photomatt thread, post 1](https://twitter.com/photomatt/status/2097979513959526641/) - [@photomatt referenced tweet, x.com/photomatt/status/1836862087320195174](https://x.com/photomatt/status/1836862087320195174) — not independently fetched or verified in this note; cited because Mullenweg links it himself. - [@photomatt referenced tweet, x.com/photomatt/status/1837291862136365107](https://x.com/photomatt/status/1837291862136365107) — same caveat. - Companion post the same day on "UNDER OATH AND PENALTY OF PERJURY" (doc `01m25hra8pxgayypjpp30yc6ff` in this batch). ## 🗣️ Paraphrase Mullenweg says he's still on Automattic's board, backs Mark Davies as interim CEO, and is moving some of his own hosted material elsewhere anyway. He revisits an old private-equity criticism and calls it a mistake without saying what specifically was wrong with it. He then explains, unprompted, that a disappearing-message tip line he'd set up was meant to emulate journalistic source protection, not to evade anything — while stating plainly that disappearing messages are illegal once a preservation order is in place. He closes by brushing off another account's comment as something that will annoy his lawyers. ## 📰 Newsletter - The same day Automattic's board placed Matt Mullenweg on leave, he posted publicly — six posts, in his own voice, touching his board seat, his support for interim CEO Mark Davies, a plan to move some of his own infrastructure off Automattic, and an unprompted explanation of a disappearing-message "tip line" alongside an acknowledgment that disappearing messages are unlawful under an active preservation order. - Worth reading in full and treating carefully: it's a first-person account from a named party in active litigation (WP Engine v. Automattic), not a resolved fact pattern. File it as primary-source evidence of what was said, when, not as a verdict on what happened. ## ✅ Action Items #### DevRel - No distinct action; this is a governance/legal event, not developer-facing content. #### OSPO - **Security Management:** post 1's public call to hire "sysadmin and security researchers... no one from @automattic" is worth tracking as a signal about trust boundaries between Mullenweg's personal infrastructure and Automattic's, independent of the litigation. - **Policy & Governance:** the apparent tension between "I'm on the board" / "fully support" Davies and any more adversarial account from the same day (see Notes) is worth resolving with primary sources before citing either version as the complete picture. #### Community - **Contributors:** nothing actionable for contributors directly; relevant mainly as context for why governance conversations were especially charged this week. #### WordPress - **Core Program Team:** a board member's public infrastructure and trust statements during a leadership transition are relevant background for anyone tracking project governance stability, independent of the litigation's merits. #### The WPOCC - No distinct action from this thread specifically. ### FAIR - No distinct action from this thread specifically. ## 🧪 Hypotheses - **H1:** Mullenweg retained his Automattic board seat at the time of this post, consistent with his own statement. - **H2:** The "tip line" disappearing-message system he describes was, or was not, subject to the preservation order referenced in WP Engine's litigation against Automattic — a factual question this tweet does not resolve either way. - **H3:** The infrastructure move he describes ("move some of my stuff currently hosted there, elsewhere") is separable from any litigation-related evidence question and reflects an ordinary personal/company infrastructure separation — or it is not separable, and relates to the same preservation-order issue raised two posts later in the same thread. ### 📊 Methodology - For H1: cross-reference Automattic's board composition disclosures (public filings, press statements) as of this post's date. - For H2: this would need court filings — specifically WP Engine's sanctions motion and any Automattic response — to determine what the preservation order covered and when, not further social-media analysis. - For H3: would need a timeline correlating what "my stuff" refers to (unspecified in the text) against the preservation order's effective date and scope. ### ❓ Questions - What did Mullenweg mean by "my stuff currently hosted there" — personal files, a specific service, correspondence? - What was the "mistake" he references from his earlier private-equity criticism of Silver Lake/Lee Wittlinger, and is it explained in either of the two tweets he links but that aren't captured here? - What did @advany's original post (replied to in post 6) actually say? - Is there a documented discrepancy between this post's "fully support" language and any more adversarial statement from Mullenweg the same day, as flagged in Notes? ### 🔮 Future Research - A primary-source timeline (court filings, board disclosures) reconciling this post's board-support language against the rest of the week's reporting. - Tracking whether the "sysadmin and security researchers" hiring call led to any documented change in Mullenweg's personal infrastructure separate from Automattic's. ### 💡 Implications - **For governance:** a sitting board member's public statements about the company during a leave of absence are themselves a live governance data point — regardless of legal outcome, they show how board relationships were being managed (or not) in public, in real time. - **For litigation-adjacent documentation practice:** this is a clear example of why contemporaneous public statements by parties to litigation get preserved and cited — not as proof of any fact in dispute, but as dated evidence of what a party said, when, and in what register. - **For security/trust practice:** publicly excluding a company's own staff from a hiring call while remaining on that company's board is an unusual, notable governance signal independent of any legal question. - **For readers generally:** the instinct to read a single thread as either confession or vindication should be resisted; the responsible read is narrower than either. ### 🧠 Learning Styles Assessment - Reading level: informal, conversational register throughout (contractions, exclamation points, a joke about "conniptions"); estimated Flesch-Kincaid grade 6–8 by ear — this is a personal social-media voice, not a formal statement, despite its legal stakes. No formula was run against the text; this is an estimate from sentence structure and vocabulary. #### 👀 Visual learners - Present: none — plain text thread only. - Improve: a simple timeline graphic (board vote → this post → preservation-order reference) would help a reader place the six posts in sequence. #### 🔊 Aural learners - Present: none. - Improve: not worth a dedicated audio treatment for a social thread. #### 🗣️ Verbal learners - Present: informal, first-person narrative voice throughout; easy to follow as spoken language. - Improve: define "preservation order" explicitly for readers unfamiliar with the term — the whole legal weight of post 5 depends on understanding it. #### 🧩 Kinesthetic learners - Present: none. - Improve: not applicable to a short social thread. #### 🧠 Logical learners - Present: post 5's causal structure (tip line existed for reason X, but rule Y applies regardless of reason) is a clear if-then structure worth diagramming. - Improve: a simple two-column table — "what he says he intended" vs. "what the law requires regardless of intent" — would sharpen the logical structure for this kind of reader. #### 🧑‍🤝‍🧑 Social learners - Present: it's a public reply thread, inherently conversational and tagged to other accounts. - Improve: linking the referenced but uncaptured tweets and @advany's original post would restore the full conversational context. #### 🧘‍♀️ Solitary learners - Present: individually quotable lines suited to close reading. - Improve: none needed. #### 🌿 Naturalistic learners - Present: none — no ecological or environmental framing. - Improve: not applicable; forcing this frame would misrepresent the source. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: plain text; no markup to navigate in the captured content. - Improve: not applicable at the authoring level — a platform (X) rendering concern, not Mullenweg's. #### Keyboard navigation - Present: not applicable — static text, no interactive elements captured. #### Contrast and readability - Present: not evaluable from captured plain text. #### Text resizing and reflow - Present: not applicable — no layout to test. #### Media and captions - Present: none — no media in the captured posts. #### Forms and interactions - Present: none. #### Standards reference - Not applicable: a plain-text social thread has no WCAG-relevant authored surface beyond platform-level rendering. ### 🌍 DEIB Assessment #### Cultural breadth - Not applicable — no cultural or regional content beyond a reference to a named individual (Om Malik) as a personal touchstone. #### Inclusive language - Present: informal but not exclusionary language throughout. #### Neurodiversity support - Present: the thread's structure (six short, loosely connected posts) is fragmented; a reader following the legal thread specifically has to skip past the unrelated private-equity aside. - Improve: a single reorganized version separating "board/infrastructure," "private equity aside," and "preservation order" into clearly labeled sections would help. #### Representation - Present: references one named individual (Om Malik) respectfully, as a personal and professional influence. #### Psychological safety - Present: the tone throughout is casual and self-deprecating ("one of my many weaknesses"), not defensive or hostile toward named individuals until post 6. ### ✅ Logical Validity #### Strong reasoning - Post 5's structure is logically sound on its own terms: it separates *why the disappearing-message system existed* (stated intent) from *whether disappearing messages are permitted under a preservation order* (a rule he states applies "actually... regardless"). Keeping intent and legal permissibility as separate claims, rather than conflating "I meant no harm" with "therefore it was permitted," is the strongest piece of reasoning in the thread. #### Fallacies - **Appeal to intent as if dispositive:** the tip-line explanation functions rhetorically to make the preservation-order acknowledgment land as less consequential ("I was just trying to protect sources, but yes, technically that's not allowed"). Stated intent doesn't resolve whether a preservation obligation was met; the thread doesn't claim it does, but the sequencing (explain the sympathetic reason first, concede the rule second) is a minimization pattern worth naming. Fix: evaluate the preservation-order compliance question on its own facts, independent of the stated motive for the underlying tool. - **Deflection via humor:** post 6's "conniptions" line responds to an unknown claim with a joke rather than engagement, which forecloses assessing whether the underlying point had merit — but since the original post isn't captured, this can't be scored as a full ad hominem; it's noted as a pattern, not confirmed as one. #### Tone of voice - Casual, self-deprecating, and joke-forward through most of the thread ("one of my (many) weaknesses," "I've learned so much!"), shifting to flatly declarative for the single sentence stating the legal rule, then back to dismissive/joking in the closer. The tonal contrast around the preservation-order sentence is itself notable — it's the one moment of plain, unqualified statement in an otherwise informal thread. ### 🛡️ DARVO Analysis Some care is needed here: Mullenweg is a named party to active litigation in which WP Engine has reportedly raised an evidence-preservation/sanctions issue, which places him in an accused-party posture on that specific point — unlike most sources in this reading batch, DARVO is a legitimate lens to apply, evaluated strictly against what this text actually does. - **Deny:** partial, and not a flat denial. He does not deny that a disappearing-message system existed, or that a preservation-order rule applies. What he offers instead is a minimizing explanation of intent — the tip-line/journalism framing — presented immediately before conceding the legal rule. This is closer to *justification* than *denial*: acknowledging the fact pattern while reframing its meaning. Worth naming precisely rather than over-labeling it a "denial" it isn't. - **Attack:** present, in post 6 only. "I think you just imagined a new way to give my legal counsel conniptions" responds to an unknown critical post from @advany with dismissiveness rather than substance — a mild version of discrediting a critic by mocking the claim rather than engaging it. Because @advany's original post isn't captured here, this can't be scored as a full personal attack on credibility; it's a dismissive deflection, evidenced in the text, at moderate confidence. - **Reverse victim/offender:** weak, ambiguous signal, not a clear instance. The private-equity aside ("how they will try to destroy your life") casts Mullenweg as a target of outside forces (Silver Lake), but that's about a different, older dispute, not a reversal of the preservation-order question itself. Nothing in the text recasts WP Engine or its counsel as the true wrongdoer on the preservation-order point specifically — that reversal, if it exists elsewhere, isn't present in this document. Flagged as absent on the specific legal question, present-but-tangential on the general "I'm under threat" framing. This is a case where DARVO partially applies — an accused party's own words, evaluated on their own terms — but two of three legs are weak or absent in this specific text, and none of it should be read as evidence about the underlying legal merits. ## 🎯 Conclusion This is the most consequential primary source in the batch: a named litigant's own public account, posted the same day as a major governance event, touching his board status, an infrastructure decision, and a preservation-order acknowledgment. None of it resolves the underlying legal or governance questions — it's a data point about what was said, by whom, when, and how. The responsible next step is documentary, not interpretive: cross-reference the board-status and "fully support" claims against Automattic's own disclosures, and treat the preservation-order sentence as a dated public statement to be weighed alongside, not instead of, whatever the court record eventually shows. ## 🔄 Refactor Appendix — I really need some great sysadmin and security researchers to... > Density: 3 Literature atoms (H4), 1 Permanent candidate (H4). Resonance filter applied — the > private-equity aside (posts 2–4) was left out of the atoms below because its referenced tweets > aren't in this capture, so no atomic, verifiable claim can be built from it without speculation. ### 📚 Literature Atoms #### [H1] Mullenweg states continued board seat and public support for Davies > [!quote] > I'm on the board there and fully support Mark Davies in his interim CEO role. **Context & use**: - Post 1 of the thread, posted the same day the board placed him on leave. - Load-bearing for governance tracking: his own stated position on his board relationship and the interim CEO, to be checked against Automattic's disclosures and against any more adversarial account from the same day noted elsewhere in this batch. **Tags**: #xref **Highlight**: not applicable — no Readwise highlight ID captured with this document; quote verified directly against `html_content`. <!-- atomicity: 1 idea ✓ --> #### [H2] He states he is moving personal infrastructure off Automattic > [!quote] > I think it's probably good if I move some of my stuff currently hosted there, elsewhere. **Context & use**: - Post 1, immediately following the board/Davies statement. - Notable independent of the litigation: a sitting board member publicly separating personal infrastructure from the company's while remaining on its board. **Tags**: #xref **Highlight**: not applicable. <!-- atomicity: 1 idea ✓ --> #### [H3] He states disappearing messages under a preservation order are unlawful > [!quote] > But it's actually against the law to have disappearing messages when you have a preservation order. **Context & use**: - Post 5, immediately after his account of setting up a disappearing-message "tip line." - The legally load-bearing line in the thread: a public acknowledgment of the general rule, offered alongside — not instead of — an account of intent. Central to WP Engine's evidence-preservation allegations in the pending litigation. **Tags**: #xref **Highlight**: not applicable. <!-- atomicity: 1 idea ✓ --> ### 🧠 Permanent Candidates (H4) #### [P1] A litigant's public statements are dated evidence, not a verdict **Claim** (Courtney's voice): When a named party to active litigation posts publicly about the facts at issue, I should treat the post as dated evidence of what they said and when — never as proof of the underlying claim, in either direction. **Evidence pointer**: [[#H3]] **Scope & conditions**: Holds for any contemporaneous public statement by a party to litigation or a formal proceeding; doesn't extend to statements made after the fact with the benefit of legal counsel review, which carry different evidentiary weight. **Links** (≥1 with annotation): - [[DARVO framework]] — because applies-in: distinguishing a party's stated intent from the legal question itself is exactly the discipline DARVO analysis requires to avoid over- or under-crediting an accused party's own account. <!-- atomicity: 1 idea ✓ --> ### ✏️ Fleeting Queue - [F1] Resolve the apparent tension between this post's "fully support" language and any more adversarial account from the same day referenced elsewhere in this batch — needs the other document's actual text, not memory. — #xref - [F2] Track whether WP Engine's sanctions motion specifically addresses the "tip line" disappearing-message system described in post 5, once public filings are available. — #xref ### → Things 3 (max 2 actions) - [ ] Cross-reference Mullenweg's board-seat and "fully support Mark Davies" statement against Automattic's own public board disclosures before citing either as settled — context #verification #things <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Tweets/I Really Need Some Great Sysadmin and Security Researchers To....md|I Really Need Some Great Sysadmin and Security Researchers To... by Matt Mullenweg]] ## Highlights - [@automattic](https://twitter.com/automattic) [@LeeEWittlinger](https://twitter.com/LeeEWittlinger) [@silverlake\_news](https://twitter.com/silverlake_news) One of my (many) weaknesses is I actually want to be a journalist, so I was trying to cosplay like my late best friend [@Om](https://twitter.com/om) and set up a tip line. But it's actually against the law to have disappearing messages when you have a preservation order. ([View Highlight](https://read.readwise.io/read/01m25knr8sp0k5kvzkxzhbp7zk)) - Note: Posted the same day as the board vote, while a sanctions motion over destroyed or unpreserved evidence is pending. His own framing of why messages were configured that way, alongside an acknowledgment of the rule. Not an admission of wrongdoing and nothing adjudicated — but a contemporaneous public statement that speaks to state of mind. - Tags: atom/literature/h1, evidence-preservation, wp-engine-litigation ## New Highlights added 2026-09-10 at 10:41 AM - I'm on the board there and fully support Mark Davies in his interim CEO role. ([View Highlight](https://read.readwise.io/read/01m25w0hxeav5g69bxd4g3jpgd)) - Note: Sits in tension with the "conspired behind my back" framing he gives elsewhere the same day. - Tags: automattic, xref