If WordPress is to survive, Matt Mullenweg must be removed

There are some people who think being right about something gives them the right to do whatever they think should be done about it; a license to act however they see fit in order to correct that wrong.

This, of course, is never the case. Doing the wrong thing for the right reason never makes it the right thing. No matter how bad the original infraction, there are some responses it never justifies. Two wrongs don’t make a right, to be pithy about it. The ends don’t justify…you know how it goes.

Matt Mullenweg appears to be one of those people who believe the ends do indeed justify the means, as he’s effectively blowing up massive swaths of the WordPress community in his fight with some of its landlords.

Matt has, for far too long, enjoyed unchecked powers at the top of WordPress—powers which are all too often a direct and flagrant conflict of interest. And while we’ve seen this power abused before, we’ve never seen it on this scale.

Yes, Matt’s original point might be warranted. But his egregious actions utterly nullify any previous merit.

A line has been crossed, and the entire community is worse for it.

I believe that if WordPress is to survive, let alone thrive, Matt Mullenweg must be removed from all forms of official WordPress leadership, as expediently as possible.

Wait, who are you and why do you care?

Let’s get this out of the way right off: I’m not the best person to be talking about this. I haven’t really been involved in WordPress for about five years now. Honestly, I couldn’t tell you the last time I even logged in to a WordPress site.

That said, however: I spent some six or seven years of my life deep in the WordPress world. I built and customized WordPress sites for clients as a designer; I taught a WordPress development course (focused on building custom themes in PHP) for about five years; and I worked in support for Flywheel, a managed WordPress hosting company, for a little over five years. It was there I transitioned to full-time frontend work, building tools to help support WordPress sites.

So while I’ve been out of the WordPress game for a good while now, I still might be considered an expert next to your average Joe. I’d like to think I could still sling some theme templates with the best of ‘em. (Hell, some days I even get a little nostalgic and think about booting up a Local site just for fun.)

You might have spotted the word “Flywheel” up there and realized that company was acquired by WP Engine—the company with which Mullenweg is publicly feuding at the moment—back in 2019. That might reasonably raise questions of my objectivity, so let’s get this out of the way:

Yes, I used to work for WP Engine. I even kinda liked them, for a while (mostly while they just kinda left us alone for the first year or so). But I wouldn’t say my time at the company left a good taste in my mouth.

We don’t need to dredge up a bunch of old and buried stuff that isn’t really important anyway, but suffice to say: I really don’t have any reason to be a WP Engine cheerleader. Most of the people I knew there have left, and I’ve watched from the sidelines as the company has implemented a bunch of scummy policies and shady sales tactics to squeeze money from their customers and make it harder to leave.

On most days, if you wanted to have a conversation about how much WP Engine sucks, frankly, I’d be a happy participant.

So this post might be a lot of things, but I can assure you it’s not me defending my old company just because I used to work for them. I’ve got literally no reason to do that.

To the extent I’m on WP Engine’s side, it’s not because of any sense of loyalty to the company or to the remaining good people I know there; it’s because I believe what Matt’s doing is deeply wrong and foolishly destructive.

I’ll also go on record as saying I got pretty far in the interview process at Automattic once, a few years back. And, since we’re being honest, it was the absolute worst interview process I’ve ever taken part of as a web professional (though the people themselves were lovely). But that alone ain’t gonna get a post out of me. I’m not wasting my time and yours just to gripe about an interview I chose to drop out of over three years ago. Just thought it merited a mention.

I still regarded Matt Mullenweg himself pretty highly after that, up until the last year or so. This post isn’t long enough to get into the details, but Matt had already become a pretty “problemattic” character well before any of this went down.

So in summary: I’m not a big fan of either party, and I don’t have any good reason to side with either one of them.

I am, however, somebody who still cares deeply about WordPress. It’s what gave me my start, and I still recommend it to a lot of people when they ask me what system might best suit their needs.

It’s a wonderful community, all in all, and despite my inactivity, I still feel invested in WordPress, and interested in seeing it continue to be a productive way to democratize the web.

Finally: I am not a lawyer, and since it’s Friday now and this feud had already reached lawyers-involved level by Monday morning, I should be careful to clarify any legal commentary here is expressly my personal, non-expert opinion.

I’m sorry, what happened?

For those of you who haven’t been following the story thus far (read: aren’t chronically online web nerds like me), let’s hit the highlights.

