- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
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.
Let’s just keep this conversation to the same thread.
If people post lies about trademark rights multiple places, they should be responded to multiple places.
Yeah, I agree with telling him it, but I also don’t like following up on the same thing in multiple places. I’m putting it here so Inter can respond there later.