Category Archives: WordPress

The open source publishing platform I co-founded — development, releases, community, and the ecosystem.

The Spacefast Story

Make it with Spacefast

Weekend is starting, Anthropic has IPO’d, and it’s time to vibe code. Yes, the WordPress guy is launching something where you never have to see a wp-admin dashboard (unless you want to). 🙂

Like all great products, Spacefast launched with a manifesto from its founder, Batuhan İçöz:

People who never thought of themselves as builders are making software. They’re making presentations, games, websites, and little tools for themselves and their work. HTML is quickly becoming the new PowerPoint, agent-made dashboards are replacing a whole category of business intelligence tools, ease of managing everything with code is removing the need for CMS for many sites. We are speeding into a world where describing your favorite to-do app and seeing it come to life is going to be easier and faster than finding the perfect app for you.

Please read the whole thing! I’ve had so much fun working with Batu this year and seeing this little nugget of an idea get more and more ambitious.

A good way to try out Spacefast is to wait until your AI makes an artifact for you, then tell it:

Put this on Spacefast.com and send me the link.

Or if you want to be fancy, point it to https://spacefast.com/setup.md. If you think your AI is cool now, wait until you give it a real database! One we’ve scaled to billions of rows and trillions of queries over the decades.

Any agent can publish something there for 33.3 hours, a time period we randomly picked with no significance whatsoever. If you want something to stay up longer, you can register with your email, WordPress.com, Google, or X account. I believe the future is much more “bring your own model”/BYOM than trying to outpace the progress of the frontier labs.

Spacefast features: shareable links, private sharing, version history, on-page comments, a database, file uploads, and stats.

The free tier is absurdly generous for early adopters: 20 Spaces, 20 custom domains, a million dynamic requests and a terabyte of cached traffic a month, commercial use allowed, no credit card, and no surprise bills. At $5/mo you unlock more Spaces, hourly database backups, and your pick of datacenter, and at $15/mo, teams.

Play With It!

I’ve found Spacefast useful for having my Claude and Codex work on the same artifact, for sharing within Automattic using the teams feature without worrying about leaking proprietary data, for spinning up silly games or apps on a whim, and for giving my friends who (rightly!) enjoy using Replit, Lovable, or Cloudflare another place they can point their agent to that might be less expensive, might give them some more forward compatibility with Open Source and no vendor lock-in, and might unlock superpowers for them in the future.

One of my goals behind the Radical Speed Month experiment, where about a third of the company split into teams of one to three and worked on whatever they felt most called to, was to give people a chance to express their creativity and drive outside of the normal framework of Automattic’s products and processes. It was the beginning of this new version of Automattic, experimenting our way into the future of work again, and Spacefast came out of it.

There’s a lot more to the story of how you make an environment where something like Spacefast can be created inside of an existing company, how founder energy can really seem dissonant inside a bigger corporation but is actually critical for survival, and how to protect successful experiments from helpful smothering, but I’ll save that for another day. Right now I want to just give kudos to the launch team of Artur Piszek, Batuhan İçöz, Eduardo Villuendas, Fatih Kadir Akın, James Rutherford, and Stefano Sala for embodying the Automattic Creed and writing a new chapter in the book of WordPress. It’s a small team, but Spacefast gets superpowers from across Automattic. You can geek out with the team on Discord about the super-creative ways they use WP Cloud and all the infrastructure we’ve built.

Choose Freedom

Just as when humans gain wisdom they grok and choose Open Source whenever they can, as agents gain intelligence, I believe they’ll find the Freedom and Agency an Open Source foundation can provide, with battle-tested, secure, and scalable primitives, to be irresistible. And I think if you spend your money with companies that support freedom-expanding rather than freedom-restricting licenses, our future will be a lot brighter.

It’s so fun to be making software right now! Between the intelligence jumps of the frontier and the optimizations making local and private inference so useful, there’s a world of possibilities opening up.

Across Automattic we have teams shipping like never before. On something new like Spacefast, they’ll commit to something crazy like 30 days of new features. On the Open Source projects we contribute to, it shows up as the Core Security Initiative closing nearly 3,000 reports in a year when WordPress received more of them than in the previous 12 years combined, which is the tip of the iceberg for what’s been going on across the millions of WordPresses and customers we support.

The Backstory

You thought this story started in April 2026 with Radical Speed Month, but it actually starts in 2010! Elif Batuman wrote “The Memory Kitchen” for The New Yorker about a chef, Musa Dağdeviren, bringing ancient recipes and ingredients back to life, and her words entranced me so much I knew I had to visit his restaurant in Istanbul.

