The blocked resources in question? Automatic security and features updates and plugin/theme repository access. Matt Mullenweg reasserted his claim that this was a trademark issue. In tandem, WordPress.org updated its Trademark Policy page to forbid WP Engine specifically (way after the Cease & Desist): from “you are free to use [‘WP’] n any way you see fit” to a diatribe:
The abbreviation “WP” is not covered by the WordPress trademarks, but please don’t use it in a way that confuses people. For example, many people think WP Engine is “WordPress Engine” and officially associated with WordPress, which it’s not. They have never once even donated to the WordPress Foundation, despite making billions of revenue on top of WordPress.
https://techcrunch.com/2024/09/26/wordpress-vs-wp-engine-drama-explained attempts to provide a full chronology so far.
Edit:
The WordPress Foundation, which owns the trademark, has also filed to trademark “Managed WordPress” and “Hosted WordPress.” Developers and providers are worried that if these trademarks are granted, they could be used against them.
ThePrimeagen invited Matt to explain what’s going on.
TL;DW Matt’s claim is that he tried to get WP Engine to pay for a Trademark license (or whatever it’s called - I’m recalling from watching yesterday), over several months, and they tried to legally block him in every way. Their self-claimed contributions to Wordpress were (as he tells it) that they held conferences where they promoted their own stuff only - code contributions have been minimal.
So the combination of not willing to pay for the trademark + not contributing back (not in code, not in helping the community) is Matt’s reasoning for blocking them from using Wordpress’ resources.
He also mentioned that he has good relations with other Wordpress hosts, so it’s not like he’s trying to block anyone else from hosting, but they were all willing to pay for the use of the Trademark (and/or contribute back).