News for hackers. Stuff that matters.

A comment on GitHub Copi­lot inves­ti­ga­tion. Parent comment

Re:GitHub Copi­lot inves­ti­ga­tion by jakelazaroff on Tuesday October 18, 2022 @09:47AM (#33247054)
Again, if I put code in a public repo on GitHub and don’t include a license that allows it, you cannot copy that code. It doesn’t matter that you’re able to access it.
[ Parent | on HN ]
Re:GitHub Copi­lot inves­ti­ga­tion by frumper on Tuesday October 18, 2022 @11:55AM (#33249349)
Cannot is a strong term. Telling me there may be consequences would be more accurate.
[ Parent | on HN ]
Re:GitHub Copi­lot inves­ti­ga­tion by abigail95 on Tuesday October 18, 2022 @01:17PM (#33250769)
I can claim fair use and short of an injunction there's nothing you can do to stop me.
[ Parent | on HN ]
Re:GitHub Copi­lot inves­ti­ga­tion by ranguna on Wednesday October 19, 2022 @03:43AM (#33258936)
Claiming fair use is not a fix all card you can play like that, there are a lot of nuences for that to hold on trial.
[ Parent | on HN ]
Re:GitHub Copi­lot inves­ti­ga­tion by kbelder on Tuesday October 18, 2022 @06:27PM (#33254916)
I'm allowed to read it and learn from it. To distill the core concepts and recreate it.
[ Parent | on HN ]
Re:GitHub Copi­lot inves­ti­ga­tion by ranguna on Wednesday October 19, 2022 @03:42AM (#33258929)
You as a human being, not you as a for profit company building a for profit product.
[ Parent | on HN ]