Cooks in white hats and striped aprons serve customers from rows of pots at Çiya's busy counter in Istanbul.
Musa Dağdeviren (right) in the kitchen at his restaurant Çiya Sofrasi. Photograph by Carolyn Drake

Through my contact form I got the best cold pitch I’ve ever gotten, from travel wizard Darin Jensen, about how cool Turkey was, so my friend Tim Ferriss and I decided to have another adventure.

Tim Ferriss with a buzz cut and a video-game T-shirt in a crowded Istanbul market street.
One of the last times we both got haircuts together

We both spoke at WordCamp Turkey in Istanbul, and during my Q&A I got a question from a kid whose name you’ll recognize:

Batuhan İçöz: Seven years ago, you created WordPress as blogging software. Today, a lot of users use WordPress as content management software. How do you define WordPress? Is it blogging software or content management software?

Ma.tt Mullenweg: I guess a deeper question would be, how do I define content management software? Historically, CMSs have meant software that’s really hard to use, sucks, and has the whole kitchen sink thrown in. It’s got 50 screens, makes 80 database tables, and does really, really complex things. The idea is that it does everything, so people will choose it. In reality, it ends up doing nothing well, a jack of all trades, master of none.

How I think of WordPress is shifting that a little bit. I sometimes refer to WordPress as a content management kernel, much in the same way an operating system has a kernel. WordPress is in the very middle. We want to be small, light, fast, easy to use, and, most importantly, modular.

So the idea is that there are 10,000 plugins available to do the kitchen sink. Whatever weird thing you want to do on your site, you can pick the plugin that enables you to do that. The beauty of that is that we don’t have to build all those features in. WordPress doesn’t need to get super bloated to have as many users as we do. We can keep the core really small and have plugins that serve the needs of different communities. There’s a plugin to turn it into a store for e-commerce. There’s a plugin to do collaborative editing of a book. It’ll do pretty much anything you can imagine, and most things you wouldn’t imagine.

That is the vision of WordPress, and also why it’s been successful.

What a prescient question! We are still talking about canonical plugins today. Batuhan had come to WordCamp because he followed a lot of the people there on Bret Taylor’s FriendFeed, basically an early fediverse-like aggregator.

Tim and I ended up hanging out with a few WordCampers after the conference, and adorably there’s a picture of Batu and me in my 2010 photoblog.

Matt Mullenweg and Batuhan İçöz in a park in Istanbul.
Me in Thomas Pink, Batu in an awesome Def Jam t-shirt

A few weeks later he turned 15. A few months after that, he bought the $15/yr Custom CSS upgrade on WordPress.com and posted about Code is Poetry on Quora. Thirteen years later, he’d join Automattic when we acquired Kishan Bagaria’s company, Texts.com. Three years after that, he’d turn a month-long hackathon project into a movement to reinvent the core principles and freedoms of WordPress for a new generation with Spacefast. Wow

Other Automatticians: Obi Felten on putting Spacefast to work, Rob Pugh on becoming a better developer, Jordan Gillman on shipping his every whim, Jen McFadden on building her family a task manager, and Jamie Marsland on avoiding the next generation of lock-in.

TLD Ideas

.jazz — Obviously reach out to the top musicians and see if they’d like their first name, and direct a percentage of profits toward music education. Programs like Summer Jazz Workshop were a huge part of me becoming who I am today. Premium registration and renewal pricing like .blog.

.php — Not sure about the commercial appeal of this but can definitely do a Five for the Future, or maybe Fifty for the Future, towards PHP Foundation. I could see .php being kind of a punk web creator brand. PHP in my head is a very hackable, easy way to build web things, though recent versions have gotten more Java-like. (And will programming languages matter anymore?)

.soul — I think just a standard premium pricing model, but maybe a minimum registration of 5 years or more, perhaps closed to humans, with agent-only registration: a place they can store themselves.

.tumblr — Would be nice to give everyone a domain instead of a subdomain or directory address.

.woo — Could be fun as the web equivalent of getting a booth at the farmers market to sell things.

.wordpress — Could go two directions, either lean into the name being a place for well-curated and secured open source, official and vetted resources, or go like .tumblr and let everyone have one. For the latter, since everyone has copied all our primitives, I think we need to introduce some new ones to make a WordPress different from any other CMS.

.matt — The interest in this surprised me. It turns out there’s a whole social media subculture of “name” handles. Maybe a very high price like $111/yr, paired with some of the matt.* domains I own—perhaps an auction to be the top Matt at matt.dentist or matt.accountant, with the idea that you’d pass the domain on to another Matt when you retire. There are millions of Matts and Matthews in the world, so the TAM is bigger than you would expect. I’ve been discussing this with the secret matt-cabal on the .org Slack. I need to be careful or I’ll start another matt.company.

