> …the risk-reward ratio of theoretical copyright litigation is not good, especially when litigating against open source projects tends to paint a target on you

> …the risk-reward ratio of theoretical copyright litigation is not good, especially when litigating against open source projects tends to paint a target on your back. And the example they give (without the link being preserved) is a patent case which is completely different. 75 years from now the heirs of the developer who wrote the library being discussed can go on a copyright lawsuit spree and there’s no amount “FLOSS community pressure” which could stop them. People keep giving advice on this issue of “it probably doesn’t matter, they put it on GitHub because they want people to use the code” which might be true today but it also might matter a whole lot tomorrow for whatever reason. Bad, bad advice…