by davidcollantes on 12/11/24, 6:02 PM with 59 comments
by Kina on 12/11/24, 7:19 PM
by ivraatiems on 12/11/24, 9:22 PM
Automattic has 72 hours to comply with the order. They probably will, plus or minus Matt being a whiny child about it. They have competent attorneys who are surely telling them to do so. They can also appeal the order, and they could even ask for the appeal to be granted on an emergency basis, but there's no promise that'd work, and usually it doesn't. The whole point of injunctions is that they stop things from changing until they're overturned by appeal or trial.
If they do comply, the status quo resumes until this goes to trial. There's no guarantee that WP Engine prevails at trial, but the fact that the injunction was granted means it's pretty likely they will, unless facts or law materially changes in the meantime. The statement Automattic released suggests to me that this is the path they'll take.
If they do not comply, things become... interesting. Of course, the case still eventually goes to trial. In the meantime, though, WP Engine can ask the court to force Automattic to comply. That probably looks like a motion to show cause why they have not complied, followed by further orders to comply and possible contempt findings. Contempt findings often come with monetary fines that escalate (e. g. $1,000 per day the first week, $2,000 per day the next, and so on). It can also come with jail time, though I am not sure how that works in cases where the entity being sued is a company.
It probably won't get to that, though. Refusing to comply with a preliminary injunction is an extremely bad idea, which is why almost nobody does it. Even states and government actors with strong political desires for things and a lot of power nearly always comply. While Matt Mullenweg is clearly not a rational actor, and clearly is willing to do extremely dumb things despite the advice of council, the other people who work for Automattic (and certainly its investors) are unlikely to be so willing to ignore the order of a federal court. If they do, their lives are going to get worse, not better, and possibly rapidly.
As of this writing, the Automattic WP Engine tracker site is still up.
(Hopefully some actual attorneys who read HN can correct anything I got wrong. I just haven't seen anyone write this out yet.)
by drannex on 12/11/24, 7:12 PM
He personally digitally stalked and targeted online users, followed them from site to site, publishing and using user details that weren't public, and personally started attacking and practically doxxing those that couldn't take or understand his weird (unintelligible) stances. He would even argue with random users by PM'ing directly.
Which gets even stranger that he doesn't know to stay quiet, considering Automattic had to pay out to the New York City Commission on Human Rights, for constructing teams and moderation policies that unfairly targetted LGBTQ+ individuals^2. They kept the policies after acquisition, made them worse, and ended up paying out for it - just for them to end up going back to what they were doing.
---
To 404Media: There is an incredible article waiting to be written that has your name all over it. It was a huuuge thing that Automattic tried to cover up and keep from breaking containment. Just start with "the car full of hammers" comment that led to the blow-up (after a lot of targeted build-up).
He self-destructed and went absolutely mental, it was weird and strange. This was last year.
Edit: knowyourmeme^2 has a little bit of history, but it goes much deeper. It's a great story that Vice would have covered in extremely poignant details years ago, ready for the taking.
^1: https://www.theverge.com/2022/2/25/22949293/tumblr-nycchr-se...
^2: https://knowyourmeme.com/memes/events/tumblr-ceo-transphobic...
by markandrewj on 12/13/24, 9:23 PM
I used to see WordPress as an example of how open-source can be good business. Being open-source, and comparatively better then other proprietary options at the time, made WordPress an attractive option, and its user base grew rapidly. Blogging was also more popular then, although people still blog.
I think as of today there are better options then WordPress, and blogging is not the same as in the past. I think because of peoples history with products like WordPress, many people have gravitated towards static site generators.
Early on Automattic seemed like a place I might want to work, but obviously a lot that has changed since WordPress first launched. I can't see myself wanting to work there now, or wanting to use WordPress again. Not to mention I moved on from PHP a long time ago.
by perihelions on 12/11/24, 6:53 PM
https://news.ycombinator.com/item?id=42382829 ("WPEngine, Inc. vs. Automattic– Order on Motion for Preliminary Injunction (courtlistener.com)", 19 hours ago, 107 comments)
by JuanSucks on 12/11/24, 7:23 PM
The jokes write themselves.
by thih9 on 12/11/24, 7:51 PM
At the moment I feel uncertain about Wordpress and its status. Are there any plans to bring more stability here?
Of all the tech CEOs to get humbled in 2024, why did it have to be one from an open source project?
by xet7 on 12/15/24, 7:09 AM
But I don't know actually what this is all about, is there any possibility.
I hope all the best for him anyway.
by mordymoop on 12/11/24, 6:43 PM
> WP Engine's main function is allowing businesses and organizations to build, host, and manage websites powered by WordPress.
> During the week preceding September 22, 2024, Matt Mullenweg—founder of WordPress.com—began speaking negatively about rival WP Engine. Mullenweg gave a speech at WordCamp US 2024 that argued that WP Engine had made meager contributions to WordPress compared to Automattic, criticized WP Engine's significant ties to private equity, and called for a boycott, sparking internet controversy.[30] In response, WP Engine issued a cease and desist against what it characterized as defamation and extortion, attributing his attacks to WP Engine's refusal to pay Automattic "a significant percentage of its gross revenues – tens of millions of dollars in fact – on an ongoing basis" for what it claimed were necessary trademark licensing fees (later clarified as 8% of all revenue, payable in gross or in salaries for its own employees working under WordPress.org's direction, combined with a clause that would've prohibited forking[31]) for the "WordPress" name.[32] Automattic responded by sending its own cease and desist the next day, citing the trademark issue.[33] On October 2, 2024, WP Engine sued Automattic and Mullenweg for extortion and abuse of power, which the defendants denied.[31] As a result of the dispute, WordPress.org blocked WP Engine and affiliates from accessing its servers—which include security updates, the plugin and theme repository, and more—on September 25, 2024, a day after its trademark policy was updated[34] to ask against usage of WP "in a way that confuses people", listing WP Engine as an example.[35] Following backlash, access to WordPress.org was temporarily restored until October 1 to allow WP Engine to build its own mirror sites two days later,[36][37] which the company did.[35] On the 12th, WordPress.org replaced the listing of WP Engine's Advanced Custom Fields (ACF) plugin on the WordPress.org plugin directory with a fork called "Secure Custom Fields" citing a guideline that empowers the foundation to "make changes to a plugin, without developer consent, in the interest of public safety".[38] On October 7, 2024, to align the company's stance, Mullenweg announced that 159 employees—8.4% of Automattic—had quit in exchange for a severance package of $30,000 or six months of salary, whichever is higher, with the condition that the resigned would not be able to return.[39] The next week concluded another offer of nine months' salary to attempt to placate those who could not quit for financial reasons,[40] though with only four hours to respond and the added term of being excluded from the WordPress.org community.[35]
by curiousgal on 12/11/24, 6:55 PM
by kayson on 12/11/24, 8:20 PM
by stevebmark on 12/11/24, 7:33 PM
by petemir on 12/11/24, 6:39 PM
@dang could it be fixed?
by mistercheph on 12/11/24, 7:03 PM