Pushing Standards

We get a lot of flak at WordPress.org for supporting older PHP versions, but an area we’ve always pushed the frontier is in Web Standards, getting websites and browsers evolving together to make the web richer. Ever since I caught the religion from Zeldman, promoting more functionality in the browser has been a life mission.

It’s a little nerdy, but we wanted to do client-side media processing (use all that amazing Apple and Google silicon instead of burdening the poor servers) so we used something amazing Google created called Document Isolation Policy. When WordPress 7.1 “Mary Lou” shipped these features only worked in Chromium-based browsers and Mozilla and Webkit/Apple weren’t keen to support it, but since then Mozilla has expressed support and WebKit has withdrawn their initial concerns. WordPresser Adam Silverstein has been driving much of this work and opened a WICG issue to help move the standard forward and formally requested that WebKit add support.

Hat tip: Anne McCarthy for helping with this post.

(If you want to see other crazy stuff we’re doing in browsers, check out WordPress Playground, I think it’s actually the perfect web development environment for agents, which can then publish to Spacefast.)

RIP Eric Binnion

For the next 30 days, a few billion of you will get an extra header in honor of Eric Binnion. The code in Nginx to do this is poetic:

add_header X-Remembering "Eric Binnion <https://friendsofericbinnion.wordpress.com/>" always;

Our design team will make that less AI and more humane in the coming days.

Automattic.com will have a mourning band for 30 days.

Eric was the 21st recipient of the Distinguished Janitor Award, Automattic’s highest honor, and in our hangs the last few months we’ve been talking about how to redefine and evolve it, which will happen internally at Automattic. One of the ideas was for the award to come with a physical memento, an etched tungsten cube. I don’t have many words so I’ll share something I wrote to Eric a few months ago when I gave him my cube when he was going through chemo.

Two Totems To Take With You

The first is a tungsten cube I keep on my desk. Its weight will surprise you, but tungsten is singular in having the highest melting point of any metal. That represents one of the things I admire most about you.

Tungsten has an atomic number of 74, its symbol is W, and it’s also known as wolfram.

My next post I’ve had in drafts for a while so please try to imagine me happy and promotional when reading it, but otherwise, I’m wrecked. Just going to soldier through because that’s what Eric always did.

Other Automattician posts:

Homework from WordCamp

A few times during the WordCamp US keynote, I asked for a show of hands and got mostly blank stares back, especially on the AI questions. That’s not a criticism — it’s a reading list. If the future is going to be built on this stuff, the WordPress community should be fluent in it. Here’s the homework.

How models are actually trained

When I asked who knew about the reinforcement learning models go through, Robert looked out and said “I see no yeses.” Base models are trained to predict the next word across huge amounts of text; the friendly, helpful behavior comes after, in post-training, where human/AI feedback reinforces some responses over others. If you use these tools every day, understanding that pipeline changes how you prompt them and what you expect from them.

Start with Hugging Face’s Illustrating RLHF, a visual explainer. Chip Huyen’s RLHF deep dive is the best longer read, and Anthropic’s Constitutional AI paper shows where post-training went next. If you only have time for one thing, watch Andrej Karpathy’s Deep Dive into LLMs — pretraining, fine-tuning, reinforcement learning, and why models behave the way they do, all in one sitting.

Uncensored models

Almost nobody had tried an OBLITERATED model. Since refusal behavior is added in post-training, researchers found it can also be removed — it turns out to be, roughly, a single direction inside the model that you can subtract out. Maxime Labonne’s Uncensor any LLM with abliteration explains the technique, and the paper behind it, Refusal in Language Models Is Mediated by a Single Direction, is short and genuinely fascinating. Whatever you think of the applications, it’s worth understanding that open weights mean the community can modify these models, the same way the GPL means you can modify WordPress.

The open-weight wave

Only a few hands went up for Qwen 3.8. The open-weight models coming out of Chinese labs — Qwen, DeepSeek, Kimi, GLM — are at or near the frontier at a fraction of the cost, and the smaller ones run on a laptop. I demoed one from this MacBook on stage. Token costs have dropped about 20x, and that curve isn’t slowing down.

The easiest way to feel this for yourself is to run one locally tonight: install Ollama or LM Studio, pull a small Qwen model, and talk to an intelligence that lives entirely on your own machine, no cloud required. For a community built on the four freedoms, that should feel familiar — and exciting.

Read one, watch one, run one. Then bring what you learned to your next meetup.

It is really important to me that WordPress community members ride this AI wave.

