Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think this is fair. I think wordpress had every right to cut WPEngine off, but

1) the fact that subbing in his fork of their plugin killed already purchased "pro" user features without warning was an illegitimate attack on the "pro" customers themselves (who probably have a case against him personally),

2) the pretense that he was doing it for "security reasons" because there was an exploit (every single part of everything about wordpress has an exploit in a random month) shows that he thought he was doing something unjustifiable; he should have been clear and open about why he was forking, and not do anything that broke people's installs, and

3) the behind-the-scenes harassment was just over the top. He should have just made his demand, and when they turned it down, sent a follow up explaining how he was going to cut off access so they could coordinate doing it cleanly. Instead he was intentionally optimizing for chaos and saying this in private communications over and over again.

He could have done almost all of the same things, and just refused to update "pro" users to the fork and instead refer them to WPEngine's alternative setup. Instead he ranted and raved ominously behind the scenes, trying to make it as clear as possible that this was extortion when in essence it wasn't. It was all of the fake snarkiness in public and in private, attempts to poach employees, threats to destroy the company, and insinuations of security problems that made it extortion.

WPE is going to win this because Mullenweg seemingly has no ability to emotionally self-regulate. Real teenage swatter vibes. And I think he was in the right, and I think that without all of the crap, they'd probably have backed down and started contributing.

They'll probably end up getting a remedy where he has to help them set up and maintain their alternative plugin directory, he might have to pay them damages, and he might even end up having to allow everyone use of the mark freely. Then what does he have? He snatched defeat from the jaws of victory.



> I think wordpress had every right to cut WPEngine off

Even though wordpress.org is built/maintained by volunteers such as WPEngine who were all told it's a "community asset", "nobody owns it but wordpress", "it's maintained by the foundation".

Volunteers who now find out from court documents that wordpress.org is the personal website of Matt who can do whatever he wants with it?

Volunteers who are now banned from the thing they helped build for simply voicing disagreement with actions which are accepted by most as extreme/unwarranted?

Even volunteers who work on WordPress (not w.org), who built in to the Core reliance on w.org infrastructure after being lied to that it's owned by the Foundation.

I think in this specific case, they have absolutely no right and the injunction supports that.


> the pretense that he was doing it for "security reasons" because there was an exploit (every single part of everything about wordpress has an exploit in a random month) shows that he thought he was doing something unjustifiable

Not to mention the threats posted online to other plugin developers, "we can and will find an exploit in your plugin and do exactly the same to you if we want" indicated it had very little to do with security. I'm sure he had Automattic employees pulled onto finding even the most trivial of exploits just to be able to do this.

> they'd probably have backed down and started contributing

WPE contributes probably in the seven digit a year range to WP. The very conference that Matt went "nuclear" at was sponsored by WPE to the tune of $75K (and for insult on injury, they were denied the ability to attend, and I believe all references to them were removed, but the money was kept).


The explanations in the injunction with regards to clients' contracts of wpengine does not read like he ever had any right to cut wpengine off. And his argument about how trademarks somehow gave him a right to ask for money from a wp hoster was never valid. I don't think he ever had a right to cut off wpengine, neither legally nor ethically. The case will be a complete loss for WordPress, and matts statements probably didn't even change that all that much, they just make the decision easier and add additional charges to lose, like the blatant extortion.

(It's thinkable to ask for money from entities accessing the plugin registry, making it a paid api. But not a fee from a company just for using a Foss software. The license doesn't allow that.)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: