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.
Seriously. People want to shove everything into Wordpress then get cranky when you can’t make Wordpress into a ecommerce store, marketing platform, personal blog, file sharing service, and NFT marketplace.
And then it gets hacked because they needed 14 SEO plugins, 2 different form plugins, and were not going to pay for managed updates because that’s easy they can do it themselves.
If you’re trying to turn WordPress into an application, for christs sake go use Django, Laravel, or Rails. Don’t send a CMS to do an applications’ job.
Shit you don’t even need a CMS at this point. I moved off WordPress to Hugo and SFTP and i’m happier than a pig in shit. Shit loads fast and no external threats.