Live data from Hacker News

WordPress.org's latest move involves taking control of a WP Engine plugin

theverge.com

161–170 of 222 posts

Re: WordPress.org's latest move involves taking control of a WP Engine plugin

#161
post #137

1. Release your code as open source. 2. Make a fortune. 3. Complain that people are freeloading. 4. Abuse your power as project founder to punish them, torching the community trust you’ve built up over decades. 5. Profit? Whatever Mullenweg hoped to gain by undermining WPEngine can’t possibly be worth the damage he’s done to WP and his own company.

[deleted]

Re: WordPress.org's latest move involves taking control of a WP Engine plugin

#162
Got a call today from a client I hadn't heard from in 5 years. They use ACF, they use another plugin that WPEngine acquired to move their uploaded files to S3. They're freaking out at all this and worried about how the next thing might impact their business... so they want off WordPress.

Thanks for the work, Matt!

Re: WordPress.org's latest move involves taking control of a WP Engine plugin

#164
post #37

Earlier quoted context omitted.

For those reviewing the changeset: There are two places where they read a value directly from $POST into an $args array. There is no validation applied, which means an attacker can inject whatever value they wish.

In 2024, wtf. How can anyone especially on software with this kind of reach still do such absolute amateur things?

> want free software to run website

> want free plugins to add functionality to site

> absolutely will not hire developers or pay for software or plugins

> how dare the free plugin for my free software not be coded to the highest standards

Re: WordPress.org's latest move involves taking control of a WP Engine plugin

#165
post #71
post #20

Earlier quoted context omitted.

This is wild. Surely Matt isn't tweeting from the official account - marketing would not allow that, right?

You mean his subordinate after he gave six months worth of pay for everyone not on his side to leave the company?

"You don't agree with what I'm about to post? Here's a severance check."

Re: WordPress.org's latest move involves taking control of a WP Engine plugin

#166
post #137

1. Release your code as open source. 2. Make a fortune. 3. Complain that people are freeloading. 4. Abuse your power as project founder to punish them, torching the community trust you’ve built up over decades. 5. Profit? Whatever Mullenweg hoped to gain by undermining WPEngine can’t possibly be worth the damage he’s done to WP and his own company.

[deleted]

Re: WordPress.org's latest move involves taking control of a WP Engine plugin

#169

The whole thing is confuinsing. It turns out WP Engine is not part of WordPress (despite the name) and has never contributed to WordPress. WordPress are trying to take more control of their name/trademark.

There's more to the story, as recounted in other threads here.

It isn't as one sided as you would imply.

Re: WordPress.org's latest move involves taking control of a WP Engine plugin

#170
post #135

can someone please explain the feud for those of us who are out of the loop?

Matt Mullenweg - owner of wordpress.org (open-source project) and wordpress.com (paid WordPress hosting provider) He is angry that WPEngine makes money with Wordpress hosting. He thinks wordpress.com should be the only paid WordPress hosting provider. He demanded 8% of revenue of WP Engine or he would embark on a “scorched earth nuclear approach” to WP Engine. https://bullenweg.com

wordpress itself is GPL, so anyone, not just WPEngine, should be allowed to freely provide hosting.

This is exactly what elastic search faced, which necessitated their changing of their license, and subsequently, caused AWS to fork elastic search.

Elastic search cannot, and do not, have the right to demand payment from AWS.

Post reply on HN