- cross-posted to:
- hackernews
- cross-posted to:
- hackernews
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.
Everytime checked someone else’s WP, the only thing that came to mind each time was a Jenga block tower. Bunch of themes and plugins that do god knows what and interact together in mysterious way. Touch anything and there’s a very good chance everything comes crashing down.
I personally send people to Wix, but I guess Squarespace is fine.
It’s that Simpsons episode where Mr. Burns is only alive because all the things that would kill him are cancelling each other out, but in PHP form.
I tend to use Squarespace because uh, they have a marketing budget and everyone tends to already know (or at least one of the people in the meeting anyways) who they are, which makes things an easier sell.
I don’t particularly think they’re the best or whatever, but they at least do what they say at a price that’s reasonable enough and I’ve yet to be burned by suggesting them, sooooo…