Rumors Say Toni Schneider Resigned From the Automattic Board  🔗 **Source:** [Rumors Say Toni Schneider Resigned From the Automattic Board](https://goblin.band/notes/ar12505pd1473qcr#recovered) > [!note]+ Document Notes > tags: [automattic, automattic-board, wordpress-governance, bluesky] > author: "@javi (goblin.band)" > source: goblin.band > reference: https://goblin.band/notes/ar12505pd1473qcr > date created: 2026-10-02 11:02 > > > [!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: Rumors say Toni Schneider resigned from the Automattic board > <!-- 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--rumors-say-toni-schneider-resigned-from-the-automattic-board) This is a social post that relays a rumor. It is unverified. Paragraph labels like ¶3 are the pipeline's extraction labels, not part of the post. The post names real people, so this note says who asserts what and states nothing from the post as fact. ## 📝 Summary - **What happened.** On 2026-09-11 at 21:53 UTC (¶7), @javi posted a short note on the goblin.band instance. The note passes along a rumor that Toni Schneider has resigned from Automattic's board of directors (¶1). Reader's saved copy is dated 2026-09-12. Reader's original scrape returned only a JavaScript-required message, so the text was recovered from the instance's public note endpoint (¶7). - **The claim.** @javi relays the rumor with hedged wording: rumors say, and he seems to have resigned (¶1). The post describes Schneider as the CEO of Bluesky and as the person who was CEO of Automattic for roughly its first decade (¶1). It then characterizes him as the good CEO of the company, says he was interim CEO during an episode in early 2025, and says he approved a letter from Tumblr's trans staff (¶2). It closes by calling his departure bad news for the company and its employees (¶3). A quoted earlier note from the same account (¶4 to ¶6) speculates about what Automattic's board learned before it acted. - **Why it matters.** If true, a long-tenured former CEO would have left the board of a company that runs WordPress.com and sits at the center of WordPress governance debates. The post doesn't show it is true. It matters mostly as a signal of what one author, on one instance, was saying within hours of 2026-09-11. - **Key stakeholders.** @javi (author); Toni Schneider (the subject of the rumor); Matt, named by first name only in the post (¶1, ¶2, ¶5); Automattic's board and employees (¶3, ¶5); Tumblr's trans staff (¶2); Bluesky, named as Schneider's current employer (¶1). The post doesn't give Matt's surname. Reading him as Matt Mullenweg is an inference from context, and it matches the earlier light-touch note on this source. - **Risks and tradeoffs.** The post names no source for the rumor and links nothing. It makes serious allegations about a named person's conduct (¶2) that this note doesn't repeat as fact. It uses mocking nicknames (¶5), which marks it as partisan commentary. Acting on it, for example by citing it in a news item or a governance thread, risks spreading a false resignation claim about a real person. - **Bottom line.** Treat the resignation as an unverified rumor, as the author frames it. The one checkable claim is whether Schneider has left Automattic's board. Confirm that through Automattic or named reporting before anyone repeats it. ## 📖 Main content **What kind of source this is.** A social post of seven captured paragraphs: three by @javi (¶1 to ¶3), a label line (¶4), two paragraphs quoted from an earlier note by the same account (¶5, ¶6), and a one-line recovery note added by the pipeline (¶7). It is opinion and rumor, not reporting. No byline beyond the handle, no outlet, no editor. The author takes a side in the dispute the post describes. **What the post attributes, and to whom.** - **The rumor (¶1).** The post attributes the resignation to unnamed rumors, with no person behind them. It then hedges again by saying he seems to have resigned. So the claim is a rumor, relayed with a second layer of doubt. - **Schneider's background (¶1).** The post says he is CEO of Bluesky and was CEO of Automattic for about its first decade, and that he effectively built the company for Matt. These are @javi's statements. This analysis hasn't checked them, and the capture contains no link for any of them. - **The characterization of Schneider (¶2).** The post calls him the good CEO of Automattic and the adult in the room for two decades. That is @javi's evaluation, written as praise. - **The early 2025 episode (¶2).** The post says that in early 2025 Matt had an episode involving other people online, that Matt was kept out of view for a period, and that Schneider was interim CEO during it. The post's description of Matt's conduct is a serious allegation by @javi. It comes with no link and no document in the capture, so this note doesn't restate its details as fact. - **The Tumblr letter (¶2).** The post says Schneider gave a thumbs up for Tumblr's trans staff to publish a letter condemning Matt's actions, and promised them no reprisals. This is also @javi's account, unlinked. - **The effect (¶3).** The post says his leaving is bad news for the company and its employees. This is a judgment, not a fact. - **The quoted earlier note (¶5, ¶6).** @javi's earlier note, as quoted, says Matt is back at the helm, and says the next thing is to learn what Automattic's board found out that made it react in panic and try to remove him without securing support. It then predicts the answer won't take long (¶6). The earlier note is speculation by its own wording: the author says they suspect the answer will come soon. **What the post does not establish.** - **That the resignation happened.** The post doesn't say how it heard, who told it, or when. - **That Schneider sits, or sat, on the board.** The post assumes it. No link or document in the capture confirms board membership. - **That Schneider was interim CEO in early 2025.** Stated in ¶2, unlinked. - **What the board did or found.** ¶5 describes a board action and a reaction in terms the post chooses. No board statement is cited. - **The date of the underlying events.** Only the note's creation time is known (2026-09-11 21:53 UTC, ¶7). **Terms.** - **Board of directors.** The body that oversees a company's CEO. Resigning from it means leaving that oversight role, not the company's staff. - **Interim CEO.** A temporary chief executive while the permanent one is absent or removed. - **Doxx.** Publishing someone's private details. The post uses the word in its allegation (¶2). This note names it only to define it. - **Instance (fediverse).** A server in a federated social network. The endpoint in ¶7 is a note-show API, which suggests a Misskey-family server. That is an inference from the path name, not stated in the capture. **Uncertain or contested in this source.** Everything above rests on one author's say-so. Nothing in the capture contradicts it, and nothing supports it independently. The earlier light-touch note on this source also reported a TechCrunch story from September 11 that covered a board vote, a paid leave for Mullenweg, and an interim CEO, and said that story didn't mention Schneider. Nothing in this source's text carries that. This analysis couldn't re-check it offline, so treat it as unverified here. ## 🗒️ Notes #### 📄 ¶1 The rumor - The post opens with the claim: rumors say Schneider seems to have resigned from the board (¶1). - It adds three descriptors in one sentence: CEO of Bluesky, CEO of Automattic for the first decade or so, and builder of the company for Matt. - The hedging is in the opening words, which read as hearsay before any claim appears. #### 📄 ¶2 Characterizing Schneider and the 2025 episode - The post calls him the good CEO and the adult in the room for two decades. - It describes an interim-CEO period in early 2025 and attributes the Tumblr letter approval to him. - It also contains the serious allegation about Matt's conduct. The post's wording about the episode is mocking, which signals opinion, not neutral report. - Two time spans appear: the first decade as CEO (¶1) and two decades as a steadying presence (¶2). They aren't the same claim and don't contradict. #### 📄 ¶3 The verdict - One sentence: his leaving is awful news for the company and its employees. - The sentence has a subject-verb agreement slip, which suggests quick, unedited posting. #### 📄 ¶4 to ¶6 The quoted earlier note - ¶4 is a label saying the next two paragraphs quote an earlier note by @javi. - ¶5 says Matt is back in charge, using a mocking nickname for him, and that the next question is what the board learned that made it act in panic. - ¶5 also says the board tried to remove him without securing support for the decision. This is @javi's account. - ¶6 predicts the answer will come soon, because of how urgently the board acted. The author's word for it marks it as a guess. #### 📄 ¶7 Recovery note - The pipeline adds the recovery line: the text came from the instance's note endpoint, noteId ar12505pd1473qcr, created 2026-09-11T21:53:42Z. - It states that Reader's original scrape returned only a JavaScript-required message. ¶7 is not @javi's text. ## 📚 References The captured link list is empty. No link in the captured markup points to any source for any claim in the post. - [The post as saved](https://goblin.band/notes/ar12505pd1473qcr): @javi on goblin.band, the document analyzed here. The recovery text (¶7) names the instance's public note endpoint, `https://goblin.band/api/notes/show`, with noteId ar12505pd1473qcr. - Claims with no link in the captured markup: the resignation (¶1), Schneider's board membership, his Bluesky role, his Automattic CEO tenure (¶1), the interim-CEO period (¶2), the Tumblr letter (¶2), the board's action and reasons (¶5), and Matt's return (¶5). - Primary sources to check next, none of them in the capture: an Automattic statement or SEC-style filing if one exists, Bluesky's leadership page for Schneider's current role, Automattic's own board listing, and named news coverage of the events around 2026-09-11. This note names them as places to look, and hasn't checked any of them. - The earlier light-touch note listed a TechCrunch story dated September 11 as context. No link for it appears in this source, and it couldn't be re-checked offline. ## 🗣️ Paraphrase @javi passes along a rumor that Toni Schneider has left Automattic's board. The post says he now runs Bluesky and once ran Automattic for about its first ten years. It calls him the steady, trustworthy one at the company and says his leaving is bad for Automattic and its employees. The post also makes claims about early 2025: that Schneider stood in as CEO while Matt was kept out of view after an online episode, and that he backed Tumblr's trans staff when they published a letter against Matt's actions. Those claims are @javi's, and the post gives no sources for them. The quoted earlier note, from the same account, says Matt is back in charge and wonders what the board learned that made it act so fast and so unsteadily. It guesses the answer will come soon. ## 📰 Newsletter **A rumor about the Automattic board, and why it stays a rumor.** On September 11, a post on goblin.band by @javi said rumors have Toni Schneider resigning from Automattic's board. The post names no source and links nothing. It frames the claim as hearsay, then adds opinion about Schneider, a 2025 episode, and Matt. For the WordPress community, the useful move is to hold the claim loosely. Board seats are checkable facts. Ask Automattic, or wait for named reporting, before you repeat it in a forum, a Slack channel or a newsletter of your own. If you cite the post, cite it as one author's rumor, with the link to the post itself: [the note on goblin.band](https://goblin.band/notes/ar12505pd1473qcr). ## ✅ Action items Each line ties to what the post says or states plainly that no action follows. The post is a rumor, so the actions are about handling it. #### DevRel - Developer advocacy: no direct action. If asked about this at a talk, say it is an unverified rumor and point to no outcome. - Education: a short module on source assessment: rumor, relayed rumor, named report. The post is a clean example of a relayed rumor with a hedge (¶1). - Developer experience: none. The post isn't about tooling. - Developer marketing: none. Don't use the post in campaigns or comparisons. - Community management: if the post surfaces in a community channel, ask for a primary source before discussion. Keep allegations about named people (¶2) out of the thread unless someone links documentation. - Internal/external/cross-project: none from this source. #### OSPO - Policy and governance: the post is a reminder that board membership of a company central to an open-source project is public-interest information. An OSPO can write down where its own board changes get announced. - License compliance: none. No license question appears. - Security management: none. - Software inventory: none. - Developer support: none from this source. - Community engagement: none directly. - Strategic alignment: none. The post makes no claim about open-source strategy. #### Community - Maintainers: no direct action. Nearest relevance: maintainers who get asked about leadership changes at a sponsoring company can say they have no confirmed information. - Contributors: none. - Sponsors: none. The post doesn't discuss sponsorship. - Ecosystem: none from this source. #### WordPress - Core: no direct action. - Core Performance: none. - Core AI: none. - **Core Program Team:** none. - Mobile: none. - Playground: none. - Community: no direct action. Nearest relevance: community leaders may see the post shared. A one-line response saying it is an unverified rumor with no source is accurate. - Training: none. - Marketing: none. Don't amplify the claim. - Support: none. - Design: none. - Documentation: none. - Photos: none. - TV: none. - Polyglots: none. - Accessibility: none from this source. - Meta: none. The post doesn't touch the .org directory. - CLI: none. - Hosting: none. The post doesn't mention hosting. - Tide: none. - Openverse: none. - Themes: none. - Plugins: none. #### The WPOCC - Programs: none directly. - Projects: none. - Funding experiments: none from this source. ### FAIR - Technical independence: none. The post says nothing about package signing or provenance. - Policies and covenants: none directly. The post shows how one company's board changes become community-wide news. A governance covenant could name where such changes are announced. That is an idea, not something the post says. - Productized governance artifacts: none from this source. ## 🧪 Hypotheses 1. Hedged relays of board changes (opening with rumors say, then seem to have) are repeated by other accounts without their hedges within a few days of the original post. 2. A board-membership rumor with no named source is confirmed or denied by the company or by named reporting within two weeks in a minority of cases. 3. Posts that pair a rumor with praise or blame for a named person (¶2, ¶3) get more reshares than the same rumor stated neutrally. 4. The recovery of JavaScript-gated posts through an instance's public endpoint (¶7) yields the same text a reader would see in the browser, so the recovered copy is a faithful record. 5. Readers who see this post without the label "rumor" in the first sentence report higher belief that the resignation happened. 6. The quoted earlier note's prediction (¶6) that the board's findings would surface soon holds or fails on a date that can be checked in public reporting. ## 📊 Methodology - **H1.** Collect posts that quote this one and compare the hedging words. Count the share that drop the rumors-say opener. Use two coders and a written rule for what counts as a hedge. - **H2.** Log the rumor claim and watch company statements, filings and named reporting for 14 days. Record confirm, deny or silence. This note can't supply a base rate. - **H3.** Show matched readers two versions of the same rumor, one neutral and one with praise or blame for a named person. Measure sharing intent. Pre-register the comparison. - **H4.** Fetch the same note through the browser and the public endpoint on the instance, then diff the text. Done here only in part: the endpoint copy is the only one this note saw. - **H5.** Survey readers after they see the post with and without a first-line "rumor" label. Measure belief that the resignation happened. - **H6.** Record the date the board's reasons become public (if they do) and compare to ¶6. The prediction fails if nothing appears within an agreed window. - **Controls throughout.** Don't republish the post's allegations about named people. Use a paraphrase such as a rumor of a resignation in all test materials. ## ❓ Questions - Who told @javi about the resignation, and when? - Does Schneider currently hold an Automattic board seat, and has any public statement said he left? - What did Automattic's board do before 2026-09-11 that the quoted note (¶5) describes as a reaction in panic? - What public record supports the interim-CEO period the post places in early 2025 (¶2)? - Is there a public copy of the Tumblr staff letter (¶2), and who signed it? - Did other accounts relay the rumor, and with which wording changes? - Does the quoted earlier note (¶5, ¶6) refer to the same board action the earlier light-touch note's context described, or a different one? - Did the author later correct or update the post? ## 🔮 Future research - **Track confirmation.** Follow Automattic and Bluesky official channels for any statement about board composition after 2026-09-11. - **Rumor propagation.** Map how a hedged claim moves across fediverse instances and Bluesky within 72 hours. - **Governance transparency.** Compare how public companies and private companies tied to open-source projects disclose board changes. - **Source recovery.** Test how often scraped social posts come back as JavaScript-required pages (¶7) and what recovery routes exist for them. - **The 2025 claims.** Gather documentary sources, if any are public, for the interim-CEO and Tumblr letter statements, and compare with ¶2. ## 💡 Implications - **Practice.** Anyone who writes about WordPress leadership should separate rumor from confirmed fact, and name the author of each claim. This post gives one claim with one stated hedge and no source. - **Policy.** Board changes at a company central to an open-source project affect the project's perceived stability. Governance policies can say where such changes are announced, so rumors have a primary source to check. - **Security.** Recovering text from a gated page through a public endpoint (¶7) is a legitimate read. Treat the recovered copy as a record of what the endpoint returned, not as proof of the claims in it. - **Education.** The post is a compact teaching example of a relayed rumor, a hedge, an unlinked allegation and an opinion in one short note. - **Funding.** The post says nothing about funding. Any effect of a board change on sponsorship or contribution levels is not in the source. ## 🧠 Learning styles assessment - **Reading level estimate.** Flesch-Kincaid Grade Level of @javi's own paragraphs (¶1 to ¶3, ¶5, ¶6), computed with a syllable heuristic: about grade 10 (213 words, 9 sentence units, 294 syllables). The long run-on sentences and nested parentheses in ¶1 and ¶2 push the score up. It is an estimate, not a validated measure. #### 👀 Visual learners - Present: none. The capture has no images, diagrams or embeds. - Improve: a short timeline of 2026-09-11 events and a table of claim, who asserts it and link status (as in Logical validity). #### 🔊 Aural learners - Present: no audio is referenced. - Improve: a 2-minute spoken summary that starts with the word "rumor." #### 🗣️ Verbal learners - Present: the post is plain, conversational prose with a clear opening claim (¶1). - Improve: a short glossary for board, interim CEO and instance, and a one-line "what is established" box. #### 🧩 Kinesthetic learners - Present: none. The post isn't a procedure. - Improve: an exercise: find three ways to check a board-membership claim, and record what each returns. #### 🧠 Logical learners - Present: a clear claim-then-support structure in ¶1 to ¶3, with an inferred causal chain in ¶5. - Improve: label each claim as sourced, unsourced or opinion, so the structure of the argument is visible. #### 🧑‍🤝‍🧑 Social learners - Present: the post is itself part of a social thread and quotes the account's earlier note (¶4 to ¶6). - Improve: a discussion prompt: "What would count as enough evidence to repeat a board-change rumor?" #### 🧘‍♀️ Solitary learners - Present: a short, self-contained post of about 330 words. - Improve: a self-check: "Which claims here have a link, and which don't?" #### 🌿 Naturalistic learners - Present: nothing relevant. - Improve: none needed. The ecosystem analogy would be forced here. ## 📊 Accessibility assessment Judged as captured. The capture is plain text recovered from a public endpoint, so the page's real markup, styling and focus behavior can't be seen. #### Screen reader semantics - Present: paragraph order is clear and each paragraph is one block of text (¶1 to ¶7). The page has no headings in the capture. - Improve: the original page's landmarks, language attribute and any alt text can't be checked here. A note with no images has no alt-text need. WCAG 1.3.1 (Info and Relationships) and 3.1.1 (Language of Page) are unverified. #### Keyboard navigation - Present: not assessable from the captured text. - Improve: the original scrape returned only a JavaScript-required message (¶7). That means the page depends on JavaScript to show its content. A reader without JavaScript sees nothing, which is a barrier for assistive-technology setups that run without scripts. #### Contrast and readability - Present: unknowable from text. Page styling isn't captured. - Improve: check 4.5:1 text contrast on the live page. #### Text resizing and reflow - Present: the capture reflows as plain text. - Improve: the live page's behavior at 200% zoom (WCAG 1.4.4, 1.4.10) can't be verified here. #### Media and captions - No media referenced in the captured text. #### Forms and interactions - Present: none. No form appears in the capture. - Improve: none needed. The instance's own reply and reshare controls are outside the capture. #### Standards reference - Candidate gaps against WCAG 2.2 AA, each unverified: **1.3.1** (structure of the live page), **2.1.1** (Keyboard, since the page needs JavaScript to render), **3.1.1** (page language). The one confirmed access issue is in ¶7: a JavaScript-required page returned no content to Reader's scraper. ## 🌍 DEIB assessment #### Cultural breadth - Present: an English-language post from one author on one instance. No multilingual content. - Improve: a plain-language summary for readers outside the WordPress and fediverse circles would add context the post assumes. #### Inclusive language - Present: the post uses he and him for Toni Schneider and Matt, as the source does (¶2, ¶3). It refers to Tumblr's trans staff by group (¶2) without naming individuals. - Improve: the post uses mocking nicknames and slang (¶5). Plain terms would carry the same point. Terms such as doxx and board would help with a glossary. #### Neurodiversity support - Present: short paragraphs (¶3, ¶6 are single sentences). - Improve: ¶1 and ¶2 pack several claims and a parenthetical into one sentence each. Splitting them into one claim per line would lower load. #### Representation - Present: two named individuals (Schneider, Matt) and one named group (Tumblr's trans staff) appear, all as subjects of @javi's account. None speak in the post. - Improve: the post has no voice from the people it discusses or from Automattic. A balanced treatment would quote a primary statement. #### Psychological safety - Present: the post has no content warning. It makes a serious allegation about a named person's online conduct toward a group (¶2) and uses mocking nicknames (¶5). - Improve: readers should avoid repeating the allegation as fact and avoid harassing anyone named in it. Moderated discussion, and a link to a primary source, would help. ## ✅ Logical validity Source type: opinion and rumor from a partisan author. The post offers assertions and no evidence chain. #### Strong reasoning - **Explicit hedging, ¶1.** The opening words mark the resignation as hearsay and seem to is a second hedge. The author doesn't claim certainty about the one checkable fact. Why it's strong: it keeps the claim in the category of rumor. To tighten, name the source or say there is none. - **Calibrated prediction, ¶6.** The quoted note uses suspect, which marks the forecast as a guess. Why it's strong: the author doesn't present it as knowledge. - **A checkable core, ¶1.** Board membership is a fact someone can verify with the company or in filings. That makes the central claim falsifiable. #### Fallacies - **Unsupported assertion, ¶2.** The statements about the 2025 interim-CEO period, the Tumblr letter and Matt's conduct appear with no link. Weakness: a reader can't check them from the post. Fix: link primary sources or label them as the author's recollection. - **Loaded language and name-calling, ¶5.** A mocking nickname for Matt and the phrase about reacting in panic shape the reader's view before any evidence. Weakness: it replaces argument with ridicule. Fix: state the observed action and cite it. - **Appeal to a character (good CEO versus the other), ¶2.** The post builds a contrast between a trusted CEO and Matt. Weakness: praise of one person doesn't support the claim that he resigned. Fix: keep the character judgment separate from the factual claim. - **Possible begging the question, ¶5.** The quoted note takes it as given that the board acted in panic and without securing support, then asks what the board found. Weakness: the premise is the author's reading. Fix: state it as interpretation. | Claim | Who asserts it | Link in the captured markup | |---|---|---| | Schneider has resigned from the board (¶1) | Unnamed rumors, relayed by @javi | None | | Schneider is CEO of Bluesky; led Automattic for about its first decade (¶1) | @javi | None | | Schneider was interim CEO in early 2025 (¶2) | @javi | None | | Schneider approved the Tumblr staff letter (¶2) | @javi | None | | The board tried to remove Matt without securing support (¶5) | @javi, in the quoted earlier note | None | #### Tone of voice - Informal, partisan and emotional. Examples: contractions and slang throughout, the blunt verdict in ¶3, and a profanity in ¶5. The hedge at the start (¶1) is calm. The rest moves from praise (¶2) to ridicule (¶5). ## 🛡️ DARVO analysis Not applicable to this source. DARVO describes how someone accused of wrongdoing responds to an accuser. @javi isn't the subject of an accusation in this post, and the post isn't a response to one. Each element, briefly: - **Deny:** no denials appear. The author makes claims instead of rebutting any. - **Attack:** the post attacks Matt's conduct and uses a mocking nickname (¶2, ¶5). Matt isn't shown responding, so there is no accuser being undermined in the DARVO sense. The attack is the author's own criticism. - **Reverse victim/offender:** none. The post casts Tumblr's trans staff and Schneider as acting against Matt's conduct (¶2), which is the author's framing of the allegation, not a reversal by an accused party. ## 🎯 Conclusion The post is a rumor that Toni Schneider resigned from Automattic's board, relayed by @javi on goblin.band on 2026-09-11, with no source and no link. The author hedges the claim and wraps it in praise of Schneider, allegations about Matt, and a quoted earlier note that speculates about the board's reasons. Only the resignation itself is a checkable fact. The rest is the author's opinion or unlinked assertion. The capture is a recovery from the instance's public endpoint, because Reader's own scrape returned only a JavaScript-required message (¶7). **Next steps for readers:** don't repeat the resignation as fact. Look for an Automattic statement or named reporting, and cite the post only as one author's rumor. Leave the allegations about named people out of any summary unless a primary source backs them. ## 🔄 Refactor Appendix — Rumors say Toni Schneider resigned from the Automattic board > Density: 2–5 Literature atoms (H1 pad), 0–3 Permanent candidates (H4 pad). > Emitted: 3 Literature, 1 Permanent. Resonance filter applied: the 2025 allegations were not > turned into atoms because they carry no source, and the recovery line is pipeline text. > > Konik claim-header rules: present tense, declarative, ≤10 words, searchable, unique. > > Atomicity: one declarative sentence per atom. "and"/"also" → split. > > Tag pool: #bmf · #addendum · #xref · #articleseed · #storystem · #share · #aphorisms ### 📚 Literature Split Pad #### [H1] The post relays a resignation as a rumor > [!quote] [¶1] > Rumors say that Toni Schneider, CEO of bluesky **Context & use**: - ¶1, the opening words. The same sentence ends with the claim he seems to have resigned from the board of directors. - The hedge and the lack of a named source are the facts to carry forward. The resignation is not established. **Tags**: #xref #share <!-- atomicity: 1 idea ✓ --> #### [H2] The author calls the departure bad news > [!quote] [¶3] > Him leaving the board are awful news for the company and its employees. **Context & use**: - ¶3, a judgment sentence. It assumes the resignation happened. - Keep the judgment separate from the factual claim when citing the post. **Tags**: #xref <!-- atomicity: 1 idea ✓ --> #### [H3] The earlier note's prediction is labeled a guess > [!quote] [¶6] > Given the urgency they acted with, I suspect it's not going to take long. **Context & use**: - ¶6, the close of the quoted earlier note. The word suspect marks it as speculation. - Useful as a checkable forecast: nothing in this source says whether it came true. **Tags**: #xref #addendum <!-- atomicity: 1 idea ✓ --> ### 🧠 Atomic Split Pad #### [P1] A hedge does not make a rumor evidence **Claim** (one sentence, Courtney's voice): A relayed rumor with a polite hedge is still a rumor, so cite the hedge and the missing source, not the claim. **Evidence pointer**: [[#H1]] **Scope & conditions**: Holds for any social post that relays a claim without naming where it came from. Breaks when the author later links a primary source or the company confirms. Here the post names no source and links nothing. **Links**: - [[Source assessment for community news]] — because extends - [[Governance transparency in open-source companies]] — because applies-in board and leadership changes - [[Reporting versus commentary]] — because contrasts on whether the post gives evidence or only opinion <!-- atomicity: 1 idea ✓ --> ### ✏️ Fleeting Queue - [F1] Check for an Automattic or Bluesky statement on Toni Schneider's board status after 2026-09-11 #fleeting #inbox - [F2] Open question: who told @javi, and did the author update the post? #fleeting #inbox - [F3] Note on how to cite a relayed rumor, hedge first and source second #fleeting #inbox #articleseed ### → Things 3 (max 2 actions) - [ ] Look for an official statement or named reporting on Toni Schneider and Automattic's board, WordPress governance tracking #things - [ ] Draft a short guide on citing unverified rumors about WordPress leadership, WordPress community education #things <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Articles/Rumors Say Toni Schneider Resigned From the Automattic Board.md|Rumors Say Toni Schneider Resigned From the Automattic Board by @javi (goblin.band)]] ## Highlights - Rumors say that Toni Schneider, CEO of bluesky and the guy who actually was the CEO of automattic during its first decade or so (so basically built the company for Matt), seem to have resigned from the board of directors. ([View Highlight](https://read.readwise.io/read/01m2b019za3mrx5gzpg0c18329)) - Note: Unverified rumor, no source linked. TechCrunch's Sept 11 story doesn't mention Schneider. Confirm board membership before citing. - Tags: atom/fleeting/f1