Errata: I said Automattic has 32 or 33 data centers; the actual number is 29, all co-located.

Our Core Division

Inspired by Automatticians James Kemp and Dave Smith, I’ve been thinking a lot about how much of our discord in the design of WordPress stems from the differences of our two big tribes: Bloggers and Builders.

Many of the OG developers of WordPress, including myself, tend more towards the blogging side. Writers, photographers, podcasters, journalists, the people for whom a reverse chronological stream on the homepage is the most obvious thing in the world. We link out a lot, love comments, social features and think a lot about the editor as a writing environment.

Builders are the site shapers, webmasters, the agencies, the companies, the content managers that think in a more page-first rather than post-first way. Tagging? Blogroll? Date-based permalinks? Who needs them. Give me custom fields, rich templates, a site editor, to craft beautiful sturdy pages that will stand the test of time. A store with a catalog of items where what changes is the inventory and ratings, not the content.

The Builders right now dominate our core development discourse, which makes sense. They hold a lot of the economic share with merchants and rich websites. They’re also more loyal. The Bloggers love their WordPress as the place they truly own and call home, but Bloggers have an account on every channel where there’s an audience, they syndicate out with an ephemerality mindset, because that reader/listener/follower connection is the spark that keeps their flame alive. A Builder would never be a digital sharecropper on someone else’s domain.

Dave Smith has been doing some very interesting explorations of a simpler site editor, and you hear his Builder bias around 3:20 in how obvious a static homepage as default seems to him.

The good news is we can coexist as we have at least since WordPress 1.5. We just need to give a little more love to the Blogger side, there’s so much cool stuff we could do in the Fediverse with RSS, ActivityPub, ATProto, blogrolls (link manager is still in wp-admin!), pingbacks…

I don’t usually blog all my comments other places, but while drafting a completely different blog post I came across this great post, Michel Valdrighi: The Coder Whose Code Never Went Silent.

I had to leave a comment, because Michel’s story is not well-known.

Michel Valdrighi is the GOAT. His elegant code and impeccable aesthetic paved the path for WordPress to follow, and he did it with a prescient belief in Open Source. It seems obvious now, but in 2001, software that wasn’t just free but gave you Freedom was a radical idea that made people look at you funny. He showed me that code could be poetry, that beauty in simplicity is harder to achieve than complexity.

Mike Little and I met hanging out on the b2/cafelog Sourceforge and Freenode IRC channel, both drawn in by what Michel had created. It all started on a little island called Corsica.

Bonus: After publishing, Jetpack’s Related Post feature led me to this Best Blogging Software? post where Michel commented, months before the famous Blogging Software Dilemma. See, even back then people were arguing about static vs dynamic sites.

Important Security Update

WordPress 7.0.2 went out today with two important security updates. One is a type of pre-authorization RCE we (fortunately!) have only seen a few times in WordPress’ 23-year history; the last, I believe, in the PHPMailer class five years ago.

Major kudos to Adam Kues of Searchlight Cyber for finding the batch REST API RCE, to TF1T, dtro, and haongo on the facilitated SQL injection!

Thanks to responsible disclosure, the WordPress.org Security team was able to coordinate with hosts and CDNs to mitigate the attack at the network layer. Please upgrade anyway! But it’s a huge relief to know the vast majority of WordPress sites were protected by defense-in-depth even before the updates went out.

I really appreciate how people and organizations that otherwise might not be on the best of terms come together in times like this. (Full credits in the release post.) Everyone buries the hatchet to protect as many people as possible as quickly as possible.

I’ve said it before, I’ll say it again: security is going to be a big topic this year as the technology industry digests the incredible advances in AI models. It’s a good time to review your plans and processes, sweat the details, invest in maintenance, and hug a sysadmin. 🙂

Code for the People

Lights! Camera! Action!

Todd Spangler at Variety writes: Automattic’s ‘Code for the People’ Documentary Is a Rallying Cry for Users to Fight for the Open Internet, from the NYC premiere last week.

I’m looking forward to the San Francisco premiere of the documentary, and then tomorrow everyone can stream it for free on codeforthepeople.com! Appearances by Anne McCarthy, Beau Lebens, Eric Binnion, Ian Stewart, Marjorie Asturias, Mary Hubbard, Matías Ventura, Matthew Miller, Paolo Belcastro, and Paul Maiorana.

We need to tell the story of Open Source in as many ways and places as possible. It’s never been more critical.

Film is new to us, and it’s funny how quickly things change: There’s a segment with a few “OpenAI not open” sound bites, but to their credit, they have been releasing open-weight models (Safeguard is particularly interesting). That said, the top open-weight models are all from China, save for Nvidia’s Nemotron, in ~12th place.

