WordPress.org bans WP Engine, blocks it from accessing its resources | TechCrunch
techcrunch.com
WordPress drama went up another notch on Wednesday after WordPress.org banned hosting provider WP Engine from accessing its resources.

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.

  • Echo Dot@feddit.ukEnglish
    42·
    2 months ago

    Wordpress is not a good fit for virtually any modern application. It’s designed as a blogging platform and basically no one makes blogs anymore. That functionality kind of got eaten up by Facebook and Twitter and LinkedIn, so no one needs blogs.

    Instead of letting WordPress die the death it most definitely deserves they shoehorned in functionality, which would be fine if it wasn’t such a bodge job.