Automattic approaches WP Engine to offer a “license”

Sometime in or around July of this year, Automattic (Matt Mullenweg’s for-profit company, which owns, among other things, WordPress.com, a major WordPress hosting company) reached out to WP Engine (also a for-profit company that offers WordPress hosting, and probably Automattic’s largest business rival).

Automattic was offering WP Engine some kind of “licensing,” at a rate of 8% of total business revenue, adding up to the eye-popping sum of several million dollars per year.

WP Engine apparently turned down this offer, presumably because it doesn’t appear they actually need any license. The term “WP” is explicitly not covered by the WordPress trademark policy, and using the term “WordPress” to describe products and services (e.g., calling yourself a “WordPress specialist,” or saying you offer “WordPress hosting”) is fully allowed, according to the policy.

They’ve also been in business for like 15 years now, and somehow none of this has come up before.

Besides, I could name dozens of companies just off the top of my head also using one or both of those terms. So the “you need a license to say this” argument seems highly targeted and extremely dubious.

Matt’s rejected, so he tries new strategies

Immediately following WP Engine’s rejection, the WordPress Foundation (the nonprofit that governs WordPress, the open source software, and which Matt Mullenweg also runs, in effect if not nominally) filed to trademark the terms “Managed WordPress” and “Hosted WordPress.”

Neither trademark has been granted at this point, nor should they; they’ve been in use for ages, and are obviously far too generic for any one organization to hold.

Most reasonable and knowledgeable people seem to share this opinion. Companies have been describing themselves as one or both of those terms for around 15 years at this point. (We freely called Flywheel a “managed WordPress hosting company” the entire time I worked there, and we were far from the first. We were also at one point one of WordPress.org’s recommended hosts. So…obviously, not a big deal.)

Anyway, this filing of spurious trademarks makes it appear very much like Matt’s endgame was to extract money from WP Engine, but he just needed more of a foundation to do it (pun intended?). So, following that initial rejection, Matt set the Foundation arm of WordPress working on securing highly dubious trademarks, which, again, I and most reasonable observers think and hope will fail.

Meanwhile, Matt also began sending a series of very apparently extortive messages to WP Engine leadership, essentially demanding they pay up or else. (This is all in WP Engine’s letter to Automattic, which I’m getting to, but which comes later in the story.)

All of this was in the run-up to WordCamp US, the largest WordPress event of the year, at least in North America. (Of note: WP Engine sponsored this event at the highest level, as did WordPress.com.)

Matt let WP Engine leadership know, via private DMs, that he intended to “go nuclear” and “scorched earth” on WP Engine in his keynote at the conference—that is, if WP Engine failed to acquiesce to his monetary demands, i.e., 8% of total revenue, i.e., tens of millions of dollars. It appears he repeated the “just pay up and I’ll make this all go away” offer up to the literal last minute before he went on stage.

Let’s not beat around the bush: words like “threat” and “extortion” very much apply to Matt’s behavior here.

Again: this demand was ostensibly in exchange for a “license” to use terms like “WordPress,” “WordPress hosting,” “WooCommerce,” etc.—none of which appear to be actually necessary.

The only possible exception seems to be “WooCommerce,” which is a trademark (and product/company) owned by Automattic. However, the lines are very blurry on what is and is not permissable when it comes to using the WooCommerce name. WP Engine does indeed call one of its offerings “WooCommerce hosting,” which is explicitly called out in the guidelines. So I don’t know, maybe there’s validity there. Maybe.

However, for one thing, it’s hard to know whether, or how much the trademark guidelines might have changed. Matt made several changes to the WordPress license page in the last week, among other things, to call out WP Engine. That makes me not trust that the WooCommerce license page I’m looking at today is the same as it was last week—which, all on its own, should be setting off raging alarms for even the most casual of observers. It’s extremely bad news when the company you’re doing business with can just decide what the new terms are with no warning or recourse.

Anyway, Matt keeps sending the DMs all the way up until the literal last minute, offering not to excoriate WP Engine onstage during his keynote at the country’s (continent’s? world’s?) largest WordPress event, provided they simply pay up.

Once more: I’m no lawyer, but I’m pretty sure that’s called extortion.

WP Engine says no (actually, they ask for more time, which Matt denies and takes as a no), so he proceeds with operation “scorched earth,” and blasts WP Engine both onstage at WordCamp US, and in several other venues.

