News for hackers. Stuff that matters.
Re:WP Engine sent "cease and desist" letter to Automattic by bastawhiz on Monday September 23, 2024 @10:24PM (#41632546)
The most damning claim, I think, is that Automattic put a banner in every WordPress dashboard on the subject, including WordPress instances hosted by WPE. Automattic is a direct competitor to WPE (by way of WordPress.com). I'm no lawyer but I expect there's at least some argument to be made that there's some abuse of Automattic's position in doing so (though I don't know enough about the law to know whether they have a chance of winning such an argument). If Automattic was purely producing open source software with no vested interest in profit, that would be a different story perhaps.
Re:WP Engine sent "cease and desist" letter to Automattic by tptacek on Monday September 23, 2024 @11:32PM (#41632900)
"Abuse of position" is not generally an actionable claim.
Re:WP Engine sent "cease and desist" letter to Automattic by uudecoded on Tuesday September 24, 2024 @12:43AM (#41633152)
Generally, but also especially when the position is "WordPress".
Re:WP Engine sent "cease and desist" letter to Automattic by eastbound on Tuesday September 24, 2024 @12:56AM (#41633193)
Yes, but being the editor of the software used by your competitor is certainly funny.
Re:WP Engine sent "cease and desist" letter to Automattic by sfmike on Tuesday September 24, 2024 @01:37AM (#41633389)
just for monopolies right? And for hosting online and software that does it(two verticals of wordpress) there are hoardes of options.
Re:WP Engine sent "cease and desist" letter to Automattic by Terr_ on Tuesday September 24, 2024 @01:57AM (#41633486)
> just for monopolies right?

I suspect that's still not actionable in the way the parent poster means, since AFAICT there no private right of action: You can't sue, only petition some government agency to bring their own lawsuit.

Re:WP Engine sent "cease and desist" letter to Automattic by throwup238 on Tuesday September 24, 2024 @02:57AM (#41633783)
US antitrust laws grant private rights of action for monetary damages and injuctive relief. They’re unlikely to apply to Automattic/Wordpress though.

(Most other governments don’t grant these rights though)

Re:WP Engine sent "cease and desist" letter to Automattic by DannyBee on Tuesday September 24, 2024 @01:25PM (#41638864)
Unfair competition is, particularly in California, which interprets it's UCL very broadly.

Let's set aside all other claims (there are others), and take a look at "Unlawful, Unfair, and Fraudulent Business Acts" under that.

We'll also throw out unlawful business acts (I don't see anything unlawful so far).

Unfair: "An “unfair” business act or practice, as defined by the UCL, is typically committed by either a company or a business competitor. ... In the context of a business competitor, it is considered an unfair business act when the company does something that broadly undermines competition in the marketplace."

Additionally, they consider " immoral, unethical, oppressive, and unscrupulous" business acts to be unfair.

Banners on wp engine sites probably not a good thing under this. Threatening your competitors with bad keynotes unless they pay you, also probably not a great practice.

(I do think you'd be fine to say they suck. I just don't think you can get away with basically extorting them)

Fraudulent: "The UCL also prohibits “fraudulent” business acts or practices, which means any conduct that misleads or deceives consumers."

Note that it does not have to be defamation, or malice, or illegal. Just misleading or deceptive. More exactly, it does not have the elements of common law fraud - Intent is not a requirement, and negligence can be a violation.

So pure opinions without intent or with negligent intent that actually deceive consumers, while not defamation or common law fraud, are quite possibly a fraudulent business practice.

Overall, I think they have a stronger case than you might. Not on defamation, but on other things.

Regardless of the outcome, the approach i see taken by the Automattic CEO here seems remarkably stupid.

Don't mix your roles unless you want a court to mix your roles.

When he threatens to ban them from wordcamp[1] in what capacity is he doing it in?

1. Which, btw, the central website totally avoids mentioning who is in charge or paying overall anywhere i can find. I hope it's not the foundation (or him or automattic) and he's not mixing roles further while threatening his competitors.

Re:WP Engine sent "cease and desist" letter to Automattic by tptacek on Tuesday September 24, 2024 @03:17PM (#41639922)
I'm just happy to have successfully baited you into commenting. You're obviously more authoritative than I am on this.
Re:WP Engine sent "cease and desist" letter to Automattic by dpifke on Tuesday September 24, 2024 @08:08PM (#41642317)
Piling on re: mixing roles: I read "abuse of position" in the GP comment as "conflict of interest," which is potentially problematic for a board member of a non-profit.

I can't speak to the veracity of the facts presented in WP Engine's C&D letter, but my reading of it is they're accusing the head of the WordPress Foundation, in his official capacity, of putting the interests of his for-profit company ahead of the non-profit's stated mission. That's the sort of thing that could threaten the foundation's 501(c)3 status, or in extreme cases lead to criminal charges.

Re:WP Engine sent "cease and desist" letter to Automattic by trog on Tuesday September 24, 2024 @12:56AM (#41633195)
I have never thought of WPE as a competitor to WordPress.com but perhaps weirdly I think of WordPress.com as a competitor to WordPress.org.

For example, if I have a WordPress site I've built from scratch out of WordPress.org, I am just going to assume trying to put it on WordPress.com will be annoying (and possibly even impossible?), because of issues with themes or plugins or whatever due to the fact that WordPress.com is a separate, hosted SaaS-style CMS, and not a hosting environment for WordPress sites.

WPE, by contrast, is Just Another Webhost to me, with some special bells and whistles for WordPress.

Re:WP Engine sent "cease and desist" letter to Automattic by fhd2 on Tuesday September 24, 2024 @01:23AM (#41633316)
It's quite possible to host a "normal" WP installation with custom themes and plugins on WordPress.com (on the more expensive plan), I've done it a few times. But as much as I want to like it, I can't wholeheartedly recommend it. Some stuff that should be easy is just ridiculously difficult, like pulling logs programmatically. I think the main audience it caters to is people hosting a basic site with off the shelf themes.
Re:WP Engine sent "cease and desist" letter to Automattic by camgunz on Tuesday September 24, 2024 @04:53AM (#41634533)
Isn't this completely fine? If you and I both make aspirin, but we both put a little something extra in it (me vanilla, you salt) and I put banners on my web page saying "bastawhiz's salty aspirin puts the ass in aspirin", doesn't this just seem like typical rivalry? My point here is that defamation is defamation no matter the scale. I think scale is relevant re: damages, but not as to whether or not rivalry escalated to defamation in the first place.
Re:WP Engine sent "cease and desist" letter to Automattic by chrisandchris on Tuesday September 24, 2024 @05:32AM (#41634759)
> Automattic put a banner in every WordPress dashboard on the subject, including WordPress instances hosted by WPE

> I put banners on my web

There's a large difference between putting up a banner on _your_ site and abusing your position to put a banner on _every_ site you can.

Re:WP Engine sent "cease and desist" letter to Automattic by malermeister on Tuesday September 24, 2024 @05:51AM (#41634866)
If you sell my aspirin in your shop, you will have to accept what I put on the packaging or stop carrying my product.
Re:WP Engine sent "cease and desist" letter to Automattic by chrisandchris on Tuesday September 24, 2024 @06:21AM (#41635031)
That's true, but does not apply to this situation.

Automattic is not the owner of WordPress, the WordPress Foundation is. Even though many employees of Automattic work (maybe full-time) on WordPress [1].

So I sell your aspirin in my shop, and a friend of yours helped you package your aspirins and while doing that put some stickers onto your aspirin.

[1] https://www.df.eu/blog/wer-steckt-hinter-wordpress-ueber-die... (German)

Re:WP Engine sent "cease and desist" letter to Automattic by Matticus_Rex on Tuesday September 24, 2024 @09:41AM (#41636369)
Does WPF take issue with this operational decision by Automattic? If so, they have the avenues to deal with it, and they're the party who can claim to be aggrieved, if it violates some duty Automattic has to WPF. I seems more like this, from my understanding:

You sell a brand of aspirin in your shop. The brand has outsourced most of the production and decision-making to another company. That company puts messages on the bottle. If those messages bother me, I can bring it up with the brand and see if they'll address it, or stop carrying the brand, but the question of whether they've overstepped is for the brand owners rather than me.

Re:WP Engine sent "cease and desist" letter to Automattic by FireBeyond on Tuesday September 24, 2024 @12:36PM (#41638321)
> and they're the party who can claim to be aggrieved, if it violates some duty Automattic has to WPF

Tortious interference - where one party (Automattic) interferes with a contractual relationship between two parties (WPengine, their customers), in this case by means of disparagement pushed to the dashboard of WPengine instances.

Re:WP Engine sent "cease and desist" letter to Automattic by Matticus_Rex on Wednesday September 25, 2024 @10:42PM (#41654014)
Tortious interference requires that the interfering party induce the party to the contract to a breach of the contract. Where's that element?
Re:WP Engine sent "cease and desist" letter to Automattic by FireBeyond on Thursday September 26, 2024 @10:01PM (#41665554)
Inducement? Like "We have blocked the ability to access plugin and other repositories for customers of WPEngine. We have not done so for this other, "independent", for-profit entity (that just so happens to be owned by the same person)"?
Re:WP Engine sent "cease and desist" letter to Automattic by Matticus_Rex on Wednesday October 09, 2024 @12:49PM (#41789989)
Inducement to what? Where's the breach of contract being encouraged?
Re:WP Engine sent "cease and desist" letter to Automattic by mthoms on Tuesday September 24, 2024 @03:16PM (#41639909)
Here's the thing. Guess who is the head of the WordPress Foundation?

Matt Mullenweg. CEO of Automattic.

Now guess who The WordPress Foundation granted sole rights to sub-license their trademarks? You guessed it. Automattic.

Yeah, it gets worse the more you look at it.

Re:WP Engine sent "cease and desist" letter to Automattic by keane on Tuesday September 24, 2024 @03:47PM (#41640184)
Automattic originally registered the trademark WordPress. They donated it to the WordPress Foundation while retaining a commercial license to the marks. https://wordpress.org/book/2015/11/the-wordpress-foundation/
Re:WP Engine sent "cease and desist" letter to Automattic by mthoms on Wednesday September 25, 2024 @12:03PM (#41648891)
Some important nuance is lost here. Matt Mullenweg transferred the trademark to the WordPress Foundation (which he is head of) and the foundation (again... Matt himself) in turn granted Automattic the exclusive ability to sub-license the name commercially. This is the important bit.

What this means is that any "licensing fee" would be paid to Matt's private, for-profit, VC-backed company (and direct competitor to WPEngine) and there would be zero accountability for how it would be spent.

In practice, the foundation doesn't enjoy any benefit to owning the marks. It's all smoke and mirrors.

Re:WP Engine sent "cease and desist" letter to Automattic by keane on Thursday September 26, 2024 @03:13PM (#41662057)
The trademark policy sounds like it falls somewhere between the Mozilla Foundation/Corporation model and the Red Hat/Fedora Project model. This is how open source in practice works.
Re:WP Engine sent "cease and desist" letter to Automattic by mthoms on Thursday September 26, 2024 @03:31PM (#41662270)
Not really. The Mozilla Corporation and Red Hat aren't direct 1:1 commercial competitors to the people they also license the trademarks to (as is the case with Automattic and WPEngine). It's an obvious conflict of interest and inherently problematic on so many levels.

If there is a real-world open-source analogue to that situation, I'd be genuinely interested in hearing about it.

To me the solution seems simple; The WP Foundation should own and license the trademark. Then use the proceeds for its mission in a way that is accountable to the community (Automattic should not have to pay of course).

Re:WP Engine sent "cease and desist" letter to Automattic by Matticus_Rex on Wednesday September 25, 2024 @10:39PM (#41653992)
How does that look worse?
Re:WP Engine sent "cease and desist" letter to Automattic by mthoms on Thursday September 26, 2024 @03:41PM (#41662378)
Do I need to spell it out? The foundation is headed by the same person who they granted an exclusive license to. Not just a commercial license to use the trademarks. It's permission to sub-license the trademarks for profit without restriction. It's blatant self-dealing.

It's an obvious conflict of interest for a foundation that is supposed to be serving the community.

Re:WP Engine sent "cease and desist" letter to Automattic by camgunz on Tuesday September 24, 2024 @03:16PM (#41639906)
One person's "abuse" is another person's "I have this platform and can use it however I like." For another example, whenever cable companies (dish, etc.) have licensing disagreements with content creators, they put up a bunch of ads that are like, "ESPN's unfair negotiations mean you may lose access to this channel, call this number to complain". That's never been found to be defamatory--it occurs to this day.
Re:WP Engine sent "cease and desist" letter to Automattic by justinclift on Tuesday September 24, 2024 @06:31AM (#41635093)
Nah. Putting disparaging claims directly on the dashboard of my customers seems pretty abusive, and if it happened to me I'd be looking at legal options too.
Re:WP Engine sent "cease and desist" letter to Automattic by tasuki on Tuesday September 24, 2024 @12:50PM (#41638433)
Automatic are publishing a blog post and syndicating it to RSS, and some other software (WP.org) is displaying that feed.

If you choose to use the WP.org software as is, it's kind of your fault, isn't it?

Re:WP Engine sent "cease and desist" letter to Automattic by camgunz on Tuesday September 24, 2024 @03:18PM (#41639927)
What about regular, non-disparaging claims? Isn't it a fact that WP Engine turns off the backup stuff? Truth's a defense to libel.

This seems to me plainly like regular old competition. Can you point to something that's clearly defamatory?

Re:WP Engine sent "cease and desist" letter to Automattic by bastawhiz on Tuesday September 24, 2024 @03:34PM (#41640068)
No, it would be like if Google started using Google Tag Manager to put banners on websites that use Plausible Analytics saying "this website uses analytics that might not be accurate!" Or if Cloudflare started putting banners on websites that use S3 saying "downloads might be slow because this website doesn't use Cloudflare R2"
Re:WP Engine sent "cease and desist" letter to Automattic by __jonas on Tuesday September 24, 2024 @06:56AM (#41635212)
Sorry could you expand on this, how can they "put a banner in [...] WordPress instances hosted by WPE"?

I was under the assumption that WordPress is OSS, and WPEngine is running this software on their platform, so there was an update to this software, contributed by Automattic developers which included a banner denouncing WPE, and the WPE people decided to just deploy that update to their platform?

I don't think that means they "put the banner on their instance" does it? If they are unhappy with the management of the open source software they are using on their platform they presumably could fork it, or decide to not deploy the version that includes this banner, no?

Re:WP Engine sent "cease and desist" letter to Automattic by pluc on Tuesday September 24, 2024 @07:03AM (#41635250)
There's is a widget on the default WordPress dashboard that displays a RSS feed of WordPress.org, where Matt posted his rant, making it show up everywhere.
Re:WP Engine sent "cease and desist" letter to Automattic by __jonas on Tuesday September 24, 2024 @07:34AM (#41635414)
Ah I see, thanks for clarifying!

I have seen the mentioned blog post now [1] the whole thing is starting to make more sense to me.

[1] https://wordpress.org/news/2024/09/wp-engine/

Re:WP Engine sent "cease and desist" letter to Automattic by brvry on Tuesday September 24, 2024 @09:30PM (#41642752)
I think we’re conflating a link in an RSS feed (that can be disabled by the user or WPE) and a banner - typically a large(r) notification in a prominent spot in the UI. This point feels like a distraction.
Re:WP Engine sent "cease and desist" letter to Automattic by chiefalchemist on Tuesday September 24, 2024 @10:39PM (#41643182)
Automattic's WP VIP hosting would be a competitor of WPE. VIP is enterprise level. But perhaps Automattic is considering a less high end offering and this is the first move to capturing some quick market share?