Live data from Hacker News

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

theverge.com

71–80 of 222 posts

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

#71
post #20

Earlier quoted context omitted.

They also have the worst social media team I have ever seen: https://x.com/WordPress/status/1845121130207535524

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

#72
post #68

Earlier quoted context omitted.

I think Matt would be quite happy with that. His issue is WP Engine not contributing to WordPress. If they decide to maintain a fork and infrastructure, they won't be freeloading anymore. Edit: That attracted a lot of downvotes. I was giving my option in response to the parent comment. In my option Automattic would be happy if they forked it.

WPE contributes to WordPress; Matt is just full of shit on this. It's an excuse, not a reason.

What does WPE contribute? I ask from a place of curiosity. Code, money?

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

#73

Earlier quoted context omitted.

Yeah, but pretty sure some of the employees/volunteers are in on it or "just following orders."

Yes, no one stopped the co-funder and it's unlikely he did the fork and the change of ownership only by himself. Other people at Automattic are responsible too.

All the sane people left when Matt offered them $30,000 or six months of salary to quit.

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

#74
post #51

Earlier quoted context omitted.

wow, they deleted 300 lines, many giving credit to others, just to replace it with > Security - ACF defined Post Type and Taxonomy metabox callbacks no longer have access to $_POST data. (Thanks to the Automattic Security Team for the disclosure) If I was on that security team, I would be livid they used my team's name on this behavior. If this was done by that security team, their ethics are disgusting, and likely n…

Wieldy enough, that line likely came from the original developer (ACF/WP Engine) [0]. I believe WordPress.org backported the change and named it v6.3.6.1 at that time [1], before rebranding ACF in a later version (v6.3.6.2). [0]: https://www.advancedcustomfields.com/changelog/ [1]: https://plugins.trac.wordpress.org/changeset?new=3164480%40a...

Ah, that would explain why those fixes are noted as "since 6.3.8".

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

#75
post #50

Earlier quoted context omitted.

It's more like gaining backdoor access to the bank's server. At this stage no attack has happened(but can happen)

They didn't gain access anywhere, it's their platform.

If the bank starts fiddling with the numbers in your account: "I'm not being attacked, it's their database"

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

#76
post #68

Earlier quoted context omitted.

WPE contributes to WordPress; Matt is just full of shit on this. It's an excuse, not a reason.

What does WPE contribute? I ask from a place of curiosity. Code, money?

Both. Matt just does not think they contribute enough. Either that or he is angry that they are more successful than his own company.

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

#78
post #31

The appropriate twist here would be to have WPEngine find a trusted third party (one or more), start a foundation together and successfully fork wordpress.

I think Matt would be quite happy with that. His issue is WP Engine not contributing to WordPress. If they decide to maintain a fork and infrastructure, they won't be freeloading anymore. Edit: That attracted a lot of downvotes. I was giving my option in response to the parent comment. In my option Automattic would be happy if they forked it.

On one hand, the claim is that WP Engine contributes nothing to the WordPress ecosystem. On the other hand, the necessity for Automattic to fork a plugin developed by WPE suggests that WPE has been contributing something significant—so significant that its continuation is essential for the community.

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

#79
post #75
post #50

Earlier quoted context omitted.

They didn't gain access anywhere, it's their platform.

If the bank starts fiddling with the numbers in your account: "I'm not being attacked, it's their database"

> bank starts fiddling with the numbers in your account

If a bank messes with your money, you ask for your money when that happens. Not defame the bank based that they updated their database, business as usual, but you liked the old one.

how exactly did they mess with your stuff? where's the attack you're speaking about? where's physical harm?

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

#80
post #68

Earlier quoted context omitted.

WPE contributes to WordPress; Matt is just full of shit on this. It's an excuse, not a reason.

What does WPE contribute? I ask from a place of curiosity. Code, money?

On code contributions, I believe the accusation was that the amount of developer time they fund is tiny relative to the size of the company.

I've not seen numbers comparing other significant WP users to them, though, only comparing them to Automattic itself, which seems a bit apples to aardvarks to me.

Post reply on HN