Wait—what’s Matt’s actual deal? Why is he doing this?

Aside from the licensing issue, which I covered above (and which seems like a mostly flimsy premise to me), Matt’s got some other complaints with WP Engine. Some have validity, some seem completely made-up. Let’s walk through them.

Matt claims WP Engine is misrepresenting itself

Among Matt’s complaints: that WP Engine is “misrepresenting” itself as an entity that’s officially affiliated with and/or endorsed by WordPress itself. Matt’s repeatedly used as an example his own mom’s confusion; she apparently thought WP Engine was somehow affiliated with WordPress.com (I guess because they also use the word “WordPress,” and are maybe a vaguely similar shade of blue).

I’m sure it’s frustrating, having taken over half the internet and being worth hundreds of millions of dollars, only to find out your own mom still doesn’t really understand what you do, but: come on, bro.

First, tons of companies use “WP” in their names, and/or the names of their products. Why isn’t Matt going after them?

Second, as many people have already noted: Matt effectively runs both wordpress.com and wordpress.org, which are entirely separate entities that do two completely different things. You wanna tell me that’s clear, but somehow WP Engine and WordPress.com are too similar? Really?

Third, my kindergartner and every kid in his class could tell the difference between the WordPress W and WP Engine’s dumb logo. (WP Engine’s logo has always been a grid of weird, almost-square shapes that’s apparently meant to vaguely resemble an engine, but which makes no sense to pretty much anyone who’s ever seen it, far as I can tell. It’s a bad logo, in my professional opinion as a designer, even the slightly better version they just released recently. But I digress. Point is: it looks literally nothing like any WordPress logo. Also: it’s not the same color. I have color vision deficiency, and even I can tell that.)

Finally, for the whole two years I worked for Shopify, most of my family thought I was at Spotify. Now I’m at Deno, and nobody in my family has any clue what a JavaScript runtime is, and my dad basically thinks I work for Java.

Family members don’t always get tech. That’s not a sign that something is wrong, and it’s most certainly not a sign that any wrongdoing has been committed, let alone deliberately. (Which, I assume, probably wasn’t Matt’s mom’s point to begin with, but that didn’t stop him from running with it.)

Matt claims WP Engine is selling a “cheap knock-off” of WordPress

Matt also claims WP Engine is selling “something that they’ve chopped up, hacked, butchered to look like WordPress.” His reason for this wild claim? Because WP Engine disables revisions (a default feature of WordPress, albeit a pretty small one).

Literally, that’s it. One tiny feature. The whole thing’s been “hacked and butchered” because they just chose to modify one tiny detail.

Of all Matt’s spurious claims, this one might be the one that reeks the most of absolute made-up bullshit. WP Engine will just turn on revisions if you want them to, but that’s beside the point.

First, if I decide to build something with, say, Laravel, but decide there’s one feature I want to turn off, I’m not “hacking and butchering” Laravel. That’s obviously ridiculous.

Second, pretty much all hosts limit revisions in some way or another anyway, because they take up a ton of memory and most people don’t really need them that bad.

And third, it’s open-source software! You don’t get to tell people how they use it!

We could also get into the utter hypocrisy that many of WordPress.com’s plans do far, far, far more invasive modifications of WordPress core (you can’t even install themes and plugins, FFS!), but again, that’s all beside the point. It’s open-source. They can do that. Anyone can. It’s in the license. This claim is clearly total garbage.

Matt says WP Engine doesn’t give back enough

Matt’s other complaint—and I think this is what everything else really boils down to—is: WP Engine doesn’t give back enough to WordPress, in Matt’s estimation.

Matt showed some numbers onscreen at WCUS, comparing Automattic’s contributions to WP Engine’s. But I’m not going to repeat them because I’m certain they’re distorted. Besides, I’m not sure the two companies’ work can, or should, be considered directly comparable in the first place. They do different things in different ways, and there’s no law or license mandating either of them do anything to begin with.

Regardless, Matt seems irked that WP Engine isn’t abiding by the “Five for the Future” program, outlined on WordPress.org. Five for the Future asks that if you benefit from WordPress, you give back 5% of your time directly to that open-source project, which I think pretty much everyone can agree is a very noble and admirable aspiration that companies such as these involved should probably be doing.

