Live data from Hacker News

Incident: Wordpress.org has blocked WP Engine customers from registry

wpenginestatus.com

21–30 of 90 posts

Re: Incident: Wordpress.org has blocked WP Engine customers from registry

#21
post #5

Why though?

> "I won’t bore you with the story of how WP Engine broke thousands of customer sites yesterday in their haphazard attempt to block our attempts to inform the wider WordPress community regarding their disabling and locking down a WordPress core feature in order to extract profit.

> What I will tell you is that, pending their legal claims and litigation against WordPress.org, WP Engine no longer has free access to WordPress.org’s resources.

If you read the full (pretty short) statement, it comes of as something written at the end of a bad day with a lot of petty and vindictive emotion behind it all. Regardless of the actual issues, which I know no more of than the statement on the website.

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

Re: Incident: Wordpress.org has blocked WP Engine customers from registry

#22
So Matt's mom confused WP Engine for official WordPress and Matt then decided that they are infringing on the WordPress trademark, by using "WP" and calling themselves "#1 platform for WordPress." Then, he threatened WP Engine to pay up or he will go to war against them, and now we are seeing what he meant by that.

Honestly, seems like pretty immature behavior, but it's entertaining at least.

Re: Incident: Wordpress.org has blocked WP Engine customers from registry

#25

Related announcement from Wordpress.org: https://wordpress.org/news/2024/09/wp-engine-banned/

>The reason WordPress sites don’t get hacked as much anymore is we work with hosts to block vulnerabilities at the network layer

I wonder what it means.

Re: Incident: Wordpress.org has blocked WP Engine customers from registry

#26
post #14

while i understand the sentiment of wpengine not contributing back, if Mullenweg were serious about gaining support from the community he would give a date for people to migrate their systems off of WPEngine before they blocked it. this just feels petty as hell and honestly makes me annoyed at him than anything, no warning whatsoever. nobody has time to just "migrate to pressable" on a whim. just be glad it's somethi…

Yeah this is my take as well. This feels like a mudsling fight and it’s messy. Whatever the .coms do is theirs, but the .org should not be in this one.

Re: Incident: Wordpress.org has blocked WP Engine customers from registry

#27

I have no dog in this fight, but from the outside this is ludicrous behaviour. Matt Mullenweg, the CEO of a for-profit WordPress hosting company, should not be using his position in the open-source WordPress project to attack another for-profit WordPress hosting company. Nothing could tank the reputation of the open-source WordPress project faster.

This only tanks the reputation of Mullenweg himself and his WordPress hosting company. WordPress powers about 40% of the web - it is too big to fail (as of now).

Re: Incident: Wordpress.org has blocked WP Engine customers from registry

#29
God the hubris of the Wordpress camp..

https://wordpress.org/news/2024/09/wp-engine/

> WordPress is a content management system, and the content is sacred.

Wordpress people have been rewriting content without asking for permission FOREVER, potentially breaking code embedded in content. They rewrite (or perhaps stopped by now, I've moved on) Wordpress to WordPress.

Re: Incident: Wordpress.org has blocked WP Engine customers from registry

#30

The statement at Wordpress.org reads like a very emotionally charged e-mail. While I am not in the know of the situation, it seems like a bit of terrible PR. https://wordpress.org/news/2024/09/wp-engine-banned/

The statement isn't at wordpress.com
Post reply on HN