Wordpress.org Login: "I am not affiliated with WP Engine in any way"

Original Article ↗ Hacker News Discussion ↗

Login Checkbox and Community Bans

  • WordPress.org’s login now requires users to affirm they are not affiliated with WP Engine “in any way” to proceed; the checkbox is mandatory.
  • HTML/CSS identifiers like “login-lawsuit” suggest it’s directly tied to ongoing litigation with WP Engine.
  • Several contributors report being removed from the Make.WordPress Slack or plugin teams after asking about the checkbox or the definition of “affiliated.”
  • WordPress leadership gives deliberately vague answers about what counts as “affiliated,” sometimes telling people to “consult an attorney,” which many see as sowing fear and uncertainty.

Perceptions of Professionalism and Governance

  • Many commenters describe the move as petty, childish, or “cringe,” especially given the high‑stakes lawsuit.
  • Some argue normal legal advice would be to freeze existing ties, not to publicly antagonize the other side and its associates.
  • Confusion is highlighted between WordPress.org, the WordPress Foundation, Automattic, and the founder’s personal ownership of wordpress.org.
  • Concerns are raised about lack of independent governance and “adults in the room” who could check unilateral decisions.

Underlying Dispute with WP Engine

  • The term sheet from Automattic reportedly demands 8% of WP Engine’s gross revenue or equivalent staff time directed by WordPress.org/Automattic, with extensive audit rights, including employee records.
  • Supporters of WordPress leadership say WP Engine is a major commercial beneficiary that has a moral duty to contribute more.
  • Others counter that the GPL imposes no such obligation; WP Engine is legally free to use the code and claims to already contribute plugins, sponsorships, and community funding.

Legal and Antitrust Concerns

  • Several commenters think the login checkbox and bans hand free arguments to WP Engine’s lawyers about self‑dealing and retaliation.
  • Some see possible tortious interference, as the checkbox and bans pressure third parties to sever ties with WP Engine.
  • A minority mentions potential antitrust issues, but others note strong competition in hosting and CMS markets, making a formal monopoly case unclear.

Impact on Ecosystem and Alternatives

  • Agencies and hosts worry about relying on WordPress.org infrastructure (plugin/theme repo, updates) if access can be weaponized.
  • There are calls to fork WordPress or to shift to alternatives (ClassicPress, other CMSs, static site generators), though past forks have struggled for funding and momentum.
  • Some see this as a test of whether there is a real independent WordPress community; if no serious fork emerges, they conclude the project is de facto controlled by a single commercial actor.