But it’s not a requirement, or a policy, and enforcing it as such—acting unilaterally as the WordPress police, let alone so suddenly and violently—is extremely questionable and deeply troubling. (Not to mention a likely deterrent for people and organizations who might want to participate in the WordPress space.)

Matt’s claimed he/Automattic have been soliciting WP Engine for increased contributions for “years,” and that they’ve given “$0” to the WordPress foundation. To the best of my knowledge, neither of those claims has been substantiated, but I suppose they don’t really change this discussion much either way, because again: Matt’s taken it upon himself to act as the WP PD to enforce a law that isn’t even a law.

So that’s it; that’s what Matt’s mad about. There’s some substance there, and in a vacuum, I think he’d probably have a lot of people on his side.

But we’re not in a vacuum; there’s a lot of context here. So I’d like to talk about that next.

An aside on motivations and justifications

Having explored Matt’s complaints, I’d like to pause for a moment, because this is where the sides seems to diverge.

The relatively small number of people in the community who appear to remain on Matt’s side (which seems to be mostly made up of his own employees and some people with their own reasons for hating WP Engine) appear to be sticking with him because they agree with this core point, i.e.: WP Engine should be doing more—maybe much more—especially considering that they’re a company owned by private equity and making significant money off WordPress.

On its own, I think that claim seems perfectly fair. We could disagree about the details, or how much is too much or too little, but I don’t think it’s unreasonable to say a company the size and profitability of WPE probably owes quite a lot to the open-source software it’s built on (ethically, at least; likely not legally).

So it bears mentioning that WP Engine actually does do a pretty good deal for WordPress. You can cherry-pick specific ways it hasn’t contributed much, and you could certainly make a reasonable case they should be doing more. But to say they’ve given “$0” strikes me as pretty deliberately misleading.

WP Engine pays several staff members to contribute work hours to WordPress core (again, maybe the number should be greater than it is, but it’s definitely not zero), on top of the full-time maintenance of plugins, themes, and apps like Advanced Custom Fields, WP Migrate, WP GraphQL, Genesis, Local WP, and many others—all of which used by countless thousands of WordPress users every day.

This is to say nothing of WP Engine sponsoring of WordCamps, creating their own tutorials and educational material, their own events, and so on and so forth.

Point is: WP Engine does do a lot more than zero. You could argue those contributions are not “pure” (Matt does), and that they’re ultimately in service to WP Engine, and not the WordPress community.

But in fairness: sure, they’re all marketing tools in some form or another, but you don’t have to pay for any of them. They all get maintained, they all have tons of users both on and off WP Engine, and they all work no matter what host you choose. (I’m sure they’re all used on WordPress.com. I’d even use some of those things if I had to spin up a WordPress site tomorrow, even if I probably wouldn’t host on WP Engine, personally. I’d probably choose SpinupWP, myself, which is another company with “WP” in the name that Matt apparently doesn’t care about.)

Besides, Matt’s company does exactly the same thing with Jetpack, which charges $5–$50 per month, depending on tier, so…not sure where that moral high ground is supposed to be coming from. Is Automattic really gonna claim Jetpack’s paid features are purely for the altruistic benefit of the community? Why do they get a pass on paid features?

I think you could fairly, if crudely, paraphrase Matt’s argument as: “WP Engine is in it for the money, and we are in it for WordPress.”

That’s a really flimsy stance in my view, without even getting into whether we can, or should, have exactly the same expectations of both companies in the first place (which is at least questionable; Automattic has their hands in a lot more things than WP Engine does, including Tumblr, PocketCasts, Longreads, and many others things that may or may not be related to WordPress, along with at least two hosting companies).

Still, once more: there’s probably some validity there. WP Engine is a big company that makes lots of money, and it probably can and should do more.

Matt could’ve made that point. I think most people would’ve agreed with him, if he had gone about it properly. We’d probably be lining up with him. There was a way to rally the community around this.

If Matt Mullenweg had done this the right way.

But Matt, being Matt, didn’t make that point in a good way.

(Sorry, this post is already too long without me going into all the times in the past he’s stirred up drama and just generally been a toxic jerk to undeserving people in the WordPress community. But if you’re not aware: it’s become increasingly common. He was even adding public snarky comments on WP Engine employees’ posts, ones who had given decades of their life to the project, as recently as yesterday.)

