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.
GPL doesn’t give you any rights to trademarks.
It’s been debated to death in the thread linked below. I tend to fall on the side of the nominative fair use, but that’s for lawyer and judge to sort out because I’m neither.
A cursory check of law review tells me the US doesn’t have a uniform nominative fair use test applicable to the resell of goods and that the supreme court has refused to endorse a test creating a lot of inconsistency between circuit court. So everyone in that thread probably right in a different circuit court.
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 them 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.