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.
WordPress.org's latest move involves taking control of a WP Engine plugin
161–170 of 222 posts
Re: WordPress.org's latest move involves taking control of a WP Engine plugin
#162Thanks for the work, Matt!
Re: WordPress.org's latest move involves taking control of a WP Engine plugin
#163Re: WordPress.org's latest move involves taking control of a WP Engine plugin
#164Earlier 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 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
#165Earlier 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?
Re: WordPress.org's latest move involves taking control of a WP Engine plugin
#1661. 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.
Re: WordPress.org's latest move involves taking control of a WP Engine plugin
#167To me, WordPress used to be the thing you used if you wanted a website that was easy to put together but was full of third party php spaghetti code and security holes. Now, it's completely radioactive.
Re: WordPress.org's latest move involves taking control of a WP Engine plugin
#168Re: WordPress.org's latest move involves taking control of a WP Engine plugin
#169The 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.
It isn't as one sided as you would imply.
Re: WordPress.org's latest move involves taking control of a WP Engine plugin
#170can 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
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.