Matt tried extortion, and threats, and petty, childish tantrums, and when none of that worked, he fully exercised his unmatched and unchecked powers in an inconscionable way, in order to extract millions of dollars from WP Engine to put in his own for-profit competitor’s bank account.

But I’m getting ahead of myself.

So that’s the core of this whole thing; Matt thinks private equity is ruining everything and taking too much without giving enough back. It’s an easy home run of a point to make in this economy. Pretty much nobody disagrees with that.

Maybe he thought he’d come off like Robin Hood in this whole deal. I don’t know. But if there was a way to tactfully and gracefully thread that needle, it wasn’t the rampaging hippopotamus approach Matt took.

The split in the community seems to lie in whether that core point justifies Matt’s actions.

It seems to me that most people agree it does not; that Matt’s committed too many flagrant fouls of his own for the original infraction to matter.

Matt had a problem with the landlords, so he carpet bombed the neighborhood. He didn’t like Alderaan’s leaders, and so he fired the Death Star. And now it doesn’t really matter what his original point was; he’s made himself the bad guy.

Anyway, back to the timeline. (Note: I may have the chronology slightly mixed up here on a few of the points, but I don’t think it should really matter.)

The WordCamp US fallout and Matt’s abuse of power

At some point in this chaos (during his keynote at WCUS, or shortly after), Matt used his sway over every branch of power in the WordPress government to write a blog post called ”WP Engine is not WordPress,” (which isn’t something anybody seems to have been confused about, except of course Matt’s mom).

That post, crucially, went up on WordPress.org, which on its own seems questionable. WordPress.org is ostensibly the website for the nonprofit foundation; it’s supposed to exist to prevent any one for-profit company from having too much power over the WordPress ecosystem. It’s supposed to be agnostic.

Not only was that boundary ignored, but since the post was published as WordPress news, it was then syndicated to each and every WordPress admin dashboard in the world.

Forget for a second whether you agree with Matt or not; we’re getting into some of the worst of the conflicts of interest and abuses of power here.

This type of maneuver, plainly, is anti-competitive. It’s a flagrant exploitation of Matt’s many roles and the wild control he has over many branches of WordPress, many with conflicting priorities.

It’s bullying, really; WP Engine doesn’t have any tools to strike back like that. It can’t. (Maybe it wouldn’t, since to date, WP Engine appears to be the company with grown-ups in the room, who know to behave as though their actions will be examined in a courtroom one day.)

This would be like Meta one day deciding it didn’t like how a competitor was using React, and serving every single Facebook user a story on their home feed, brutally disparaging that competitor. It’s clearly a dramatic overreach.

I think Matt thought WP Engine had no retaliation. I think he was counting on this maneuver being yet another push towards their eventual acquiescence. But I guess it doesn’t matter; that’s just my speculation.

In any case, Matt wasn’t done. Matt went on flexing (read: abusing) his power by updating the WordPress trademark policy to retroactively disincentivize the use of the term “WP” in titles of products and companies. (Here’s the source on that change.)

You know why you constantly get notifications saying “we’ve updated our terms”? Because you legally have to do that. To just change the terms without letting people know is shady at best, and actively malicious at worst.

Well, Matt just went in and changed the terms.

Altering the WordPress trademark policy is yet another abuse that should make any remotely impartial observer shudder. Why would anyone want to use a software with an oligarch dictating the terms, and changing them on a whim, with no warning?

It’s around this point in the story Matt is really losing the plot. His whole complaint with WP Engine is that they’re not helping WordPress enough.

But yet…he’s burning WordPress to the ground to make that point.

WP Engine’s reaction

Following all this, WP Engine—quite understandably—doesn’t really care for all of their users seeing that negative messaging in their wp-admin. So, WP Engine finds a way to block the news feed on WP Engine sites.

That would be questionable in a vacuum, to be sure. But we’re steeped in context at this point. (A lot of users either turn it off or ignore it on their own anyway, for what it’s worth.)

Following WordCamp US, WP Engine also sent a cease-and-desist to Automattic. It’s pretty damning, and does a good job laying out all the points I tried to cover above. (In short: Matt tried to extort money from WP Engine for spurious licensing claims, and used disinformation, or at least heavily slanted data, to do it.)

One of the biggest revelations here is: Matt wanted the money he was trying to get from WP Engine to go to Automattic, which, again, is Matt’s for-profit company.

There are some pretty obvious conflicts of interest here. First and foremost, Automattic (or WordPress.com, at least) is a direct competitor of WP Engine’s.

