Filed: WP Engine Inc. v Automattic Inc. and Matthew Charles Mullenweg [pdf]

Original Article ↗ Hacker News Discussion ↗

Allegations and Legal Framing

  • Complaint lists interference with contracts, interference with economic relations, CFAA, attempted extortion, unfair competition, promissory estoppel, trademark non‑infringement, libel/slander, etc.
  • Lawyers in the thread argue the CFAA claim is weakly pleaded (missing required “loss” factor) and likely to be amended or dismissed.
  • Several see the “computer fraud” theory as really an extortion theory wrapped in CFAA language.
  • Many note the real legal center of gravity is declaratory judgment over trademarks and unfair competition.

Trademarks, Foundation, and Governance

  • Major focus on a 2010 transaction: WordPress trademarks were put into a nonprofit foundation while an exclusive, perpetual, royalty‑free license was given back to Automattic the same day.
  • Commenters say this appears to contradict public statements that the mark was “independent of any company,” and may raise nonprofit self‑dealing / tax‑filing issues.
  • Confusion and concern over blurred lines among WordPress.org, the Foundation, Automattic, and other entities personally controlled by the same individual.

Alleged Extortion and CEO Conduct

  • The complaint’s text messages are widely read as attempted extortion: threats of a public smear campaign and investor outreach if WP Engine doesn’t agree to an 8% “franchise‑like” fee and other terms.
  • Many find the conduct “unhinged” and reputationally catastrophic, especially combined with public livestreams and active commenting during pending litigation.
  • Multiple lawyers urge that continuing to talk publicly is strategically disastrous and will be used in discovery.

Impact on Ecosystem and Business Risk

  • Cutting off WP Engine customers (≈1.5M sites) from wordpress.org plugin/theme updates without notice is seen as a severe breach of trust and security risk for third parties.
  • Enterprise engineers and agencies in the thread say they are dropping WordPress from consideration due to governance and stability concerns.
  • Others argue this will deter new companies from building on WordPress for fear of retroactive “taxes” or retaliation.

Views on WP Engine

  • Some portray WP Engine as a “taker”: making hundreds of millions with minimal core contributions, disabling core features like revisions, and allegedly misusing Stripe affiliate attribution.
  • Others report good experiences with WP Engine hosting, or call them expensive and aggressive but still preferable to WordPress’ current leadership.
  • There is agreement that both sides will burn large sums on lawyers; some frame WP Engine’s suit as defense against a “bully.”

GPL, Forking, and Trademarks

  • Significant debate over a term‑sheet clause requiring WP Engine to “cease and desist from forking or modifying” Automattic/WooCommerce software.
  • Some argue:
    • Attempting to contractually restrict GPL forking rights may itself violate the GPL and terminate Automattic’s own license.
    • There’s tension between using trademarks to indirectly constrain GPL freedoms and the spirit of free software.
  • Others respond that trademark licenses can legitimately carry behavioral conditions, as long as code‑forking minus marks remains possible.

Community Sentiment and Future of WordPress

  • Many long‑time WordPress users and contributors say this episode confirms longstanding worries about concentration of power and conflicts of interest.
  • Some still credit Automattic for massive historical contributions and view the fight as “maker vs taker,” but believe execution (especially “nuclear” measures) has badly backfired.
  • Overall tone: deep concern that regardless of legal outcome, enthusiasm for WordPress and confidence in its governance have been seriously damaged.