[felizuno]

yeah, this part is where I am confused - the dispute itself is about bad business to business behavior, but the class status of this lawsuit drills down to harm caused to end users. I'm trying to figure out what expectations end users are entitled to since it's obviously not the case that WP users can hold Automattic directly liable when they are hacked.

I _think_ the argument is that WPE gave them the (at the time reasonable) expectation that risk mitigation was handled by them, and Automattic made that expectation impossible to meet retroactively hence tortious interference, but is there language that passes the liability up the chain from the end users? To me it seems like WPE has a case but the end users as a class might face headwinds.

And for everybody angrily downvoting me I agree with you that Matt is an asshole but that doesn't mean I don't want to understand the nuance of a class claim in a case like this.

[friendzis]

IANAL. The chain of argument is roughly: WP was transferred to WPorg -> WPorg promised open access to WP ecosystem (including plugins) -> Matt/Automattic retained effective control over WPorg -> Matt/Automattic abused their control over WPorg to sabotage WPE's ability to provide contractual services -> WPE's customers suffered.

EDIT: I think the part causing most confusion is relying on customer's expectation that they are NOT using WPE's product, but rather using WP plus WPE's services. I.e. If X contractor installs a thing to your house/car/whatever and then manufacturer of that thing then uses it to sabotage your business, you get a claim against manufacturer, not you against contractor.

[mcosta]

But in this case the manufacturer does not offer any warranty at all to anybody.