Good. It's literally the point of choosing the GPL that organisations producing proprietary software can't benefit and mix in GPL licensed work without publishing the source.
The copyright-holder can take action against an organization producing proprietary software who is violating their copyright. Legally, they're violating the rights of the copyright-holder, not the end-user.
> The claim that a GPL violation could lead to the forcing open of proprietary code that has wrongfully included GPL'd components is simply wrong. There is no provision in the Copyright Act to require distribution of infringing work on altered terms. What copyright plaintiffs are entitled to, under the Act, are damages, injunctions to prevent infringing distribution, and--where appropriate--attorneys' fees. A defendant found to have wrongfully included GPL'd code in its own proprietary work can be mulcted in damages for the distribution that has already occurred, and prevented from distributing its product further. That's a sufficient disincentive to make wrongful use of GPL'd program code. And it is all that the Copyright Act permits.
> A defendant found to have wrongfully included GPL'd code in its own proprietary work can be mulcted in damages for the distribution that has already occurred, and prevented from distributing its product further. That's a sufficient disincentive to make wrongful use of GPL'd program code. And it is all that the Copyright Act permits.
From your own quote. This is ultimately good enough. You either get the source or the proprietary software is knee-capped/no longer allowed to be distributed. From a Free Software perspective that's a win.
Good! That’s precisely the whole point of the GPL. That is: to prevent proprietary code, which harms users, from being mixed with Free Software! Proprietary software is harmful to the users. OpenAI is malware, it has cryptominers in it. It also sets off antivirus scanners. Now we’ll get to see if their claims are true by looking at the code for ourselves
Such companies are freeloaders at best and sometimes even hostile to FOSS and to users.
This approach is what drives corporations to adopt zero-GPL policies. The GPLv3 explicitly includes language about how to cure a violation (spoiler alert: it's not "haha, we caught you - now hand over all of your source!"), and both of the mentioned violations are available under GPLv3.
This person needs to notify the copyright holders of the GPL libraries, who can then contact the copyright holders of the violating software, starting the timer on the window in which the offending software must be cured.