News for hackers. Stuff that matters.

A comment on Copilot regurgitating Quake code, including sweary comments. Parent comment

Re:Copilot regurgitating Quake code, including sweary comments by runeb on Friday July 02, 2021 @02:14PM (#27714843)
How would they do that?
[ Parent | on HN ]
Re:Copilot regurgitating Quake code, including sweary comments by oauea on Friday July 02, 2021 @04:18PM (#27716359)
Read the LICENSE file in each repo.
[ Parent | on HN ]
Re:Copilot regurgitating Quake code, including sweary comments by rovr138 on Friday July 02, 2021 @06:03PM (#27717498)
What guarantees it’s intact?
[ Parent | on HN ]
Re:Copilot regurgitating Quake code, including sweary comments by willis936 on Friday July 02, 2021 @10:40PM (#27718947)
It doesn't need to be. If the license isn't positively exactly permissive then you can't use it.
[ Parent | on HN ]
Re:Copilot regurgitating Quake code, including sweary comments by hermitdev on Sunday July 04, 2021 @02:23AM (#27727633)
Can you even trust that the License in a random repo is accurate and expresses the actual copyright of all the contained code?

I guess my point is, you can't be positive that even if you're following the license in a repo you forked that the repo owner hasn't already violated someone else's license, and now transitively, so have you.

[ Parent | on HN ]
Re:Copilot regurgitating Quake code, including sweary comments by icebraining on Sunday July 04, 2021 @03:22AM (#27727878)
> Can you even trust that the License in a random repo is accurate and expresses the actual copyright of all the contained code?

In fact, that seems to be exactly the problem shown in the tweet - someone copy-pasted the quake source and slapped a different license on it, and copilot blindly trusted the new license.

[ Parent | on HN ]