WordPress Plugin Repository Inaccessible to WP Engine Hosted Sites

Don't you love it that the US government released an announcement about unsafe programming languages and software vulnerabilities in general, that need to get more secured and better security / safety practices should take place...only to have the co-creator of the CMS the White House's website currently uses (SHOOOCKIIING!), to let it exposed to many attackers on various outdated plugins that cannot get upgraded by a direct competitor, because you decided to become modern day's Nero?!

If you lose most of your corporate (VIP) customers, don't come forth crying like a baby...because that is what you are mate; a baby trapped in an adult's body!

GROW UP please!

This is a security issue now! It's not clear why Mullenweb has gone off the deep end. But if we can't get updates, he's putting sites at risk. And I use "he" because it looks like there's something personal about the kind and method of the complaints. From here, it also looks like WordPress.com is practicing restraint of trade, violating the spirit if not the letter of open source, and is being arbitrary and capricious in choosing to target WP Engine with its strange laundry list of complaints when there are so many other companies with "WP" in their names or which set installation standards for plugins and themes to their hosting clients.

As I wrote elsewhere on HN, my web-focused company uses WP Engine and I administrate it and let me tell you, it's WordPress. Completely WordPress. So some defaults are changed? Every other provider I've used does something similar. Matt hasn't mentioned the other excellent default WP Engine choices, if he wants more to complain about. Random PHP calls disabled by default. Must-use security drop-in plug-ins. High-risk and processor-intensive plug-ins disallowed. Regular plug-in vulnerability reports. It's an administrative layer of choices I appreciate as a web admin because I am just one guy.

Confirmed by Wordpress: https://wordpress.org/news/2024/09/wp-engine-banned/

Blocking WPengine should make everyone aware of what the real problem is: more than 40% of the sites on the web run not only on WordPress but on one man's whim

What a shame. This feels like a defining moment for WordPress. I'm not optimistic this is going to end well for anyone in the WP ecosystem.

I've been looking to start a blog to replace my dying social media accounts. Definitely not about to consider WordPress if one guy's psychotic episode can affect it like this.

Related: WP Engine is banned from WordPress.org

https://news.ycombinator.com/item?id=41652760

All website users and business owners that host their websites on WP Engine, should start suing Matt for the damage caused by him...this is UNACCEPTABLE!

WP Engine hasn't acknowledged this yet, so I hope it's a bug or a mistake.