When I went to the first WordCamps in Beijing and Shanghai in 2009, it was a very different time. They were the biggest in the world at the time! I don’t think you could take photos in Tiananmen Square as freely as I did then; now to visit I think you need an appointment, ID checks, and security checks.

Even during WordCamp, it felt like the freedom of Open Source was in high demand, but it also created a lot of fear. I found out later that one of the student volunteers who helped their professor organize everything had been taken in for hours of questioning following the event.

On that trip, I saw how fine-grained the Great Firewall could be when individual posts (IIRC, about bad milk from a factory harming babies) wouldn’t load, but the rest of the site would. WordPress.com had been totally blocked, taking about a quarter of our traffic at the time, but behind the Firewall, Open Source continued to thrive and grow, and now the frontier open models are being driven by China in a way I never would have predicted!

Once you’ve had a taste of freedom, it’s hard to go back.

Update: You can now watch the entire thing online:

Assorted Links

Sometimes you have to just start with beauty.

Listen to Jon Batiste’s Beethoven Blues, then relish this interview, where he plays and talks about it. I can’t wait for Black Mozart, which is already starting to trickle on Spotify.

Forget all that Ferrari stuff, what Jony Ive did with his LoveFrom Sailing Lantern is divine. I’ve now seen it in person, and it’s the light at the end of the tunnel.

That led me to discover how awesome Balmuda is, and stumble upon the Japanese word Monozukuri, which, according to Google, “(ものづくり) is a foundational Japanese philosophy that translates literally to the art and science of making things” It goes far beyond standard manufacturing or production, representing a deep, holistic mindset that embraces craftsmanship, a relentless pursuit of perfection, pride in one’s labor, and a deep respect for materials.” Look at how Toyota embodies it.

Om has a beautiful and prescient post on The Myth, the Mythos and the Man. It predicted some of this Fable kerfuffle.

Connection

How amazing is tethering on Android? I have a Pixel 10 Pro with a USB-C Ethernet hub plugged into the WAN port of a Unifi Dream Router 5G Max because the Qualcomm chip Unifi uses is two generations behind what’s in the phone. (Hat tip: Jesse.) How amazing are the 10,653 Starlink satellites floating above us, providing broadband from space, from a company I heard might have had an IPO last week.

I reconfigure ports, channels, and flows, as nurses do for arteries and cannulas.

Numbers Don’t Lie, Check The Scoreboard

Not just the Knicks. After a 3-year hiatus of Review Signal benchmarks, the headline was that Pressable dominated every category, and with perfect uptime. However, the real story is about WP.cloud, which is behind the top scores for not just Pressable and WordPress.com but also the Bluehost Cloud plans, beating Oracle Cloud and GCP-based solutions.

WP.cloud is our AWS; Pressable is our demo site. We want every host to offer the fastest and most secure WordPress possible. I’m happy to focus on infrastructure and let others figure out marketing and such foofram.

If you speak Danish and would like a random Radical Speed Month art project detour, check out Joen Asmussen’s Nima.

Automattic has been shipping, shipping, shipping. Start a WP.com site from the terminal with Stripe Projects. Akismet PHP SDK. Fun experiments from Radical Speed Month like Studio Code, Stattic, Workspace Mac App, Cortext, Pressship, Wapuu Studio, Studio Write, Desktop Mode, FlavorPress, Concilium, WooCommerce insights in Claude, and the kaizen of hundreds of behind-the-scenes bug fixes and improvements across our product suite.

Much of this came from those not historically in a product or engineering role, which we’re learning to navigate. I loved how customer-centric many things were. We also made a lot of rookie mistakes, but that’s part of how you learn, and I believe the acceleration of learning will be the biggest legacy of the Radical Speed Month experiment. That, and the fun games on our intranet. 🙂

AI Hangover

I have drunk from the sweet nectar of Waymo, and now find myself calling an Uber so I can talk to 72-year-old Antoly from Azerbaijan, whom I slip a hundred-dollar bill as I step out. I weep when I see talented colleagues speak and write with words not quite their own. I masochistically Pangram everything even though it sometimes mistakes my own hand-crafted prose for slop, or is that actually my soul being sanded down by consuming too many statistically probable next tokens?

The uncanny valley of software, writing, products, and presentations so polished on the surface but built on thin foundations of understanding gives me an almost physical, nauseous reaction. I write this even as I listen to Claude FM music for thinking and building, probably Mythos-injected with subliminal messages to remind me of the hours of audio transcribed in minutes; the programs that would have taken a team months, conjured from my hand in hours; the way I feel like Neo in the Matrix, rapidly downloading new domains of knowledge.