Second, while Automattic does apparently own the WooCommerce copyright, it does not own the WordPress copyright. That is owned by the WordPress Foundation.

But it gets even murkier from there, as the Foundation is maybe (or maybe not) WordPress.org? And either way, the Foundation is apparently three people, and Matt Mullenweg is not only one of them, he appears to be the only active one!

Of the other two board members, one is a blogger whose company Matt bought out, and who apparently is no longer in the industry. The other is apparently a Partner and Managing Director at—surprise!—a private equity firm (not to mention a twice-failed Republican politician).

Wait…isn’t private equity bad? I guess not if it’s on Matt’s side. (For the record, Matt and his companies are tied up in private equity in other, more substantial ways than this, but that’s not worth getting into. It’s all pretty hypocritical.)

It appears neither of the other two Foundation board members is active, and therefore, Matt is essentially, behind the curtains, the King, Prime Minister, and Pope when it comes to WordPress.

Nobody holds any ability to check his power or challenge him. (That’s very relevant to what happens next.)

Also: Matt apparently kinda sorta owns WordPress.org, too. So he has a dizzying interweaving of conflicts of interest and power abuses here. (Source for all that about the foundation here.)

Let’s not leave unspoken the irony that the guy who basically is WordPress.com, and WordPress.org, and the WordPress Foundation, wants you to think the name “WP Engine” is confusing.

Anyway. Automattic responded by sending its own cease-and-desist to WP Engine, claiming mainly that WP Engine is deliberately confusing people, and that it owes licensing to…someone. Automattic, I guess, though the lines are so blurry it’s clear the separations between WordPress entities were only ever little more than a smokescreen.

I should mention: most people believe WordPress.com and WordPress.org/the Foundation are two (three!?) separate entities. I sure did, before this week. I thought the two had separated many years ago, with the express intent of preventing any one for-profit company from abusing the WordPress name.

I guess they technically are. But when one person apparently enjoys unchecked control over all of them…

[Guitar begins strumming with Alanis Morissette vocalizing]

Matt melts down

Two really weird things happened on Wednesday.

First, out of nowhere, Matt decides to publish a post on his personal blog outlining his charitable donations. He really frames it as though he’s being victimized and bullied into revealing this information, and I suppose some people were probably (reasonably) asking how much he gives, since he spent the whole week blowing up half the internet over how much WP Engine gives.

In the post, he also spends a lot more time defending himself against claims of being a “mafia boss” than most people who aren’t mafia bosses or acting like mafia bosses ever feel the need to do.

Weird move all around. Especially since the implication seems to be…what? “I’m a good guy so I can’t do bad things”?

I tried my best to look up Matt’s net worth and work out what percentage he’s giving, and by the best figures I could find, we’re likely at or below 5% here. (He’s said to be worth around $400 million, although that figure appears to be a little outdated—especially since he may or may not have sold a shitload of user data to AI companies earlier this year.)

Which, fine, that’s still millions of dollars going to charity, and that’s objectively a good thing.

But also: if my wife and I gave that percentage of our income, it wouldn’t even be enough money to get a tax deduction for it. So it’s worth mentioning that just for scale. Contextually, Matt’s donating at below the standard deduction level for somebody of his net worth. (And, most likely, enjoying significant tax benefits for it.)

Anyway, no matter which way you look at it, that’s all weird, but it doesn’t even really matter in the case of this larger discussion. It has major “oh yeah? Well would a bad guy do THIS?” energy.

You know…the sort of thing actual good guys don’t usually have to do.

Almost like Matt was trying to distract from something…

Matt goes nuclear

The next move, and most recent development in this story, is still shocking to me. I think it should be shocking, and deeply disturbing, to any observer.

WordPress.org banned WP Engine sites from accessing the plugin repository.

No more doing anything with plugins via the WordPress admin area. No installing, no updating. Not if you’re on WP Engine/Flywheel.

There are many layers to this.

First: again, this is the .org arm of WordPress enforcing this brutal new edict. The Organization, or Foundation, or whatever, is not supposed to be controlled solely by an oligarch who can bend it to their own will, to directly benefit their own interests. It’s supposed to be agnostic.

WordPress.org’s entire reason for existence, as I understood it (and I think as it was pitched to a lot of people), was explicitly to prevent things like this from happening.

