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.

  • Aatube@kbin.melroy.orgOP
    0·
    3 months ago

    At most, they just ambiguously used “Powered by WordPress Experts” once. I don’t see how the evidence misleads people into thinking there was an endorsement.

    IMO, dumb people confuse stuff all the time, like the Minecraft Gamepedia with the Minecraft Wikia back then. The meager amount of evidence presented does not convince me that WP Engine has done any actual harm to the WordPress brand.

    But yeah, the smart way out would’ve been adding a “WP Engine is not associated with WordPress.org”, at least one below the “WP ENGINE®, VELOCITIZE®, TORQUE®, EVERCACHE®, and the cog logo service marks are owned by WPEngine, Inc.” footer. All in the past now, though. At the best both companies are tomfools.

        • conciselyverbose@sh.itjust.worksEnglish
          0·
          3 months ago

          No, they can’t, because no, it isn’t. That’s what trademarks are for. You can’t use a trademarked name to refer to your competing product.

          Open source projects are generally permissive in terms of people repackaging their code for distribution for different platforms within reasonable guidelines, but even that is a sufficient change that they aren’t obligated to allow their trademarks to be used that way.

          It is no longer Wordpress once it’s modified. That’s what trademark is for.

                  • Aatube@kbin.melroy.orgOP
                    0·
                    3 months ago

                    That is the question. I think this is all perfectly achievable by only writing new, separate software to selectively gatekeep the configuration files without changing the source code of WordPress itself. Like I said, not dedicating more resources to WordPress.org doesn’t give WP Engine the moral high ground either, though.

            • conciselyverbose@sh.itjust.worksEnglish
              0·
              3 months ago

              There is no “enough”. Any modification at all takes their permission to use their trademark.

              Most allow you to do so within reasonable guidelines, but that only gives you the benefit of the doubt if it’s ambiguous. As soon as they tell you that you don’t have permission to use their trademark on your altered version, you can’t use it.