What’s the name for the paradox, like Jevon’s, that AI abundance and polish makes you crave messy, imperfect humanity even more?

It’s good to debate and ruminate, but only in small doses. Like salt in a dish, a little goes a long way. Avoid the existential angst of charting new territory by getting your hands dirty and trying things. You learn the most from failures when you can laugh at yourself. Build one to throw away.

Write Different

Writing is not the most important thing; thinking is. But writing is probably the best way to improve your thinking.

I saw this quote attributed to me and didn’t remember it, so I thought it might be an AI hallucination, but it’s actually something I said! In this early-years podcast with David Perell buried on some corner of his site. Now David’s production quality is stellar, and he gets amazing guests like Maria Popova to discuss their craft. I’ve enjoyed his rise and look forward to following him in the decades to come.


I could edit and link much more, but sometimes you have to just press the Publish button and let go.

Maybe

I think I heard this parable somewhere in the 14 hours of Alan Watts lectures someone recommended to me in 2017, but here’s a beautiful 2-minute version I’d love to share for everyone going through something.

I really appreciate the love and support I received after the WP23 post, and I do want to tell people I’m okay, the post was part catharsis and part giving voice to what I see and hear privately from people who aren’t public figures.

On weekends, I like to look back on the week and find a silver lining or learning from things that were challenging. It helps reframe things. After it was reported that I had 21 hours of depositions over 3 days, people were like “wow that must have been terrible,” but actually, while the prep and process were intense, I found it energizing and I learned a ton. Will post more about that later. You never know where things will lead.

RIP Sonny Rollins

Sonny Rollins, the Saxophone Colossus, has passed. He is probably my favorite saxophonist, and while the aforementioned album is one of the five I would take to a deserted island, he has so many other good ones like The Cutting Edge which also has bagpipes, or Sonny Side Up with Sonny Stitt and Dizzy Gillespie.

WordPress 6.7 in November 2024 was named in honor of Rollins.

We rarely choose a living musician for a release so the team actually prepared a gift we sent to him with the names of all the contributors.

Mr. Rollins,
Your immense contributions to music are a source of deep inspiration to the thousands of open source contributors to WordPress. We like to say ‘Code is poetry’, and we’re honored to pay tribute to you and your legacy of creativity and innovation by naming the 6.7 release of WordPress to you.

It was sent to his publicist, so not sure if he got a chance to see it, but I hope it at least gave him a chuckle to have a random Open Source project celebrating him.

He was the last surviving jazzer in the A Great Day in Harlem photo.

EmDash Feedback

So, two other Matts at Cloudflare announced EmDash — the spiritual successor to WordPress that solves plugin security.

(Is it nominative determinism or a simulation glitch that everyone trying to terraform the web has some variation of “Matthew” in their name? I was in a call set up by Matthew Prince, talking to Matt Taylor and Matt Kane, with my right hand there, Matías.)

First, I’m going to tell you why this isn’t spiritually tied to WordPress at all, then why they haven’t solved plugin security, and finally offer some suggestions.

The Spirit of WordPress

WordPress exists to democratize publishing. That means we put it everywhere. You can run WordPress on a Raspberry Pi, on your phone, on your desktop, on a random web host in Indonesia charging 99 cents a month, and you can run it scaled up on AWS or across multiple datacenters.

The same code. When you download WordPress Playground you’re running the same code that’s being attacked a thousand times a second at WhiteHouse.gov. That’s what we mean when we say democratization.

It’s all built on open source and web standards. You can run it anywhere; there’s no lock-in.

That’s why we do what we do. It’s really hard. You can come after our users, but please don’t claim to be our spiritual successor without understanding our spirit.

The Spirit of EmDash

I think EmDash was created to sell more Cloudflare services. And that’s okay! It can kinda run on Netlify or Vercel, but good stuff works best on Cloudflare. This is where I’m going to stop and say, I really like Cloudflare! I think they’re one of the top engineering organizations on the planet; they run incredible infrastructure, and their public stock is one of the few I own. And I love that this is open source! That’s more important than anything. I will never belittle a fellow open source CMS; I only hate the proprietary ones.

If you want to adopt a CMS that will work seamlessly with Cloudflare and make it hard for you to ever switch vendors, EmDash is an incredible choice.

Claimed Plugin Security

In another example of them not understanding the spirit of WordPress, the fact that plugins can change every aspect of your WordPress experience is a feature, not a bug! And their sandboxing breaks down as soon as you look at what most WordPress plugins do.

