/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

WordPress.org adds a checkbox to confirm users aren't “affiliated with WP Engine in any way, financially or otherwise” before they log in or register an account

WordPress.org users are now required to agree that they are not affiliated with website hosting platform WP Engine before logging in.

404 Media Samantha Cole

Context & Ripple Effects

The account requirement extends a dispute that had already cut WP Engine off from free WordPress.org access, shifting the conflict from service access toward participation in the project’s own infrastructure. The earlier access cutoff made WP Engine’s customers and support channels a central point of friction.

It also lands after Mullenweg described WordPress.org as personally owned, while a proposed trademark arrangement reportedly sought a share of WP Engine revenue. That ownership assertion sharpened concerns that WordPress.org, the Foundation and Automattic were not cleanly separated in the dispute.

First-order effects

  • WP Engine-affiliated people who want to log in or create a WordPress.org account must now make an affirmation they cannot truthfully provide, creating an immediate participation barrier.
  • WordPress.org turns account access into an affiliation screen, broadening the practical impact of its earlier restriction on WP Engine access.

Second-order effects

  • The screen may strengthen WP Engine’s argument for court intervention over blocked WordPress.org access by adding an account-level restriction to the dispute over repository access.
  • Plugin developers, hosts and contributors tied to WP Engine face added uncertainty over whether their relationship with the company affects access to shared project infrastructure.

Third-order effects

  • If this approach persists, control of open-source project infrastructure can become a more direct bargaining tool in commercial and trademark conflicts, even when the affected users are not the company in dispute.
  • The episode increases pressure for clearer governance boundaries between a project’s public-facing infrastructure, its trademark authority and commercial participants; the reported proposed trademark-revenue terms make those boundaries especially consequential.

The trend: This is one data point in the broader trend of platform gatekeepers using identity and access controls to extend commercial disputes into the communities built around shared infrastructure.

Discussion

  • @allyngibson Allyn Gibson on x
    Twenty years to build WordPress' reputation. Two weeks to burn that reputation to the ground. https://www.404media.co/...
  • @josephfcox Joseph Cox on x
    New: the WordPress community “is in chaos.” https://wordpress.org/ now requires users to agree they are not affiliated with the hosting platform WP Engine before logging in. “WordPress community is in chaos. People don't know where they stand legally” https://www.404media.co/...
  • @vinnysgreen Vinny Green on x
    “...Whatever Matt's end goal is, his ‘tactics,’ especially this legally and ethically ambiguous checkbox, are causing a lot of confusion and mental anguish to people around the world.” https://www.404media.co/...
  • @samleecole Samantha Cole on x
    Automattic CEO Matt Mullenweg added a dubious checkbox to the WordPress org login today, dragging the open-source community into the middle of a very messy beef https://www.404media.co/...
  • @mor10 Morten Rand-Hendriksen on x
    People are asking me what the 🤬 is going on with WordPress. Here's a decent and up-to-date primer from @samleecole on @404mediaco (hosted on @ghost). Just to be absolutely clear, I'm not the “anonymous source” here. https://www.404media.co/...
  • @photomatt Matt Mullenweg on x
    @dhh I'm a huge believer in open source and the GPL and I've never modified any projects I'm involved with in 21 years to have a more restrictive license.
  • @blackmagikcodes Jeremy Nusser on x
    They went to retain WordPress' shine of open source, but also be able to extract their pound of flesh from any competitor that might appear, whenever they see fit. Screw that.
  • @dhh @dhh on x
    @photomatt I'd love to see that spirit prevail in this dispute. Accepting the lack of patches as a valid option under the license terms. We don't have to capture every potential contributor to prosper. The GPL is restrictive enough without the shadow terms on top.
  • @sherieffyi @sherieffyi on x
    “Open Source” is becoming meaningless as a term when the hustlers try to use it as a marketing / lead gen funnel
  • @dan0sz Daan van den Bergh on x
    Best take I've read so far on #wpdrama https://world.hey.com/...
  • @hunvreus Ronan Berder on x
    Hopefully more high profile OSS contributors speak up. @photomatt's handling of his feud with WP Engine is a net negative for Open Source.
  • @dhh @dhh on x
    “That's the deal. That's open source. I give you a gift of code, you accept the terms of the license. There cannot be a second set of shadow obligations that might suddenly apply, if you strike it rich using the software. Then the license is meaningless.” https://world.hey.com/..…
  • @technerdteitzel Chris Teitzel on x
    If Matt won't listen to the WordPress community, hopefully he can listen to a peer who also started a massive and successful open source project. This has implications across the fabric of technology and open source.
  • @lemire Daniel Lemire on x
    Open source software represents a vibrant, global community where code is not just written, but shared, scrutinized, and improved upon by an extensive network of developers worldwide. Open source isn't just about free code; it's about building communities where ideas flourish.
  • @photomatt Matt Mullenweg on x
    @dhh Thank you for writing about this! I'm sorry if our messaging made you think this about the GPL — I have no issue with their use of GPL code. It's specifically about their misuse of the “WordPress” and “WooCommerce” trademarks. Happy to hop on a call and explain more! Huge fa…
  • @shortformernie @shortformernie on x
    This is the argument that should win. That DHH is making it is likely to rub some folks the wrong way, but ... this is the argument that should win.
  • @thdxr Dax on x
    these kinds of things have impacts - big company legal teams are quite annoying and hyper-sensitive they already scrutinize everything and create lists of “risks” - we don't need to be giving them more ammo so they can tell people they can't use OSS