←back to thread

479 points plam503711 | 1 comments | | HN request time: 0.212s | source
Show context
florbnit ◴[] No.44004552[source]
> We’re not going to waste days chasing them. But at some point, this goes beyond saving a few bucks: it becomes performance art.

Oh for the love of tech, do chase them. This absolutely has to be in void of the terms of your trial take them to court. If not, then at the very least name and shame the company, so some dumb manager orchestrating this silly theft will get fired and someone more mature can be rotated in.

replies(7): >>44004613 #>>44004622 #>>44004679 #>>44004709 #>>44005332 #>>44007040 #>>44009381 #
plam503711 ◴[] No.44004613[source]
I’m actually considering reaching out directly to the CEO and telling the full story. But honestly? There’s a good chance he’s fully aware — and totally fine with it. That’s part of what makes it so disappointing.

We’re not rushing into legal action — it’s not worth the energy for now — but publicly calling out the behavior felt necessary. It also sends a message to others in the ecosystem about the kind of nonsense OSS maintainers sometimes face.

And yes, while I’m still holding off on naming the company directly… I haven’t ruled it out.

replies(11): >>44004717 #>>44004734 #>>44004740 #>>44004748 #>>44004836 #>>44004930 #>>44005036 #>>44005106 #>>44005234 #>>44007093 #>>44009913 #
threeseed ◴[] No.44005106[source]
> There’s a good chance he’s fully aware — and totally fine with it

Why would you think that a CEO would involve himself in matters like this ?

Especially given that whichever aerospace company it is would be far more concerned with issues like tariffs, geopolitics, recession risks etc than whether or not a company is using an open source versus a community edition of some forgettable infrastructure component.

Also choosing to pursue legal action instead of simply blocking them from downloading more free trials seems childish and short sighted.

replies(2): >>44005199 #>>44005352 #
plam503711 ◴[] No.44005199[source]
"forgettable infrastructure component": this is what runs their entire IT. We build both the hypervisor and the backup/orchestration for it. Our stack could kill their entire operations if it's down because $whatever. 4000 virtual machines running isn't just the print server or the coffee machine.
replies(2): >>44005577 #>>44008763 #
1. Disposal8433 ◴[] No.44008763[source]
> 4000 virtual machines

At that point I would have created some scripts to randomly reboot or fuck with their VMs. How long will you accept this? They won't pay ever.