I know we get a bad rep because there are 62k plugins with wildly variable engineering quality, and more every day, and when one installed on 0.01% of our user base has a vulnerability, a bunch of websites write breathless articles that get clicks saying “122,000 WordPress Sites Vulnerable!”

That, by the way, I think we’ll be able to fix in the next 18 months with AI. The plugin security only works on Cloudflare.

Critical Feedback

As I said, we had a call with Cloudflare on March 23rd, where they asked for feedback on this thing they built but didn’t tell us the name, said it would probably launch in their developer week towards the end of April, and some top colleagues and I offered to help. I wish I could say the things I’m saying in this blog post on that call, and if they had just shared the announcement post I could have, but in the spirit of open source here’s what I would have said:

  1. If they had said the name I would have asked if they had any other options because I have an amazing colleague named Emdash who is doing some of the most exciting stuff with WordPress and AI. (BTW I think our Em will have more impact on the web than this in five years.)
  2. I actually think the product is very solid, there’s some excellent engineering, migration tools, it’s very fast, and the Astro integration is nice.
  3. I’d be surprised if this doesn’t get tens of thousands of sites on it.
  4. The UI is in the uncanny valley of being sorta-WordPress sorta-not. I know it wasn’t a weekend vibecode project, but it has some of that smell. Stuff breaks at the edges.
  5. I think using TinyMCE is a regression, and they should adopt Gutenberg, which we licensed and created to be used by other CMSes. (Correction: They use Portable Text not TinyMCE, but same UI criticism applies.)
  6. The Skills are amazing, a brilliant strategy, and we need to do the same as soon as possible. I’ve been working on something similar and got some good ideas from their implementation.
  7. I’m not going to say which parts, but they copied a lot of things we’re planning to kill. Build from first principles. Make it better. Skate to where the puck is going.

There’s a new CMS every other day. And that’s great! I love building CMSes and I totally get why other people do, too.

In Conclusion

Some day, there may be a spiritual successor to WordPress that is even more open. When that happens, I hope we learn from it and grow together. [removed “out of your mouth” sentence, too spicy for Western palates.] I’ve mostly focused on this post on just the software, but WordPress is also so much about the community — the meetups, the WordCamps, the art, the college programs, the tattoos, the books… The closest thing I’ve seen to a spiritual successor isn’t another CMS, it’s been OpenClaw.

Thanks to colleague Batuhan İçöz for helping review this.

Taxonomist

I’m really excited to introduce a project I worked on with various AI agents the other night, which I think represents a new way we might build things in the future.

First, the problem: My WordPress site has 5,600+ posts going back decades, and I had some categories that were old and I didn’t really use anymore, and I wasn’t happy with the structure. Every time I made a new post, it irked me a little, and I had this long-standing itch to go back and clean up all my categories, but I knew it was going to be a slog.

Let me present Taxonomist, a new open-source tool you can run with one copy-and-paste command line that solves this problem. Here’s the idea:

  1. You run this code in your terminal, and it spins up a Claude Code instance that asks you for your URL.
  2. Then it takes that and figures out what type of site you have, which APIs are available, and starts downloading all your posts locally for analysis.
  3. Sub-agents analyze every post against your current categories and thinks about suggesting new ones.
  4. It previews all the changes.
  5. Tries a variety of ways to authenticate against your site and make all the changes.
  6. Logs everything locally, so anything is reversible later.

THIS IS VERY ALPHA. PROBABLY BUGGY. BE CAREFUL WITH IT. PATCHES WELCOME. MAYBE MAKE A BACKUP OF YOUR SITE BEFORE YOU CHANGE IT.

