Live data from Hacker News

GitHub Copi­lot inves­ti­ga­tion

githubcopilotinvestigation.com

521–530 of 1001 posts

Re: GitHub Copi­lot inves­ti­ga­tion

#521

Copilot is trained on and returns AGPL code verbatim. It’s game over. If these licenses are not enforced it defeats the entire purpose.

The vast majority of GPL violations are not enforced, because those who would want to enforce them are small and their opponents are big.

For Copilot to blow up, it'd need to be licensed code from a big company demonstrably turning up in a product of a competitor, or some similar event.

Re: GitHub Copi­lot inves­ti­ga­tion

#522

Earlier quoted context omitted.

As a human, if I learn how to program by studying copyrighted code, is it unethical for me to use that knowledge to make a living ?

The difference is this, you’re likely working for the company whose proprietary code you’re working on and using as a “training model” while contributing to the greater good of that codebase. You’ve been authorised to see this code.

I learned to code when a misconfigured CGI server spit out an application's code (it was written in Perl) instead of executing it. While that starts going down the long and complicated road of whether or not the machine is acting definitively, I think for our purposes here we can assume that the intent was for me to not have access to the code.

Re: GitHub Copi­lot inves­ti­ga­tion

#523
post #491

It would be sad if someone succeeded in shutting down CoPilot for this kind of copyright stuff. It is genuinely useful. I don't care that it reproduces copyrighted content. The only way you can get it to do that is to bait it with the function names of functions that have already been copy and pasted thousands of times onto GitHub without proper licenses. Luckily, someone will probably come out with a "renegade" vers…

If it was also free and open source, sure. But it's not, it's a paid product that one party reaps the profits from.

Re: GitHub Copi­lot inves­ti­ga­tion

#525
post #247

There are two issues -- (1) feeding copyrighted material in to an AI model, and (2) getting copyrighted material out . The latter is obviously a violation of copyright, full stop. The former, to me, is obviously not a violation. If it were, that would massively tilt the playing field in favor of large corporations. It would become very hard to independently train your own models. Philosophically, I go by the principl…

> There are two issues -- (1) feeding copyrighted material in to an AI model, and (2) getting copyrighted material out. > The latter is obviously a violation of copyright, full stop. It's not obvious to me that (2) is a violation of copyright. Unlike patents, copyright violation is not as simple to prove. My understanding is that, at least in the US, independent creation is a valid defense against copyright infringem…

> For example if 2 people independently write the same story and can prove that they did, they can both hold copyright over that story.

This is the theoretical case but I don't think I've ever seen that actually happen in practice.

Re: GitHub Copi­lot inves­ti­ga­tion

#526

Earlier quoted context omitted.

As a human, if I learn how to program by studying copyrighted code, is it unethical for me to use that knowledge to make a living ?

Unless Microsoft is secretly powering Copilot with Mechanical Turk, that isn't what's happening here.

Why not complete that analogy?

What if instead of Copilot, it was a bunch of humans who were searching all the source code they could access and then copying/autocompleting that code, regardless of the license.

Is that still OK? If yes, why?

Re: GitHub Copi­lot inves­ti­ga­tion

#527
Sadly, I think this marks the beginning of a winner-takes-all economy fueled by AI.

Just imagine how in a lawsuit like this, OpenAI can use GPT-3 to generate eloquent court speech with statistical confidence that it can defeat human lawyers? It just comes down to TPU power.

Re: GitHub Copi­lot inves­ti­ga­tion

#528

Earlier quoted context omitted.

> It would be because it's illegal and violates the licenses, desires, and intentions of the thousands of workers who wrote the code in its corpus. I wonder how many people on HN would be on the side of the creators if we were talking about content created by Walt Disney and whether pirating was ethical?

Equal protection under the law. I am 100% on the side of content creators. Regardless of who they are . The courts tend to take a dim view of theft. Which is what this is. The article clearly lays out that multiple requests for sound legal basis have gone unanswered . It simply doesn’t exist and Microsoft is operating on a forgiveness vs permission model. Licensing is 100% about permissions. Clear and explicit enumer…

It's not full stop didn't grant permission.

Fair use is a major part of copyright law. I do not have to ask permission to use your work.

For you to win in court you have to overcome fair use, you have to overcome innocent infringer, you have to overcome no damages.

Anyone leaving comments saying that there's an obvious way a court would rule on a copyright case involving those 3 things is wrong.

Re: GitHub Copi­lot inves­ti­ga­tion

#529
A sizable, possibly plurality cohort of fully adult tech people is young enough to not know about United States v. Microsoft Corp. This would explain a lot of comments I see on this topic.

If you don't know Microsoft's history, a lot of what more informed people are worried about seems overblown. Copilot was Microsoft's first test of people's trust after the GitHub acquisition. It's going very, very, very poorly. There were ways to do this with consent and collaboration with the people and projects it takes code from, but they're acting like classic Microsoft here.

Too many people are focused on what's legal. It's fine to think of, but law is the last stop before the breakdown of society. Microsoft skipped society and went straight to sparking an inevitable test of and possible reshaping of copyright law.

Re: GitHub Copi­lot inves­ti­ga­tion

#530
post #491

It would be sad if someone succeeded in shutting down CoPilot for this kind of copyright stuff. It is genuinely useful. I don't care that it reproduces copyrighted content. The only way you can get it to do that is to bait it with the function names of functions that have already been copy and pasted thousands of times onto GitHub without proper licenses. Luckily, someone will probably come out with a "renegade" vers…

> It would be sad if someone succeeded in shutting down CoPilot for this kind of copyright stuff. It is genuinely useful. I don't care that it reproduces copyrighted content. Sure — in the same way that hacking into a competitor's GitHub account and copying their private source code is "genuinely useful" to you. As the person benefitting from unlawfully using their source code, of course you wouldn't care that it rep…

I use Copilot all the time and I’ve never once used it to generate a whole prepackaged function that’s more than maybe three lines. So no, I don’t benefit from its reproducing other people’s code at all. Tell me you don’t use Copilot without telling me about it.
Post reply on HN