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.
Would it be wrong to hope they manage to commit some gross act of mutual destruction, and that the outcome would be that I never have to deal with Wordpress ever again?
That would be great but the reality is that client’s mindsets need to change. I tried to explain to a client that Wordpress is not a good fit for their complex web application and yet they didn’t wanna switch to anything else. People are way too worried about new tech and wanna stick with whatever they know, even if it causes massive problems.
Wordpress is not a good fit for their complex web application
Seriously. People want to shove everything into Wordpress then get cranky when you can’t make Wordpress into a ecommerce store, marketing platform, personal blog, file sharing service, and NFT marketplace.
And then it gets hacked because they needed 14 SEO plugins, 2 different form plugins, and were not going to pay for managed updates because that’s easy they can do it themselves.
If you’re trying to turn WordPress into an application, for christs sake go use Django, Laravel, or Rails. Don’t send a CMS to do an applications’ job.
Shit you don’t even need a CMS at this point. I moved off WordPress to Hugo and SFTP and i’m happier than a pig in shit. Shit loads fast and no external threats.
Wordpress is the Excel of CMSs. It can do just about anything, but at this point it barely manages content well.
I haven’t done web work for well over a decade and recently was surprised to learn that Wordpress is still very relevant. I remember back then, seeking alternatives as we expected it to become more of a legacy thing a few years down the track, so we were on the lookout for future-proofing client sites with a better foundation. At that point it was a decade old and annoying af because it morphed into a messy way of doing websites because people misused it’s original purpose. Brain had to think like a blog and then trick it into doing what you want, kind of like using tables to structure pages before CSS-P saved the day.
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.
Wix and Squarespace managed to be even worse options anyway.
Anyway who cares what the client thinks, they don’t know anything that’s why they’re hiring a professional. The professional thing to do would be to convince them of the advantages of one of the listed options.
Anytime I’ve ever had to deal with WordPress I’ve always run up against the fact that it has limitations that the client doesn’t understand, and then at some point you end up redesigning it custom anyway. May as well save time and start out custom.
I’ve been pushing Squarespace for most people who come to me asking about setting up a small store or just simple business website.
Yeah, it’s closed source and blah blah blah, but the end of the day, it’s not about my opinions on software, it’s about the most cost-effective, simple, usable option for the client who is asking me for my expertise, which is almost always not something they’re going to have to keep paying me to maintain.
Like if you really really want Wordpress, I’ll get you set up, and then quote you a couple thousand a year for maintenance.
Unshockprisingly, very few people think that’s the right choice once they see what the keep-it-from-being-exploited cost is.
(And for anyone who thinks that’s an unreasonable amount, okay cool. But maintaining a staging environment and testing updates and then pushing everything into production assuming there’s no regressions you have to address takes a lot of time.)
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.
Genuine question: what is the real alternative to WP?
What’s wrong with html/css/js? It can do anything you want it to do.
It doesn’t allow Dick from marketing to update the content without having to learn a skill.
Even though wordpress is an unsecure piece of shit, it’s very good at doing a just good enough shitty job quickly and cheaply (most of the time by adding a metric crap ton of even shittier plugins). Hence it’s massive popularity.
I have off-and-on searched for alternative software for personal blogs that can be self-hosted and it doesn’t seem like there are many options anymore. The only ones I’ve seen are WriteFreely and FlatPress. Are there any other options you’re aware of?
Depends on if you need a CMS, or if you can use a static site generator.
For a CMS, I’m still a fan of Ghost and it has (mostly) not enshittified to the point it’s unpleasant to use.
If you don’t need the whole CMS thing, there’s an awful lot of options. (And hosting them is super simplified since you can just stuff the output into a S3 bucket/Cloudflare Pages/Github Pages/a dozen other providers for basically free.)
https://kbin.melroy.org/m/technology@lemmy.world/t/480078/WordPress-org-bans-WP-Engine-blocks-it-from-accessing-its-resources/comment/4249030#entry-comment-4249030
There really isn’t one that’s a true alternative to WP.
There are plenty of nice static site generators, but those are significantly harder to use and not just drag and drop, they also don’t have the huge plugin marketplace that WP does.
Everyone loves to complain about WP (rightfully so in some cases, it has its own problems), but will suggest alternatives that are nothing like it.
I use WP to post weekly (sometimes more frequently) updates about my new releases and events happening in my shop (a game shop). It works for what I need, I just wish I could find I build a theme that displayed the way I want it to display.
I have one that you may not like, but fits your description.
I don’t know what wordpress is, so I would suggest just not bothering at all with whatever that is. Maybe use wordpad.
Yeah, open source licenses don’t entitle you to use trademarks.
This looks pretty bad to me.
WP Engine for WordPress.
That seems to be the commonly accepted solution if you look at other 3rd party trademark cases - situations like “RIF is fun for Reddit” coming to mind.
RIF did have to change their name though. https://www.reddit.com/r/redditisfun/comments/el8ri3/reddit_is_fun_is_being_renamed_to_rif_is_fun_for/
Reddit is fun is fun for Reddit. The WP is just WP, just like RIF is just RIF.
Like JohnEdwa said, using a trademark to refer to someone else’s product is considered nominative fair use: “referencing a mark to identify the actual goods and services that the trademark holder identifies with the mark.”
They’re very obviously using the trademark in a manner that implies endorsement.
That is absolutely trademark infringement.
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.
Wow Matt really looking bad on this one. This just reeks of trying to push out a major business competitor to wordpress.com and abusing control over wordpress.org to do it.
ThePrimeagen invited Matt to explain what’s going on.
TL;DW Matt’s claim is that he tried to get WP Engine to pay for a Trademark license (or whatever it’s called - I’m recalling from watching yesterday), over several months, and they tried to legally block him in every way. Their self-claimed contributions to Wordpress were (as he tells it) that they held conferences where they promoted their own stuff only - code contributions have been minimal.
So the combination of not willing to pay for the trademark + not contributing back (not in code, not in helping the community) is Matt’s reasoning for blocking them from using Wordpress’ resources.
He also mentioned that he has good relations with other Wordpress hosts, so it’s not like he’s trying to block anyone else from hosting, but they were all willing to pay for the use of the Trademark (and/or contribute back).
This is accurate, but also, “minimal” here is 40 hours of code contributions per week compared to Automattic’s near-4000. Additionally, WP Engine is the biggest Wordpress.com competitor.
What does WP stand for then?
Wordpress is a security hole anyway, use something else if you have to use plugins for your usecase.