AI summary by TwinMind
The Wordpress drama keeps getting worse
Theo - t3․gg
12m 47s
Background of WordPress-WP Engine Conflict
- Matt Mullenweg (CEO wordpress.com, WordPress creator, Automattic) upset with WP Engine hosting company
- WP Engine acquired by private equity firm Silver Lake, pushing for profitability
- WP Engine contributes: ACF plugin, WP GraphQL funding, WordCamp sponsorships
- Matt demands 8% royalty fee from WP engine's revenue - considered absurd by community
Initial Escalation Actions
- Matt restricts WP Engine user access to wordpress.org (plugins/updates system)
- Destroys security and update paths for popular WordPress provider
- Hurts WordPress users and community out of spite
- Community sentiment towards Matt plummets rapidly
- Matt threatens to make "WP Engine customers hurt"
- Makes WP Engine "worst possible platform" intentionally
Legal Escalation
- WP Engine files lawsuit against Matt Mullenweg and Automattic
- Lawsuit includes: Matt threatening WP Engine CEO, pretending to do interview then threatening board contact, borderline extortion behavior
- Second legal document published by WP Engine
WordPress.org Login Blocker Implementation
- Matt adds checkbox requiring users confirm "not affiliated with WP engine in any way financially or otherwise" to access wordpress.org
- Blocks WP Engine employees (including ACF plugin developers) from updating their own plugins
- Video creator advised Matt against this action day before implementation
- Predicted massive negative sentiment - proved entirely correct
- 20+ years good reputation "burned in days"
Advanced Custom Fields (ACF) Plugin Takeover
- WordPress.org announces security issues with ACF plugin
- Unprecedented action: WordPress.org forcibly takes over ACF plugin without creator consent
- Forks plugin with no actual changes, republishes under same slug as "Secure Custom Fields"
- All existing ACF users automatically updated to WordPress.org fork instead of original
- Never happened before in 21-year WordPress history - plugin under active development taken from creator
- Described as "absolutely unprecedented in open-source software history"
Community and Industry Response
- Ex-Automattic employee (5 years): "ashamed I ever worked there", would take severance offer 100%
- Internal Slack message about fork gets 161 downvotes, clown emoji reactions result in bans
- DHH (Ruby on Rails): warns against "Mad King" behavior, calls it "totally crazy"
- Compares to hypothetical npm taking over Express package or RubyGems expropriating official gems
- Steve (JavaScript community): initially supported WordPress, now definitively against
- Universal agreement this was unprofessional, community-destroying behavior
Dangerous Precedent for Open Source
- Could set precedent for other package managers (npm, RubyGems) to take similar hostile actions
- Threatens entire open-source ecosystem if normalized
- Platform operators could expropriate any popular package and lock out original teams
- "Uncharted and dangerous territory for open source"
Matt's Justification Attempts
- Claims "team running the account" - video creator calls this excuse invalid since Matt is boss
- Defends takeover claiming plugin was "abandoned" (false - actively maintained)
- Pattern: Matt overreacts → creates bad scenario → overreacts again claiming forced by circumstances
- Continues cycle of self-created problems and escalating responses
Final Warning/Ultimatum
- Video creator offers "last chance" to Matt
- Demands: formal apology, stop all actions, wait it out
- Warns any further action beyond apology will hurt 20+ year community
- Creator declares "I'm done" if Matt continues destructive path
- Community largely not giving Matt any more chances
