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.
I’ve been pushing Squarespace for most people who come to me asking about setting up a small store or just simple business website.
Yeah, it’s closed source and blah blah blah, but the end of the day, it’s not about my opinions on software, it’s about the most cost-effective, simple, usable option for the client who is asking me for my expertise, which is almost always not something they’re going to have to keep paying me to maintain.
Like if you really really want Wordpress, I’ll get you set up, and then quote you a couple thousand a year for maintenance.
Unshockprisingly, very few people think that’s the right choice once they see what the keep-it-from-being-exploited cost is.
(And for anyone who thinks that’s an unreasonable amount, okay cool. But maintaining a staging environment and testing updates and then pushing everything into production assuming there’s no regressions you have to address takes a lot of time.)