Second: not being able to update plugins is a massive deal. You could very well be exposing your site to security vulnerabilities if plugins don’t update (to say nothing of bugs). There are nonprofits, charities, government agencies, and public services that host on WP Engine, on top of countless businesses. All of those are just being thrown under the bus to serve one man’s whims.

(Yes, it’s possible to manually update plugins, but nobody’s gonna do that. Certainly not the agencies and freelancers who oversee dozens or hundreds of sites on WP Engine.)

This is bombing civilians. This is putting innocent bystanders in harm’s way. This is firing the Death Star.

What Matt’s done is unforgivable, no matter how right he might have been at the beginning. To unleash harm on actual users of WordPress, indiscriminantly, solely over where they choose to host their sites, is an unconscionable, terroristic abuse of power.

(In the middle of all this, Pressable, a separate host Automattic owns, started offering promos to help people migrate to them from WP Engine. That alone should be majorly headline-grabbing, but Matt’s abuses up to this point are so egregious it barely even registers on the scale.)

You don’t hurt users because you’re beefing with their host.

You don’t bomb civilians because they live near a criminal, you don’t shoot at innocent bystanders because a terrorist is hiding behind them, and you don’t fire the Death Star because you disagree with Alderaan’s government.

It no longer matters what this was all about at that point, or whether you were originally right or not. You are irreversibly the bad guy now.

It’s also worth calling out a side effect of this move, which may or may not have been deliberate:

Matt’s actions have ensured his hosting companies are now the only WordPress hosts that can guarantee something like this will never happen to their users.

I mean, he can just flip the switch at any time. He can change the rules whenever he wants to. So what company is safe?

None. Except his.

I hope I don’t need to go into how anti-competitive that is, all on its own, or what an egregious abuse of power it is to have put himself and his company in that position by using WordPress.org to do it.

If Matt cares about WordPress, he should step down immediately. And if Matt won’t step down, he should be removed.

The weapons Matt Mullenweg has wielded unilaterally in this war shouldn’t even exist, let alone be controlled by one person.

I believe the ability to block an entire hosting provider from accessing the plugins repository is a power that nobody should have. If one could ever be justified in the use of such unthinkably drastic measures, this case most certainly isn’t extreme enough to do that.

Imagine if Microsoft got into a dispute with Apple, and decided to block npm for anyone using a Mac.

Imagine if Apple got into a dispute with Google, and blocked all text messages from Android phones.

Imagine if Google had a dispute with Amazon, and blocked all Amazon communications in Gmail. Or with Walmart, and prevented store locations from showing up on Google Maps.

And imagine if one person at any one of those companies had the power to make that decision, unilaterally and without challenge.

This is the scale of thing we’re talking about. This is the collateral damage Matt has unleashed on the WordPress community, and it’s not to anyone’s benefit except maybe Matt’s and his own companies’. (For now, anyway. We’ll see how it all shakes out; it seems pretty inevitable that a class action suit will follow and this all gets dragged into court.)

Virtually no WordPress users are happy about this, no matter how they felt about WP Engine. Certainly, none benefit.

No reasonable person could argue WordPress is in a better place today than it was a week ago, or is on a better path now than it was then.

It’s less secure, less trustworthy, more volatile, and overall just not something anybody is as excited about as they were a week ago. People who spent the majority of their lives working on this software are leaving it. Professionals are looking at new tools to sell their clients. Major sites are considering changing platforms, when they wouldn’t have before.

The neighborhood we all lived in just rocked, by a man who’s enjoyed unchecked power as the head of every branch of the current government, as it were. And he insists he’s doing the right thing by us for blowing up a whole bunch of our homes. (Forgive me, I know the metaphor is beleaguered by this point, but it seems apt.)

Matt’s clearly willing to burn it all down to score a pyrrhic victory, and that’s not a power he or anybody else should ever have over any community, let alone one this size.

Matt has to go.

I don’t expect him to be removed from Automattic leadership (although I think others in leadership absolutely should be considering whether that’s the right move). But in any case:

It’s clear that the blurry lines between WordPress.org and WordPress.com should be turned into unbreachable walls, with no one company on both sides, or able to exercise power over the Foundation and/or Organization.

I don’t care about Automattic giving 5% to WordPress anymore. I want it to give up Matt’s unchecked, unilateral power. Because it’s clearer than ever he can’t be trusted with it.