I use Arch btw

IDK then. spinning up an entire game engine just to do what Electron does seems unbelievably wasteful though.

Not being able to transfer purchases seems like an other-platforms problem. Steam has authenticated API for users’ game libraries.

Sure, a small disclaimer wouldn’t, and a large, prominent, tobacco-style disclaimer wouldn’t get rid of everything but will make a dent. Anything else? Where is the endorsement? Where is the modification?

To be fair, Epic Store was marred by exclusives and having way less features back then. Even now, their (Electron) launcher boots up way slower than (CEF) Steam, and their sales are way worse.

While I agree with the politics part (especially the notorious suspend-then-hibernate thing), I do see why a lot of devs would ask for systemd-init: to just bundle 1 kind of service instead of a gazillion. Same thing with Flatpak and not needing to build a gazillion binaries for every distro that hasn’t packaged you, even though FLatpak’s sandboxing away from native libraries is something I just don’t like.

They’re advertising the speed of their cache, which can easily be just a plugin, and the amount of servers, which well of course is external software that requires no changes to WordPress.

As for the endorsement part, I’ll just copy what I said above:

At most, they just ambiguously used “Powered by WordPress Experts” once. I don’t see how the evidence misleads people into thinking there was an endorsement.

But yeah, the smart way out would’ve been adding a “WP Engine is not associated with WordPress.org”, at least one below the “WP ENGINE®, VELOCITIZE®, TORQUE®, EVERCACHE®, and the cog logo service marks are owned by WPEngine, Inc.” footer. All in the past now, though. At the best both companies are tomfools.

See, that’s why I don’t like talking about the same thing in multiple threads.

The second you change how a project works in any way in any context, it is no longer the same product and you are not entitled to use their trademark to reference it.

However, it’s quite plausible that they did not modify the project at all. Instead, they are providing their own servers and dictate how their servers work while the WordPress source code (& binaries) themselves are isolated from any changes. That’s a new service.

There’s a past case where “an independent auto repair shop that specialized in repairing Volkswagen cars and mentioned that fact in their advertising was not liable for trademark infringement so long as they did not claim or imply that they had any business relationship with the Volkswagen company”, which I think holds just as well here.

as soon as they were contacted and told that their use was unacceptable, that ambiguity goes away.

Think that over. If that were true, you’d have endless corporate bullying. Every past “nominative use” case has originated from a trademark holder suing a plaintiff.

(IANAL)

This is accurate, but also, “minimal” here is 40 hours of code contributions per week compared to Automattic’s near-4000. Additionally, WP Engine is the biggest Wordpress.com competitor.

There is a debate, and it’s in that thread. I have replied to you there, and you have not yet.

I’m not saying it’s legal, I’m saying it’s part of being “nice”. Matt claims Automattic also gave WP Engine the option to pay the license in contributing development hours.

They do still have some basic protection. Steam’s default, loose, DRM requires you to launch Steam when you open a game’s executable.

Manjaro has a stability track record miles worse than Arch, to the point where someone made a GitHub wiki called “Manjarno”.

I’d doubt that. Everyone hated S mode: Corporate hated it, power users hated it, newbies…probably ignored it. Even if MS continued down it, it’d just be like Digg v4.

Personally, I think the profit incentive is a way to improve SteamOS further for free.

After December 2018, which is when WordPress 5.0 released?

It’s Medium, whaddya expect?

Yeah, I agree with telling them it, but I also don’t like following up on the same thing in multiple places. I’m putting it here so Inter can respond there later.