News for hackers. Stuff that matters.
Re:GitHub Copi­lot inves­ti­ga­tion by smt88 on Monday October 17, 2022 @07:12PM (#33240757)
Copilot wouldn't be shut down or neutered because "a few vocal people" protested against it.

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.

You act like Microsoft is trying to do a public service and people are angry about it. The reality is that they're taking billions of hours of work and using it to build a product that only they control.

If they re-released Copilot as FOSS, a lot of the valid criticisms would evaporate.

Re:GitHub Copi­lot inves­ti­ga­tion by beebmam on Monday October 17, 2022 @07:27PM (#33240920)
Why should Copilot engineers, and the company that invests in it, not be rewarded for their incredible product and SaaS offering they spend resources on providing?
Re:GitHub Copi­lot inves­ti­ga­tion by lucasyvas on Monday October 17, 2022 @07:47PM (#33241125)
Are you a bot? The accusation is that they've built their offering on theft. They are entitled to nothing in that case. Incredible product?
Re:GitHub Copi­lot inves­ti­ga­tion by visarga on Monday October 17, 2022 @07:56PM (#33241189)
That's not theft. Was the original code deleted? No. Then it's copying. And not even that, is the model replicating the training set like Google search? No. Then it's some kind of derivative work. And especially for Github it's OK because user agreements allow MS to do it.

Is "imagining" the same with "copying"? Does copy-right cover learning-right? Can learning and practicing be restricted by the authors? Can visual styles, algorithms and facts be copyrighted? I say no to all of them.

Re:GitHub Copi­lot inves­ti­ga­tion by batmanturkey on Monday October 17, 2022 @08:34PM (#33241517)
It’s not about “learning” at all, copilot spits out copyrighted licensed code verbatim directly copied from the source to your project in violation of specific and multitudinous repositories.

They are making rips of other peoples stuff, selling the contents of peoples “books/movies/songs” sans author attribution or album credits etc… to put it in terms you may be familiar with Vinegar and salt on open wounds. Bad

Re:GitHub Copi­lot inves­ti­ga­tion by seadan83 on Tuesday October 18, 2022 @12:43AM (#33243059)
Is there any nuance for scope? Software I've licensed as GPL, I'm concerned about the working software being re-used and re-licensed for something commercial. For a given method out of tens-of-thousands, it's very not-germaine to the overall software to the point that I don't see it is a really relevant (but that is my opinion). Though, if someone likes the opening sentence of the encylopedia (or some other giant work), and an AI says, "this is a good opening sentence - does that really make for "ripping" off? Isn't the covered work the larger contents of the encylopedia, rather than an arbitrarily well written opening sentence? Isn't the big part of the work the ensemble?

I'm starting to wonder about these arguments, and whether we've gone into bad faith and hyperbole territory here. Are algorithms subject to copyright? Is it the case that if a GPL work uses a well known algorithm, that GPL work cannot be used as a reference? (Given that algorithms have very limited forms they can take, using an algorithm as a reference is really just copying it. Even translating pseudo-code to code, it's still the same thing).

Can you explain to me how something like using Eulers formula to solve a math problem would not be copyright infringement? A GPL project might use that formula somewhere, but then using that would be a copyright violation?

How about HTML source code, does putting a 'copyright' notice on the webpage make it invalid to then use any of the javascript, even if it has nothing special to do with the domain of the website?

"selling the contents of peoples “books/movies/songs”

Going to this analogy, I don't know if it is really the contents, but more like the first sentence, or even the first few words of that sentence rather than any recognizable subset of that work.

Like, if I have an app that does a spreadsheet, I don't care if you take an implementation of quick sort from my code as reference, but I do care if you use the same and main features of the spreadsheet app that I made.

Re:GitHub Copi­lot inves­ti­ga­tion by abigail95 on Tuesday October 18, 2022 @03:36AM (#33244153)
Whether verbatim copying infringes copyright can only be determined by a court, and only on a case by case basis.

Anyone saying "in violation" without doing a fair use test doesn't know how copyright works.

Re:GitHub Copi­lot inves­ti­ga­tion by lucasyvas on Monday October 17, 2022 @08:16PM (#33241382)
Human's aren't even allowed to do this. It has to be done clean room - this is not learning, it's copying and has been proven so.

The only implementation that would be allowed is if they had to describe the code via a specification and Codepilot was able to generate it from scratch. It does not do that - it just reorganizes stuff it's already seen, which is a copyleft violation in humans, therefore it should be for a machine created by humans.

The code has had its license violated.

Re:GitHub Copi­lot inves­ti­ga­tion by visarga on Monday October 17, 2022 @08:38PM (#33241542)
> It has to be done clean room

That's for patents not for copyrights. All you need to do is make it a little different, generate until satisfied for patent safe code. Another model can also do the patent checking.

Re:GitHub Copi­lot inves­ti­ga­tion by lucasyvas on Monday October 17, 2022 @08:41PM (#33241573)
I've heard multiple stories from people who can't even look at the Linux source before they do something in their company's kernel because the act of just looking at it compromises them legally. So which is it?
Re:GitHub Copi­lot inves­ti­ga­tion by visarga on Tuesday October 18, 2022 @01:01AM (#33243161)
Clean room implementation only happens for very special codes, like codecs or efficient matrix multmul that took billions of trials to develop with AI. Not for 2-3 lines of code snippets that do one simple thing and are already covered online in hundreds of places.
Re:GitHub Copi­lot inves­ti­ga­tion by int_19h on Monday October 17, 2022 @10:18PM (#33242210)
One of the canonical examples of software reverse engineering is Phoenix Technologies producing a compatible BIOS for IBM PC. They did exactly what OP described - had one person look at (public but copyrighted) IBM source and produce an extremely detailed design document, then another team went and wrote a new BIOS from scratch following that document. The issue at hand was copyright, not patents.
Re:GitHub Copi­lot inves­ti­ga­tion by jacooper on Monday October 17, 2022 @08:05PM (#33241284)
I think he is using theft because currently piracy(which is basically copying files) is legally considered theft.
Re:GitHub Copi­lot inves­ti­ga­tion by larsiusprime on Monday October 17, 2022 @08:32PM (#33241498)
Larceny and copyright infringement are two distinct legal categories for two distinct kinds of crimes. One involves a taking of property and the other involves the violation of a government granted monopoly
Re:GitHub Copi­lot inves­ti­ga­tion by noasaservice on Monday October 17, 2022 @07:48PM (#33241133)
Are they following All the licenses they are consuming?

Why haven't they uploaded Windows source to Copilot?

Just how much code reproduced violates copyright?

If, instead of Copilot, Bob was giving me code to copy, and it was a AGPL codebase, am I still subject to the AGPL?

Re:GitHub Copi­lot inves­ti­ga­tion by nine_k on Monday October 17, 2022 @07:58PM (#33241208)
They built it using some publicly available resources. These resources are available conditionally, subject to licenses (such ad GPL). Which is fine.

The problem is that their product sometimes produces verbatim copies of licensed works, without attaching licensing information. This not only goes against the licenses under which the original authors made these works available. It can also put the product's users in danger of anything from bad publicity to a copyright lawsuit.

CoPilot is a very interesting research project. It's not yet an acceptably mature product though.

Re:GitHub Copi­lot inves­ti­ga­tion by Spivak on Monday October 17, 2022 @07:27PM (#33240919)
> If they re-released Copilot as FOSS, a lot of the valid criticisms would evaporate.

That changes nothing at all. A FOSS license is, in a legal sense, no different then a proprietary one. If it’s illegal it’s illegal regardless of whether it’s FOSS.

Re:GitHub Copi­lot inves­ti­ga­tion by rockemsockem on Monday October 17, 2022 @07:32PM (#33240971)
I mean, legally, yes, but the point at issue was public outcry, which has almost nothing to do with laws.

If Copilot was FOSS there'd probably be a few absolutists complaining, but they'd be mostly ignored.

Re:GitHub Copi­lot inves­ti­ga­tion by btdmaster on Tuesday October 18, 2022 @04:03AM (#33244339)
If Copilot is deemed a derivative work of its inputs, it would resolve the issue that it does not comply with the AGPL because it currently does not provide source code to its users under an AGPL-compliant license.
Re:GitHub Copi­lot inves­ti­ga­tion by scarface74 on Monday October 17, 2022 @07:20PM (#33240843)
> 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?

Re:GitHub Copi­lot inves­ti­ga­tion by lbotos on Monday October 17, 2022 @07:25PM (#33240901)
Wait, I'm not sure what you are trying to say? Can you clarify?
Re:GitHub Copi­lot inves­ti­ga­tion by scarface74 on Monday October 17, 2022 @07:29PM (#33240936)
That many people who are criticizing Microsoft for using open source code and claiming “fair use” and saying it’s not fair to creators are the same ones that say pirating digital content is harmless.
Re:GitHub Copi­lot inves­ti­ga­tion by pornel on Monday October 17, 2022 @08:27PM (#33241461)
Because issues aren't automatically symmetrical, and impact of actions isn't equal in both ways, especially when there's power difference between the sides of the conflict, e.g. it's not hypocritical to punish a bully punching their victim, but not the victim for punching the bully back.

Disney used its power to distort copyright laws in a self-serving manner. As an individual you don't have equal power to oppose them (you were supposed to have in a democracy, but lobbying is legal and corporations are people).

Disney is a huge corporation that won't even notice if you pirate a movie, which you may not even have been able to pay for anyway, because of their region-locked twisted maze of distribution and DRM.

OTOH you may be screwed if you're a creator making a living from your work, and a big corp can just take it without paying, launder it through "… in the style of $YOURNAME" query, and say they own it now, because unlike your copyright, their Terms Of Service apply.

Even people who think copyright shouldn't exist may rely on using copyright — against itself. You can't unilaterally say "I don't believe in copyright", because the law doesn't care, but if you license something as copyleft, then the law does care about your anti-copyright license.

Re:GitHub Copi­lot inves­ti­ga­tion by numpad0 on Monday October 17, 2022 @09:04PM (#33241749)
There’s an assumption that hackers are automatically anarcho-communist, and unconditionally, wholeheartedly, vocally supportive of content piracy, which is not correct.
Re:GitHub Copi­lot inves­ti­ga­tion by concordDance on Tuesday October 18, 2022 @04:12AM (#33244389)
Hackers mostly are, but Hacker news is mostly frequented by bog standard developers, who mostly aren't.
Re:GitHub Copi­lot inves­ti­ga­tion by Spivak on Monday October 17, 2022 @07:30PM (#33240943)
I don’t think anyone at all is here arguing that an AI trained on a massive corpus of movies that outputs snippets of film based on a prompt would be illegal. Such a thing would literally be the same as Midjourney with images. The fact that you can likely coax any AI to output snippets close to some of the source material is not likely to really matter and would be as if you recreated a copyrighted work using any other tools.
Re:GitHub Copi­lot inves­ti­ga­tion by scarface74 on Monday October 17, 2022 @07:41PM (#33241074)
What’s the difference here then?
Re:GitHub Copi­lot inves­ti­ga­tion by yarg on Monday October 17, 2022 @07:53PM (#33241169)
It'd probably turn towards Disney's history of bribing congress for copyright extensions whenever the mouse is about to enter the public domain.
Re:GitHub Copi­lot inves­ti­ga­tion by scarface74 on Monday October 17, 2022 @08:06PM (#33241296)
The same copyright laws that the open source proponents are complaining about MS breaking?
Re:GitHub Copi­lot inves­ti­ga­tion by drstewart on Monday October 17, 2022 @08:32PM (#33241500)
There is a certain amount of irony that a likely possible outcome will be the strengthening of copyright laws and enforcement, at which point people will realize they won the battle but lost the war
Re:GitHub Copi­lot inves­ti­ga­tion by yarg on Monday October 17, 2022 @08:59PM (#33241710)
The problem with copyright isn't that it exists and provides protections - this incentivises creators.

But life of the creator + 70 years?

Reminds me of this:

https://arstechnica.com/uncategorized/2007/07/research-optim...

https://papers.ssrn.com/sol3/papers.cfm?abstract_id=1436186

Re:GitHub Copi­lot inves­ti­ga­tion by shagie on Monday October 17, 2022 @09:34PM (#33241950)
But isn't it copyright upon which open source is founded? The license is based on the right of the owner of the copyright to authorize someone else to create a derivative work?

Without copyright, it would be perfectly legitimate and legal for someone to not follow a license (because it would bear no legal weight because of the lack of copyright).

I would argue that open source is best served by strong copyright protections that allow the people created the software to make sure that further changes to it are released back to the community. Weakening copyright law means that it is that much easier for big companies to co-opt some software and not need to release the changes back.

Re:GitHub Copi­lot inves­ti­ga­tion by yarg on Monday October 17, 2022 @08:19PM (#33241401)
Steamboat Willie was released in 1928.

People probably would have less of a problem if microsoft breached the license on 100 year old code.

Re:GitHub Copi­lot inves­ti­ga­tion by klyrs on Monday October 17, 2022 @09:18PM (#33241849)
> The same copyright laws that the open source proponents are complaining about MS breaking?

As long as Microsoft can and will wield those laws against me? Darn tootin'

Re:GitHub Copi­lot inves­ti­ga­tion by tzs on Monday October 17, 2022 @10:44PM (#33242387)
That's a bit of an exaggeration. There have only been two copyright term extensions since Mickey Mouse was created, and only one of those can even remotely be attributed to Disney lobbying.
Re:GitHub Copi­lot inves­ti­ga­tion by kmeisthax on Tuesday October 18, 2022 @12:14AM (#33242888)
Even for the term extension that is attributable to Disney, you can also attribute it to Germany and the formation of the EU. "Mickey Mouse Protection Act" is funny, yes, but also an oversimplification.

This is also why I fully expect Steamboat Willie to fall out of copyright protection in January 2024 - right on schedule. There's a few countries that have supra-EU copyright terms, but none of them are dealmakers. Nobody is demanding we match Mexico's life+100 terms, for example.

Re:GitHub Copi­lot inves­ti­ga­tion by reachableceo on Monday October 17, 2022 @08:37PM (#33241535)
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 enumeration of the permissions (or lack thereof ) for a work.

This class action lawsuit should surprise nobody. It’s a class that is sick and tired of being exploited.

Do not take my work that I contributed with explicit permissions and use it in a way I didn’t grant permission for. Full stop. It isn’t complicated.

You wouldn’t download a car and all that jazz….

Re:GitHub Copi­lot inves­ti­ga­tion by naikrovek on Monday October 17, 2022 @09:53PM (#33242064)
> The courts tend to take a dim view of theft. Which is what this is.

https://docs.github.com/en/site-policy/github-terms/github-t...

so much animosity over rights you gave GitHub when you put your code there. "Theft" gimme a break. you license your code to GitHub so they can show it to others. This is separate to the stated license in your code. Nowhere in that terms of service document are the means that the code is shown to users specified.

Re:GitHub Copi­lot inves­ti­ga­tion by cycomanic on Tuesday October 18, 2022 @01:25AM (#33243274)
Give me a break. Did you even read the license? You read that it is restricted to "the service". That service cannot be copilot, because it didn't even exist when most people agreed to the license. Moreover the license explicitly states they cannot use the code to distribute in any other way or sell it. So if anything they are violating their own agreement.

Also MS themselves don't even claim that training is covered by their terms of service, they claim it is fair use.

Re:GitHub Copi­lot inves­ti­ga­tion by abigail95 on Tuesday October 18, 2022 @03:31AM (#33244121)
What do you think is more likely, that Microsoft stuffed their own terms and conditions?

Or you are mistaken and "the service" of github, includes all features available on the website including copilot.

Even if you're right and a court rules against them, what's to stop them changing the terms to become compliant?

Re:GitHub Copi­lot inves­ti­ga­tion by cycomanic on Tuesday October 18, 2022 @06:55AM (#33245430)
? Did you read what I wrote, MS doesn't even claim copilot is covered by their terms. They claim it is covered by fair use (some people also claimed there is code not hosted by GitHub in copilot, which would further confirm that they believe they are covered by something else)

Moreover terms have been largely unchanged for years AFAIK. If someone agreed to the license years ago, they can't have agreed to copilot use. Also copilot is not a service on their website, it is a separate service and they charge for it, also contradicting the terms.

Re:GitHub Copi­lot inves­ti­ga­tion by abigail95 on Tuesday October 18, 2022 @07:43AM (#33245827)
If you think I'm mistaken I will gladly reevaluate what I said if you could kindly restate your position, by answering a few questions

What does separate service mean? What would Copilot look like if it was not separate?

Elaborate on "not a service on their website", as it is available and listed as a feature "Github Copilot" on their website.

Is the contradiction related to payment for the service, or just because you think it is separate?

Since I thought you were arguing that Githubs own terms prevent them from using the public repositories in Copilot, this is what I argued against.

If you think fair use is involved, then that's the end of the line. If MS claims fair use, then until a court says otherwise, it is. Anyone who thinks their copyright is being violated can get an injunction tomorrow.

Re:GitHub Copi­lot inves­ti­ga­tion by skydhash on Tuesday October 18, 2022 @09:08AM (#33246546)
> What would Copilot look like if it was not separate?

Maybe some type of hint shown inside your code when it’s shown at github.com. There is already a text editor.

Re:GitHub Copi­lot inves­ti­ga­tion by naikrovek on Tuesday October 18, 2022 @01:10PM (#33250672)
> They claim it is covered by fair use

they claim the training of their model is covered by fair use, but they did not say that was the justification they were using. They don't need to claim fair use.

It's pretty clear from the Terms of Use that they can use code hosted on github.com to provide any service they like, so long as it is a GitHub service. They don't need fair use, they already have the rights to do what they are doing.

Re:GitHub Copi­lot inves­ti­ga­tion by abigail95 on Monday October 17, 2022 @11:21PM (#33242594)
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 by reachableceo on Monday October 17, 2022 @11:58PM (#33242803)
If my code is licensed under terms , that’s the permission .

If you use my licensed work then yes, you do need to follow the terms of the license .

The issue of license / contract / copyright is messy. It doesn’t ever seem (in the USA anyway ) to be definitively answered / “solved.”

I chose AGPL v3 only on purpose.

Co pilot and users thereof (so now two levels removed ) utilizing code in whatever work are stealing my work (unless it’s AGPL v3 licensed ). The adding of intermediaries (and the most likely unknown and with no way to know) infringing is going to be very difficult to mitigate. It’s like truly unknowingly buying stolen property,

Re:GitHub Copi­lot inves­ti­ga­tion by abigail95 on Tuesday October 18, 2022 @03:29AM (#33244100)
No I don't have to follow your license.

If I use it under fair use, there is nothing you can do about it.

The fourth factor of fair use is the effect on the value of your work. If I'm not affecting the works value because there is no market for it, because it has no commercial value, you are going to have a very hard time defeating this argument in court.

Re:GitHub Copi­lot inves­ti­ga­tion by int_19h on Monday October 17, 2022 @10:11PM (#33242176)
I don't think many people here would object if Copilot was trained on all the publicly available source code from before 1930.
Re:GitHub Copi­lot inves­ti­ga­tion by deworms on Monday October 17, 2022 @07:34PM (#33240985)
You have an agenda you're pushing and pretending it's a foregone conclusion.

No it doesn't violate any licenses, most open source licenses are a meme and are never enforced; people copypaste code all the time with no consequences, and you can't stop any of it, Copilot or not.

And no they are not "taking billions of hours of work", what's that even supposed to mean? If you don't want your code to be publicly available, how about you don't post it on the internet?

Re:GitHub Copi­lot inves­ti­ga­tion by noitpmeder on Monday October 17, 2022 @07:44PM (#33241102)
It definitely does violate licenses -- this is true EVEN WHEN the repo they pulled it from is the original violator.
Re:GitHub Copi­lot inves­ti­ga­tion by rwalle on Monday October 17, 2022 @08:09PM (#33241322)
Well... If you do a search you'll find that there are actually lots of lawsuits related to open source license violation, mostly around GPL license. Maybe educate yourself first
Re:GitHub Copi­lot inves­ti­ga­tion by batmanturkey on Monday October 17, 2022 @08:29PM (#33241476)
Your assertion thst copyright doesn’t matter and that people should “get used to it” is… pretty incorrect on the former (surely there are still pending copyright suits on earth circa 2022) and ill-conceived on the latter (I’ll just rob your house while you sleep and you should just get used to it)
Re:GitHub Copi­lot inves­ti­ga­tion by nathanaldensr on Monday October 17, 2022 @09:09PM (#33241790)
Your comment amounts to "sometimes crime occurs; therefore, laws are pointless."`
Re:GitHub Copi­lot inves­ti­ga­tion by visarga on Monday October 17, 2022 @07:49PM (#33241138)
> 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.

Copilot makes source code much more open, if you think about it. It implements code reuse in a different way than classes and libraries. It offers its skills equally to everyone, skills learned from everyone.

As for the cost of the API - it's expensive to run large language models, I think the price is justified. But there are free models if you like to run your own.

Re:GitHub Copi­lot inves­ti­ga­tion by yjftsjthsd-h on Monday October 17, 2022 @07:54PM (#33241182)
And if it preserves licenses that's fine. Otherwise it's copyright infringement.
Re:GitHub Copi­lot inves­ti­ga­tion by jacooper on Monday October 17, 2022 @08:02PM (#33241254)
Free/libre software ≠ free as beer.
Re:GitHub Copi­lot inves­ti­ga­tion by quickthrower2 on Monday October 17, 2022 @08:49PM (#33241632)
They should in addition release all code generated as a combo of AGPL, GPL, MIT, etc. and put a comment on every usage. Users would then need to license their code accordingly.

For a commercial version, run it on Microsoft's internal code, the code they actually own!

Re:GitHub Copi­lot inves­ti­ga­tion by Aeolun on Monday October 17, 2022 @09:04PM (#33241751)
> 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.

Yeah, the vocal few.

Do you think I give a rats ass that Copilot is duplicating my OS code?

I have to imagine most people are completely ambivalent. Of course I have no proof, I just can’t imagine anything else.

The lines probably fall somewhere along the MIT vs GPL camps.

Re:GitHub Copi­lot inves­ti­ga­tion by smt88 on Monday October 17, 2022 @09:39PM (#33241978)
> Of course I have no proof, I just can’t imagine anything else.

"Ambivalent" means "of two minds," but I'm going to assume you meant that you're indifferent.

If people are/were indifferent, their licenses should reflect that. They overwhelmingly don't.

Regardless, Microsoft is legally bound to obey the licenses.

Re:GitHub Copi­lot inves­ti­ga­tion by seadan83 on Tuesday October 18, 2022 @12:55AM (#33243121)
I consider GPL as meaning, "don't make the same app as me using this very source code". Cribbing one method out of quarter million line code-base, hardly seems to be redistributing the source code. Literally, it is, but is there no concept scale? Can we go to an extreme and force anyone with a `catch(Exception e)` line in their Java code to go and prove they did not take it from a GPL (or similarly licensed project)? I think this indicates there is a line, at some point it is enough code where you are recreating the functionality of the software - to me that is the thing that matters. I don't give a crap if you use my GPL code to learn from and use any parts of it to build whatever software, but I do care if you recreate the same software using my GPL code.

I would accept a claim of license violation if someone used copilot to autocomplete so many methods from one specific project that you have recreated that original project.

I still think it is a matter of scope. It can still be the case that a relatively small module is not cool to lift, but I think in this case we are still talking about such small subsets of functionality that it is completely divorced from the original software. Like, I could see it if a specific method were really key in some way to a unique application, a very novel solution to a difficult problem - but if that were the case, how can an AI possibly use that for a training model? In other words, the auto-suggestions of an AI are going to be common coding solutions to common coding problems that the AI has seen hundreds of thousands of times. That individual proprietary GPL, unique and novel solution is not really the stuff of an AI suggestion. In other words, the code that co-pilot is going to suggest is going to be non-unique, generic, and not really specific to the overall application at all.

Re:GitHub Copi­lot inves­ti­ga­tion by abigail95 on Tuesday October 18, 2022 @04:48AM (#33244611)
What contract does Microsoft have with the license holders that would force them to obey the license?
Re:GitHub Copi­lot inves­ti­ga­tion by Aeolun on Wednesday October 19, 2022 @06:12AM (#33259949)
Good point, I meant indifferent.

> If people are/were indifferent, their licenses should reflect that. They overwhelmingly don't.

Apparently, overwhelmingly they do. At least if the licenses used are any indication.

https://github.blog/2015-03-09-open-source-license-usage-on-...

Re:GitHub Copi­lot inves­ti­ga­tion by nathanaldensr on Monday October 17, 2022 @09:08PM (#33241782)
The funny thing is that even the MIT license requires attribution, which of course Copilot doesn't provide.
Re:GitHub Copi­lot inves­ti­ga­tion by concordDance on Tuesday October 18, 2022 @04:13AM (#33244401)
> 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'm almost entirely certain you're wrong about the desires bit. 99% of the developers who wrote that code won't mind.

Re:GitHub Copi­lot inves­ti­ga­tion by shuger on Tuesday October 18, 2022 @07:21AM (#33245645)
> 99% of the developers who wrote that code won't mind

This is completely unsubstantiated. I for one would mind microsoft profiting from the closed source code I wrote.