Post #2900981

2026-04-18 22:04 UTC

@jedbrown@hachyderm.io A case from 2022 still not a trial in 2026 doesn't indicate unreasonable or manipulative delay by Defendants. Such cases really do take that long. Also, Doe vs. Microsoft's Github is a terribly constructed case and actually pushes us toward compulsory licensing of #FOSS works for #LLM-backed gen-#AI training— since the Plaintiff's lawyers in that case are clearly chasing their own avarice, not software freedom. Background: https://sfconservancy.org/news/2022/nov/04/class-action-lawsuit-filing-copilot/ @cwebber@social.coop @ossguy@fedi.copyleft.org @richardfontana@mastodon.social

Replies (1)

@jedbrown@hachyderm.io 2026-04-18 23:19

@bkuhn@fedi.copyleft.org I had browsed the docket, but you are right that it is not for me to say whether motions are a delay, and plaintiffs also do not seem to be in a rush (e.g., joint motion to postpone deadlines). The point is that we don't know how such litigation will play out, especially in light of the volatility of public sentiment about this industry. Has anyone written an analysis of how their case pushes toward compulsory licensing? If LLM outputs routinely constitute derivative works, then it is impossible to comply with licenses (even permissive ones) without acknowledging all such training data and/or constant open-ended research quests as due diligence that each response does not infringe an unknown corpus. The companies don't want to disclose their corpus because their business relies on not acknowledging the derivative relation. @cwebber@social.coop @ossguy@fedi.copyleft.org @richardfontana@mastodon.social

Open ##2900982