<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Kellie Peterson on Medium]]></title>
        <description><![CDATA[Stories by Kellie Peterson on Medium]]></description>
        <link>https://medium.com/@kelliepeterson?source=rss-2fe96dee7f10------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*W-OyNK-_9pWcPWPK</url>
            <title>Stories by Kellie Peterson on Medium</title>
            <link>https://medium.com/@kelliepeterson?source=rss-2fe96dee7f10------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 04:03:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kelliepeterson/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Automattic Wants .wordpress. It Doesn’t Own WordPress.]]></title>
            <link>https://medium.com/@kelliepeterson/automattic-wants-wordpress-it-doesnt-own-wordpress-d9e6be3f3a45?source=rss-2fe96dee7f10------2</link>
            <guid isPermaLink="false">https://medium.com/p/d9e6be3f3a45</guid>
            <category><![CDATA[icann]]></category>
            <category><![CDATA[trademark]]></category>
            <category><![CDATA[domains]]></category>
            <category><![CDATA[wordpress]]></category>
            <dc:creator><![CDATA[Kellie Peterson]]></dc:creator>
            <pubDate>Thu, 08 Oct 2026 09:05:54 GMT</pubDate>
            <atom:updated>2026-10-08T09:05:54.634Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ec_ENkYmdrD-4exLuo8EMA.png" /></figure><p><a href="https://www.icann.org/">ICANN</a> published the <a href="https://newgtldprogram-aps.icann.org/applications">full list of 2026 top-level domain applications</a> this week. All 2,783 of them. I went looking for one string out of curiosity and came away reading a different one three times. I also made a pit stop at .taylorswift because… duh, but that’s beside the point.</p><p>Automattic has applied for .wordpress.</p><p>Some disclosure first. I worked for Matt Mullenweg years ago. I’d also spent the majority of my career in the domain name space, so I read ICANN filings the way other people read box scores. I may have a personal axe to grind with Matt, but that doesn’t mean I don’t know what I’m talking about. I read this application, then I read the rulebook it was written against. Together they say something the application alone doesn’t.</p><h3>What they’re asking for</h3><p>The applicant is Knock Knock WHOIS There, LLC, the Automattic subsidiary that has run .blog since 2016. Its filing asks ICANN for an exemption from the Registry Operator Code of Conduct, which is Specification 9 of the standard registry contract. Registration in .wordpress, the application says, “will not be made available to unaffiliated third parties.” Every name would belong to Automattic or its affiliates.</p><p>The Code of Conduct is the rule that keeps a registry from favoring itself. Closed brand registries routinely get out of it. Apple doesn’t sell .apple domains, and nobody needs protecting from self-dealing when the only customer is Apple. It made its intentions clear by applying as a “.brand” TLD.</p><p>The filing also insists WordPress is not a “Generic String.” That matters because ICANN won’t approve a closed generic, a general term locked up by one company, until it has a method for judging whether one serves the public interest. To get a closed .wordpress, Automattic has to convince ICANN that WordPress is a brand and nothing more.</p><h3>The test that never asks who owns the name</h3><p>Automattic doesn’t own the WordPress trademark. The WordPress Foundation, a nonprofit Matt started in 2010, holds it. When the mark moved, Matt wrote that WordPress’s name was now <strong>“fully independent from any company.</strong>” Under the Foundation’s trademark policy, Automattic holds an exclusive license for commercial use.</p><p>Here’s what I didn’t expect when I opened ICANN’s 2026 Applicant Guidebook. The Code of Conduct exemption has exactly three tests, set out in Section 7.4.4. Every registration must belong to the registry operator or its affiliates, for their exclusive use. None can be sold or handed to anyone outside that group. And applying the Code must not be “necessary to protect the public interest.”</p><p>Trademark ownership isn’t one of them. ICANN runs a separate track for brand TLDs, called Specification 13, which requires a registered trademark verified through the Trademark Clearinghouse. But the Guidebook says plainly that an applicant can get the Code of Conduct exemption without qualifying for brand status.</p><p>So the application describes WordPress as a brand that “corresponds to” registered trademarks and never says who owns them. No evaluator will flag that. The test it applied under doesn’t ask.</p><h3>Pick one</h3><p>If Automattic also wants .wordpress designated a brand TLD, the trademark comes back into play, and the registered owner of that trademark is the Foundation. Watch how Automattic connects itself to a mark it doesn’t own. The obvious route runs through ICANN’s definition of “Affiliate.”</p><p>The registry contract defines affiliates by control, and it counts control exercised “by serving as an employee or a member of a board of directors.” Matt is Automattic’s CEO. He is also one of the WordPress Foundation’s three board members, according to its 2022 tax filing as reported by LWN.</p><p>For sixteen years, whenever someone asked whether one company had too much say over WordPress, the answer was that the name belongs to an independent nonprofit. That answer got heavy use once the WP Engine fight started in 2024. The Foundation can be independent of Automattic, or it can be under common control with Automattic. It can’t be both, and an ICANN filing is a strange place to quietly choose.</p><h3>“Nobody uses those things anyway”</h3><p>That’s the reply I expect first, and on the surface it’s right. Most people have no idea what a top-level domain is. Plenty of companies bought their own in the last round of “new TLDs” and did little with them. Nobody is going to type plugins.wordpress into a browser. Yet.</p><p>Usage was never the point. <strong>An approved application is a record</strong>. The body that coordinates the internet’s naming system would have accepted that WordPress is not a generic term, and handed a closed namespace carrying that name to the trademark’s commercial licensee. That record holds whether or not anyone ever visits a single domain.</p><h3>Built to last</h3><p>The standard registry contract runs ten years and renews for further ten-year terms, except in narrow cases tied to breach. That’s Sections 4.1 and 4.2.</p><p>Closed registries get one more protection. Under Section 4.5, a registry that keeps every name for itself and its affiliates, and where no public-interest reason requires a handover, can’t have its TLD moved to a new operator when the contract ends unless it consents. Those are the same conditions the Code of Conduct exemption is built on.</p><p>A trademark license is a permission. Nothing in the exemption ties the TLD to that permission. If Automattic’s license to the WordPress name ever changed, .wordpress would stay right where it is.</p><p><strong>Then there’s what a closed namespace can hold. A list of certified hosts. A plugin marketplace. Email addresses that look official. None of that exists today, and maybe it never will. Once this is approved, Automattic alone decides.</strong></p><h3>What you can do, and when</h3><p>Nothing is open yet. The list of applied-for strings locks on November 17, 2026. That starts the community input period, which ICANN says runs to March 16, 2027, with a pause built in for its year-end office closure.</p><p>The Guidebook says a <strong>Code of Conduct exemption request is open to public comment</strong>, and evaluators consider only comments that arrive inside the window. The third test is where comments count. ICANN has to conclude that applying the Code to .wordpress is not necessary to protect the public interest. For a name attached to an open-source project built by thousands of people outside Automattic, and relied on by hosts that compete with Automattic, that conclusion deserves a fight. So does the claim that WordPress is a brand and not a general term for a kind of software.</p><p>If you build with WordPress, host it, sell plugins for it, or contribute to core, read the application yourself on <a href="https://newgtldprogram-aps.icann.org/applications">ICANN’s Application Publication System</a>. Comment when the window opens. If hosts and contributors want to go further, ICANN’s rules allow a community objection. It requires showing a clearly delineated community, substantial opposition within it, a string that targets it, and likely detriment.</p><p>I hope I’m wrong about where this goes. I’d still rather say it now, while it can matter, than in 2028, when someone explains that the comment period closed and nobody noticed.</p><h3>Sources</h3><ul><li><a href="https://www.icann.org/en/announcements/details/icann-reveals-2026-round-applications-for-new-generic-top-level-domains-07-10-2026-en">ICANN Reveals 2026 Round Applications</a>, ICANN, October 7, 2026</li><li><a href="https://newgtldprogram-2026-agb.icann.org/en/11-module-7-string-and-application-evaluation-procedures.html">2026 Applicant Guidebook, Module 7</a>: Sections 7.1.2.4 (.Brand TLDs), 7.3 (.Brand eligibility), 7.4 (Code of Conduct exemption)</li><li><a href="https://newgtldprogram.icann.org/sites/default/files/documents/new-gtld-program-2026-round-applicant-guidebook-current-en.pdf">2026 Applicant Guidebook, full PDF</a>: Sections 1.2.1.7 (closed generics) and 1.2.3 (community input)</li><li><a href="https://itp.cdn.icann.org/en/files/registry-agreements/base-registry-agreement-12-03-2026-en.pdf">2026 Base Registry Agreement</a>: Sections 2.9(c) (Affiliate), 4.1–4.2 (term and renewal), 4.5 (transition)</li><li><a href="https://newgtldprogram-aps.icann.org/applications">Application Publication System</a>, ICANN</li><li><a href="https://lwn.net/Articles/991771/">LWN on the WordPress Foundation and trademark</a>, October 2024</li><li><a href="https://icannwiki.org/.blog">.blog on ICANNWiki</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d9e6be3f3a45" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Long Con: How Matt Mullenweg Used the WordPress Community to Build His For-Profit Empire]]></title>
            <link>https://medium.com/@kelliepeterson/the-long-con-how-matt-mullenweg-used-the-wordpress-community-to-build-his-for-profit-empire-afa26d26002c?source=rss-2fe96dee7f10------2</link>
            <guid isPermaLink="false">https://medium.com/p/afa26d26002c</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[wordpress]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[publishing]]></category>
            <dc:creator><![CDATA[Kellie Peterson]]></dc:creator>
            <pubDate>Fri, 06 Jun 2025 20:23:53 GMT</pubDate>
            <atom:updated>2025-06-07T05:35:17.563Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MlyYILJSnCaM5ND-8UrWpA.png" /></figure><p>More than two decades ago, WordPress was born as a humble open-source blogging tool. Its co-founder, Matt Mullenweg, quickly became a beloved figure in the open-source world — a charismatic leader who championed freedom, community-driven development, and software for the people.</p><p>However, recent developments suggest that Mullenweg has leveraged the WordPress community to further his own business interests, raising serious questions about the project’s governance and the ethical implications of his actions.</p><p>Behind the polished keynote speeches and his affable public persona, Mullenweg has carefully orchestrated a system in which unpaid contributors build and maintain a multi-billion-dollar ecosystem — largely to serve the strategic goals of his privately held, for-profit company, Automattic Inc. The deeper one digs into the governance of WordPress.org, the more it becomes clear: this isn’t a story of community triumph. <strong><em>It’s a long con</em></strong>.</p><h3>WordPress.org: A “Community Asset” Owned by One Man</h3><p>The ongoing beef with WP Engine, which began late last year, has shed light on the long-obfuscated truth: Mullenweg personally owns the WordPress.org domain. This is more than symbolic. WordPress.org hosts the official plugin repository and serves as the primary hub for distributing WordPress itself. That ownership grants enormous power over the ecosystem’s direction.</p><p>This structure has led to growing concerns about the concentration of power. It means that the face of the open-source project — and the CEO of a private for-profit company — has ultimate control over the main distribution channel, the brand, and the communications platform that defines WordPress.</p><p>It’s not just a potential conflict of interest. It’s an ongoing one.</p><h3>Free Labor, Private Gain</h3><p>At the heart of WordPress’s success is an army of unpaid contributors who dedicate their time and expertise to the project’s development. These volunteers believed they were contributing to a common good, improving the web through a shared, open tool. But in practice, their work often aligns perfectly with <strong><em>Automattic’s strategic goals</em></strong>.</p><p>Consider the “Five for the Future” initiative — a program that encourages companies and individuals to dedicate 5% of their resources to the WordPress project. While framed as a noble contribution to the project, it also ensures a steady flow of unpaid labor and influenceable goodwill into a project that ultimately advances Automattic’s interests.</p><p>Automattic is the single largest corporate contributor to WordPress core, yet it employs only a minority of the core committers. Despite this, it has an outsized influence on major decisions — often to the frustration of the broader community. Long-requested improvements from users and developers languish, while features that support Mullenweg’s vision for WordPress.com and Automattic are prioritized.</p><p>This is to say nothing of the long-standing confusion between <strong>WordPress.org</strong> (the open-source project) and <strong>WordPress.com</strong> (Automattic’s commercial platform), which continues to benefit Automattic while misleading users.</p><h3>The “4-Hour Workweek” Reimagined</h3><p>Matt Mullenweg has openly admired productivity evangelists like his good friend Tim Ferriss, author of <em>The 4-Hour Workweek</em>, who advocates optimizing one’s time by outsourcing work and minimizing labor. But Mullenweg appears to have taken this philosophy to its most cynical conclusion: why pay people to build a product when you can convince thousands to do it for free?</p><p>Not only did Mullenweg leverage a global labor market to build Automattic into one of the first truly distributed companies — often asking U.S.-based employees to take less “for the mission” — he also cultivated a system in which volunteers work for free under the illusion of shared ownership.</p><p>While he rarely commits code anymore, Mullenweg’s influence over project direction remains absolute. Volunteers are thanked with badges and swag — not equity, not compensation, and certainly not any meaningful role in governance.</p><p>This is not to deny Mullenweg’s influence on the modern web. WordPress has undeniably empowered millions. But when the fruits of a community’s labor are funneled into a privately owned, lightly regulated, and profit-oriented company, the moral clarity of open-source participation becomes deeply muddied.</p><h3>Governance Reform is Long Overdue</h3><p>Why is there no independent, nonprofit foundation overseeing WordPress.org? Why is project governance so opaque? And why are Automattic’s commercial interests so entangled with decisions that should be made democratically?</p><p>Open-source is built on trust, shared goals, and transparency. When one man owns the distribution channel, controls the brand, and leverages volunteer labor to fuel his private company’s growth, it ceases to be a movement — it becomes a business model dressed in community clothing.</p><p>Matt Mullenweg may have mastered the art of doing less while appearing to give more. But it’s the community that has paid the price in time, energy, and idealism. They deserve better than an open-source project with a closed door at the top.</p><h3>It’s Time to be FAIR</h3><p>That’s where the <a href="https://github.com/fairpm">FAIR Project</a> comes in.</p><p>Today, at Alt CTRL ORG in Basel, the <strong>FAIR Project</strong> announced the launch of its <strong>WordPress Package Manager</strong> — a serious response to the questions about control and distribution that have grown deafening in recent months.</p><p>Backed by the <a href="https://www.linuxfoundation.org/press/linux-foundation-announces-the-fair-package-manager-project-for-open-source-content-management-system-stability"><strong>Linux Foundation</strong></a>, organized by <strong>Joost de Valk</strong> and <strong>Karim Marucchi</strong>, and steered by trusted community figures like <strong>Carrie Dils</strong>, <strong>Mika Epstein</strong>, and <strong>Ryan McCue</strong>, FAIR aims to bring true decentralization to the WordPress ecosystem.</p><p>If it succeeds, it could do something that no plugin, no fork, and no blog post has managed to do: make Matt Mullenweg — and WordPress.org — irrelevant.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=afa26d26002c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[It’s a Maison thing, you wouldn’t understand.]]></title>
            <link>https://medium.com/@kelliepeterson/its-a-maison-thing-you-wouldn-t-understand-9182b400ec74?source=rss-2fe96dee7f10------2</link>
            <guid isPermaLink="false">https://medium.com/p/9182b400ec74</guid>
            <category><![CDATA[wordpress]]></category>
            <category><![CDATA[branding]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Kellie Peterson]]></dc:creator>
            <pubDate>Thu, 15 May 2025 11:02:28 GMT</pubDate>
            <atom:updated>2025-05-15T14:20:27.686Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-N5Z_ytOsB5CwzLJK1wJtg.jpeg" /></figure><p>Automattic was the darling of distributed work long before the pandemic. The company was also innovative in the way they interviewed prospective hires, structured teams, and even with the language of work. One could be forgiven for thinking it precious to call support professionals Happiness Engineers and software engineers Code Wranglers.</p><p>CEO Matt Mullenweg and other leaders have a habit of creating or adopting non-standard names for commonly accepted terms. The silly vocabulary is so widespread there is a glossary actually built into P2 (the company communication platform)!</p><ul><li>“Automattician” for employee or staffer. The OG cute replacement.</li><li>“Post-economic” for independently wealthy, AKA rich AF technojerk</li><li>“Bizzer/Byzzer” for SMBs</li><li>“AFK” for PTO/vacation</li><li>“JITM” for the actual message delivered as part of the “Just-in-time-messaging” strategy. Example: Send JITM when X happens vs. trigger SMS when x happens.</li></ul><p>A former colleague posted this explanation of the new structural nomenclature being used at Automattic this year. Yes, I said “this year”. Seems like every year or two Automattic’s CEO gets a wild hair and decides to shake up the entire organization with some new model or terminology he wants to embrace.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/543/1*N4fXfxMANtWzkX9LKGq0HA.png" /><figcaption>The “Maison” model comes from the <a href="https://www.lvmh.com/en/our-maisons">LVMH luxury house</a>.</figcaption></figure><p>This critique isn’t direct to the person who posted this, rather to the thinking that led to using this model/nomenclature on a tech company, specifically Automattic.</p><p>LVMH as you may know is a French luxury brand conglomerate. From a marketing structure they operate as a House of Brands (in less luxurious terms think of Proctor &amp; Gamble, Unilever, and Nestle) vs. a Branded House (Samsung, Google).</p><h3>Misapplied Luxury Metaphor</h3><p>The <em>Maison</em> model at LVMH works because it applies to fashion, fragrance, wine, and other desirable luxury goods where brand allure, heritage, and aesthetic cohesion are important. Trying to apply this to a technology company where utility, speed, scalability, and functionality matter far more than taste rings intellectually shallow.</p><blockquote>“Business Units are now Maisons. ‘Leads’ and ‘Heads of’ have become Artistic Directors.”</blockquote><p>This is branding for branding’s sake. It does nothing to clarify roles or responsibilities. Where “Maison” elicits thoughts of haute couture I have a hard time applying it to a blog or a podcasting app. The use of the title “Artistic Director” makes so little sense in this context it borders on absurdity.</p><h3>Taste as a Moat? Deeply Oversimplified</h3><blockquote>“If AI drives execution cost to zero, then taste is the new moat.”</blockquote><p>Holy Silicon Valley pseudo-wisdom Batman! Execution is never free. It changes, sure, but implying that AI eliminates all executional barriers is naive. Taste is important, but reducing competitive advantage to “vibes” ignores the grinding complexity of shipping good software.</p><p>It also treats “taste” as some kind of mystical quality rather than a mix of intuition, testing, data, and product-market fit. Automattic’s leadership rarely allows for taking the time and effort to adequately intuit what a customer desires or needs or test. I’m sure this will go well.</p><h3>Leadership Abdication Rebranded as “Artistry”</h3><blockquote>“I’m no longer responsible for direct reports…”<em><br> </em>“But my work will influence theirs… hopefully they will be HAPPY to follow my suggestions.”</blockquote><p>At a company that just laid off 16% (281) of its workforce then internally gaslit the remaining employees by blaming it on “feedback inflation” this seems like a truly unhinged direction.<br>You’re removing accountability, decision-making authority, and team ownership and yet Artistic Directors get the influence and prestige of being a leader. That’s not artistry. It’s merely <em>Sparkling Incompetence </em>topped with a jaunty beret.</p><h3>Faux Depth, Real Vagueness</h3><blockquote>“shaping taste, vision, and cultural coherence”<em><br> </em>“render a product meaningful, desirable, necessary”</blockquote><p>What the heck does “shaping cultural coherence” mean in a continuous delivery software pipeline? How do you render a plug-in <em>necessary</em> through “taste”? As though anything that Automattic sells is necessary at all. Hollow abstractions posing as innovation is very on brand for Automattic though so I ought not be surprised.</p><h3>How Does This Benefit the Customer?</h3><blockquote>“That’s why we’re changing our language — and our mindset — around how we build and lead.”<br><em>“</em>time to update my LinkedIn…”</blockquote><p>These lines reveals that part of this rebrand isn’t about user value or organizational efficiency. It’s about signaling. Changing language and mindset, but nothing about <em>how</em> you actually build? Automattic trying to position themselves as a premium purveyor of pixels and giving them something to new squawk about that isn’t related to their war on WP Engine.</p><p>This new Maison terminology isn’t visionary, it’s cosplay. Swapping job titles for couture terms doesn’t create vision, leadership, or value. It creates confusion, erodes clarity, and suggests Automattic is more interested in aesthetics than outcomes. Dressing up organizational role changes in the language of luxury houses doesn’t make you LVMH, you’re just LARPing as them.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9182b400ec74" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is the WordPress v WP Engine Drama Really About?]]></title>
            <link>https://medium.com/@kelliepeterson/what-is-the-wordpress-v-wp-engine-drama-really-about-3a82a54e7553?source=rss-2fe96dee7f10------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a82a54e7553</guid>
            <category><![CDATA[wordpress]]></category>
            <category><![CDATA[matt-mullenweg]]></category>
            <category><![CDATA[private-equity]]></category>
            <category><![CDATA[automattic]]></category>
            <category><![CDATA[blackrock]]></category>
            <dc:creator><![CDATA[Kellie Peterson]]></dc:creator>
            <pubDate>Wed, 09 Oct 2024 03:31:12 GMT</pubDate>
            <atom:updated>2024-10-09T04:14:40.407Z</atom:updated>
            <content:encoded><![CDATA[<h4>Money. Well that and ego. Isn’t it always?</h4><p>In the David vs. Goliath tale that Matt Mullenweg is spinning in his <a href="https://techcrunch.com/2024/10/04/wordpress-vs-wp-engine-drama-explained">battle against WP Engine</a>, one of his major criticisms is that WP Engine is backed by the private equity firm Silver Lake, which manages over $102 billion in assets. During his fiery keynote at WCUS, Mullenweg stated, “Silver Lake doesn’t give a dang about your open-source ideals; it just wants a return on capital.” Silver Lake’s control of WP Engine dates back to 2018.</p><p>However, Mullenweg is not exactly the David in this scenario. I don’t buy this being about protecting open source from private equity or WP Engine; if it were, it would have been handled differently.</p><p>What Mullenweg has not discussed recently is that his for-profit company, Automattic, has been backed by BlackRock since 2021. BlackRock manages over $9 trillion in assets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/806/1*MqQNVFG7xDGWMFoYpT3YFQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/796/1*mkL0Oqm_qySQBVzzh6DzrA.png" /></figure><p>In the lead-up to Matt’s WCUS attack on WP Engine, a post dated September 20, 2024 titled “<a href="https://ma.tt/2024/09/are-investors-bad/">Are Investors Bad?</a>” fails to mention The BlackRock investment. Instead, he lists other investors, including True Ventures, Addition, Tiger Global, Salesforce, GIC, ICONIQ, LVMH/Aglaé, Akkadian, Wellington, Sweetwater, Alta Park, Schonfield, and Chris Sacca.</p><p>Matt seemed eager to share the news of the <a href="https://ma.tt/2021/08/funding-buyback-hiring/">BlackRock investment in Automattic</a> back in August of 2021, six months after the $288M investment round closed. He also stated “We’ve grown and increased our valuation at a rate higher than most other alternate investments available to investors.” What about since then?</p><h4>Matt’s investment in WP Engine</h4><p>WP Engine built their entire platform around WordPress. In 2011 when WP Engine was generating ~$1M in annual revenue with approximately 30k customers, <a href="https://wpengine.com/blog/wp-engine-closes-1-2m-in-series-a-financing/">Automattic invested in WP Engine</a>. The $1.2M round was led by Silverton Partners and closed in November.</p><p>Mid 2011 (perhaps around the time that fundraising round was being negotiated?) the very permissive WordPress Foundation Trademark Usage Policy was updated to include:</p><blockquote>We do not allow the use of the trademark in advertising, including AdSense/AdWords.</blockquote><p>The policy has gotten a lot longer but is still permissive:</p><blockquote>Similarly, it’s OK to use the WordPress or WordCamp logo as part of a page that describes your products or services, but it is not OK to use it as part of your company or product logo or branding itself. Under no circumstances is it permitted to use WordPress or WordCamp as part of a domain name or top-level domain name.</blockquote><p>Automattic maintained its investment until Silver Lake acquired control of WP Engine in 2018. Was Automattic forced out of its investment? Is Matt just bitter that he’s no longer benefiting from their growth?</p><h4>Head to head growth of Automattic &amp; WP Engine since</h4><p>2020 was a hellscape of uncertainty all over the world thanks to the pandemic. One sector that thrived? Anything related to creating and expanding an online presence. This was a prime time for securing additional investment.</p><p>In February 2021, Automattic closed that $288 million investment round, bringing BlackRock into the picture and increasing Automattic’s valuation to $7.5 billion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wkDnXa94DrqMEQyxcSpoyw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W2YHtydWTRnuQlAQEij3sQ.png" /></figure><p>While Automattic has a diverse portfolio of revenue sources (WooCommerce, VIP, domains, .Blog, etc. fueling growth), WP Engine maintains a singular focus: selling WordPress hosting.</p><p>Since 2021, WP Engine has evidently quadrupled its revenue. By contrast, Automattic, including all its business units, may not have even doubled its revenue during the same period.</p><p>Given this context, one might wonder if Matt’s recent trademark scrutiny is an attempt to bolster earnings under pressure from investors or creditors. What kind of growth promises were made, and to whom?</p><p>Is Mullenweg trying to rewrite history and alter how WordPress is licensed now that other companies are more successful with his creation than he is?</p><p>Love him or hate him DHH has an <a href="https://world.hey.com/dhh/automattic-is-doing-open-source-dirty-b95cf128">excellent read with more detail on the open source aspect</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a82a54e7553" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“Nice Guy” Matt Mullenweg, CEO of WordPress.com Cries Foul and Threatens Me With Legal Action]]></title>
            <link>https://medium.com/@kelliepeterson/nice-guy-matt-mullenweg-ceo-of-wordpress-com-cries-foul-and-threatens-me-with-legal-action-f116ac57d862?source=rss-2fe96dee7f10------2</link>
            <guid isPermaLink="false">https://medium.com/p/f116ac57d862</guid>
            <category><![CDATA[automattic]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[wordpress]]></category>
            <category><![CDATA[wpengine]]></category>
            <dc:creator><![CDATA[Kellie Peterson]]></dc:creator>
            <pubDate>Thu, 03 Oct 2024 04:33:51 GMT</pubDate>
            <atom:updated>2024-10-03T04:33:51.848Z</atom:updated>
            <content:encoded><![CDATA[<p>TL;DR: Matt Mullenweg, the CEO of Automattic, co-founder of WordPress, and single point of failure for <a href="http://wordpress.org/">WordPress.org</a> is trying to bully me with legal threats over my commentary regarding <a href="https://joshcollinsworth.com/blog/fire-matt">his recent behavior</a>.</p><p>On Tuesday I posted a couple tweets after a long hiatus on the app. I’d been informed that Matt had issued an invitation to employees who disagreed with his actions or direction over the last week (or more?) to leave Automattic. The invitation came with a severance package of a minimum of $30k USD or six months salary (whichever was more), healthcare until October 31, the ability to keep the company provided laptop, etc. The big caveat is that those who accept would become ineligible for rehire. I had also replied to a couple of other tweets with straightforward facts and an opinion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2UT1fAFsH21Pc9XQ7BXY2A.png" /></figure><p>To my surprise I found a DM from Matt when I woke. I should have known what was in store. In the six plus years I’d worked for him the only time I can remember getting an unsolicited ping from him was when he was unhappy.</p><p><em>Disclaimer for Matt and any armchair legal experts: This is not doxing.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nnOodooIS1oYbw-cIIod5w.png" /></figure><p>Uh. No attacks detected mate.</p><p>Commentary: ✔️ <br>Attacks: ❌</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QtW5L3l2_7ovrzJasNzLdg.png" /><figcaption>Sharing my take and feedback to him.</figcaption></figure><p>And then!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pqu-gcoqwWwoXeyk7tXMCg.png" /><figcaption>FYI: My offer to help new Automattic alumni still stands.</figcaption></figure><p>Uh oh… spicy Matt enters the chat!</p><p>My dude, you invited people to leave your employ. Even if I was looking to poach your people (which, <a href="https://x.com/VicVijayakumar/status/1841667823870894409">pot... kettle… eesh</a>) I feel like offering to pay them to leave might damage your case. Regardless, I’m retired. I’m not soliciting anything and my offer was clearly *if* someone takes it without something lined up. Which seems is most of them. Ouch.</p><p>Remember how he started off with “I’ve never been anything but nice to you, and we worked together for years.” Ladies… does this sound familiar? IYKYK.</p><p>Yes, Matt was often kind to me as well as many others. But he was also dismissive, demeaning, and demoralizing. To myself, to my team, and to my colleagues — we were all subject to his mercurial moods, whims, and rampages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QcSm9bLv5V36rkfAf174vg.png" /><figcaption>“Every villain is a hero in his own mind.” — Tom Hiddleston</figcaption></figure><p>Honestly, my biggest regret is that I did not think to replace “retired” with being “post-economic” as he likes to describe his financial status thanks to his alleged $400MM net worth.</p><p>You might be asking yourself why I’m sharing this at all. I could probably list a dozen reasons but these are at the forefront:</p><ol><li>I am not a WP Engine (or PE in general) apologist. I believe they should contribute more to core, etc. However, what Matt has done, is doing, continues to do is antithetical to opensource, to his own stated goals to democratize publishing and to grow the use of WordPress. He has demonstrated time and again that when he does not get his way or has no leg to stand on he will default to subterfuge to achieve his goals.</li><li>He has harmed the community that he is supposed to be leading. He is harming the ecosystem that he helped to build. He is harming the reputation of each of the 2000 (and dwindling) employees who have long been proud to call themselves Automatticians. He is harming his own legacy. Be more Jimmy Carter and less Elon Musk.</li><li>Finally, and most importantly: <strong>Because I can and others feel unable to</strong>. Matt may not be a billionaire but we’ve all seen him go after people with his <em>Smallest Man Who Ever Lived</em> petty crown. Current Automatticians rely on him for their livelihoods. Former Automatticians who aren’t lucky enough to be “post-economic” know better than to openly critique him because they still need jobs and no one wants to risk losing a reference or being seen as denouncing their former boss, etc.</li></ol><p>Yes, Matt could sue me and tie me up in court on some bogus complaint, but otherwise he can’t hurt me. Matt is blind to his privilege in so many ways and he wields his power irresponsibly. He has maintained iron clad control over Automattic, WordPress, and WordPress.org. How? By insisting on securing the proxy votes from investors. Investors — what on earth were you thinking? My hope for the sake of WordPress, the community, the health of the wider ecosystem, the employees of Automattic, and heck — even your own investment — is that you take action and hold Matt to account for his actions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f116ac57d862" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>