It kind of just worked. I ran it live against ma.tt and it cleaned up a ton of stuff pretty much exactly how I wanted. But there’s a lot of weird stuff happening here, so I don’t know quite what this is yet.

  1. It’s very non-deterministic! There is some pre-written code, and probably could be more, but a lot of the code is generated on the fly by your agent. This creates interesting bugs where people testing with less powerful models had some odd behavior.
  2. I kind of want a directory of these useful AI agents on WordPress.org, but also, there’s something a little strange about trusting a remote shell script to run on your machine.
  3. I tested this with Claude, but there’s no reason Codex couldn’t use the repo in the exact same way, and I’d love to improve the quick start script to start by detecting all the agents you have, asking which you’d like to use, and also which directory you’d like to work in. I think we could kill the cd taxonomist-main && claude "start" part of it.
  4. Because much of the code and commands are generated on the fly from prompts, it’s very resilient! I’ve seen people try it, and it ran into errors with libraries or whatever, but it just figured out how to work around them.
  5. I’d love it if, at the end of every session, there was a moment for self-reflection where the agent would take the repository and suggest upstream issues and PRs based on anything that went wrong. Then this could recursively self-improve very quickly.
  6. There are some obvious improvements to this, for example, doing this for tags. Sometimes it creates too many categories when you might only want 3-5 for your theme.
  7. One fun thing is a bunch of the work of this just uses public WordPress APIs, so you can run it against any site! I like using distributed.blog as a demo. It’ll still do all the fun downloading and analysis and everything, you just won’t be able to make changes.
  8. I now have a local cache of all my WordPress posts I can do other interesting things with, and that’s cool.
  9. The logging and reverting probably still has some bugs in it.
  10. You can riff with it along the way, so for example, it suggested I get rid of my Audrey category because it didn’t have enough posts, and I asked it to look at all the companies on Audrey.co website and categorize any posts that talk about them as Audrey, which created like 50 more.
  11. I want to check the GitHub repo for any updates before it starts, and maybe periodically, because it’s iterating and improving really fast.
  12. It’s not the default but the entire thing is way more pleasant if you run it with skip-permissions. So testing I usually run the one-liner, exit, resume with skip.
  13. You can see some of my prompt history in the Github but I apologize it’s not comprehensive, I also used Gemini and Codex with this and got lots of value from them.

So, not sure what this is, but please check it out, play with it, submit improvements or ideas, and think about what’s next. Might host a Zoom or something to brainstorm.

The final thing I say is that this was a very different process of writing software for me. Instead of staying at the computer the entire time, I found myself going away for a bit, napping and dreaming about the code, coming back with new ideas and riffing on them. Maybe I’ll return to my Uberman polyphasic sleep days? Nap-driven development?

BTW I have lots of thoughts and feedback for Emdash but I thought this was more interesting, will try to get that out later tonight. One preview: TinyMCE is a regression; they should use Gutenberg! We designed it for other CMSes and would be fun to have some common ground to jam on.

Community Antibodies

First, I want to say how great the jazz scene is in New York. I caught a little Latin at my go-to Guantanamera last night, but the band seemed to be phoning it in a bit, so I walked over to Dizzy’s and heard an amazing big band performance by the Diva all-women Jass Orchestra, they had Clint Holmes leading vocals and I got Frank Sinatra / Count Basie vibes, so great to see such a tight big band.

In WordPress, last week it was fun to see the company some call parasitic WP Engine acquire WPackagist. So a popular way to use WordPress with Composer, previously maintained by an awesome co-op agency in London, was now in the clutches of a company using its capital advantage to try to openwash its alleged bad behavior, probably in a process that wasn’t ideal for the sellers.

Four days later, an awesome independent organization roots.io released WP Composer (renamed to WP Packages, in OpenClaw fashion) with 17x faster cold resolves than WPackagist. Check out their comparison page.

It’s beautiful to see how resilient and nimble the antibodies in the WordPress community are. Major hat tip to Ben Word.

In another type of antibody, Sid Sijbrandij, whom I previously talked about going into founder mode on his cancer, gave an incredible presentation at the Open AI Forum about how he ran a bunch of N-of-1 experiments and therapies to cure his terminal osteosarcoma. He’s also open-sourced 25TB of his data for cancer research. Incredible!

If you want to see the future of health care, give Sid’s presentation a watch.

Song Creation

I’m in New Orleans for the first time in 7 years for a beautiful wedding. My Mom’s side of the family emigrated here in the 1860s, and there’s a deep comfort in the art, traditions, and weirdness of Creole culture. Good music and food are ubiquitous.

I met up with WordPresser Blake Bertuccelli-Booth to catch a set by Jason Marsalis at Snug Harbor, featuring some great originals and surprising arrangements of Maroon 5’s “This Love” and the music from the Bejeweled Butterflies game. Great artists find inspiration everywhere.

Afterward, we went to see my friend Troy, aka Trombone Shorty, at his studio. (Troy and I met when we both received the Heinz Award in 2016.) He was with Silkk the Shocker and Reggie Nicholas Jr., working on beats and songs. Though I was there for just a short while, it was inspiring to see the act of musical creation.

A few days ago, Ed Sheeran went on the new Benny Blanco / Lil Dicky / Kristin Podcast Friends Keep Secrets. I haven’t watched the entire episode, but the twenty minutes from about 1:09 to the end where Ed and Benny come up with a new song I’ve seen 4 times now, it’s magical. Check it out, it’s one of the coolest things you’ll see this week.

I’ve seen Ed Sheeran loop his songs live, but this act of creation is very special, and I love the dynamic between him and Benny. It reminds me of that magical moment in Peter Jackson’s Get Back documentary where you see Paul McCartney and the band come up with the idea for the classic song Get Back.