Earlier quoted context omitted.
+1. And let's not forget too that "AI", that is, ML models, are not "autonomous" in the way that humans are autonomous. Sure, we use the word "learn" to describe what they do, which is one word that we also use to describe what people do. But ML models are always wielded by people or corporations for particular purposes. If a corporation was to directly publish some copy that appears plagiarized, we'd call that plagi…
A lot of really good points. >Sure, we use the word "learn" to describe what they do, which is one word that we also use to describe what people do. But ML models are always wielded by people or corporations for particular purposes. This is extremely important. "Learning" in machine learning is an aspirational label, not a descriptive one. People who claim otherwise either drank too much of their own Kool-Aid or are…
GitHub Copilot investigation
901–910 of 1001 posts
Re: GitHub Copilot investigation
#902Earlier quoted context omitted.
You're not supposed to be able to use dominance in one market (git hosting) to gain dominance in another (AI powered code suggestions).
That might be true, if GiHub were a monopoly. But they are not.
Just because there is some existing competition which has a few percent marketshare and technically it's not a monopoly doesn't materially change anything besides a pro forma excuse. Which is why Google have been propping up Mozilla, they want the excuse "but technically there's another browser". However for consumers and the market it doesn't matter that technically there's an option that practically nobody uses.
Re: GitHub Copilot investigation
#903Unfortunately the tone I'm getting from many of these comments makes me feel that people see open source projects as a resource to be mined rather than as a product to be respected. A very entitled attitude ("I really don't want to lose my lovely tool") There seems to be -- on the whole -- little respect for the spirit of the GPL and LGPL and it really is quite a change from, say, 20 years ago, when the 'free softwar…
What do you expect when people grant GitHub an extra license to their repos[0]? 0: https://docs.github.com/en/site-policy/github-terms/github-t...
Re: GitHub Copilot investigation
#904Unfortunately the tone I'm getting from many of these comments makes me feel that people see open source projects as a resource to be mined rather than as a product to be respected. A very entitled attitude ("I really don't want to lose my lovely tool") There seems to be -- on the whole -- little respect for the spirit of the GPL and LGPL and it really is quite a change from, say, 20 years ago, when the 'free softwar…
What do you expect when people grant GitHub an extra license to their repos[0]? 0: https://docs.github.com/en/site-policy/github-terms/github-t...
Re: GitHub Copilot investigation
#905Re: GitHub Copilot investigation
#906Earlier quoted context omitted.
So many comments like this, but none list a tangible harm that's anywhere near the millions of man hours systems like this will save. Heck, basically none (including this one!) list a harm at all!
You could say this about all software piracy. So Microsoft can work to end software copyright instead of trying to corner the market on pirated software and asking forgiveness after the fact.
Because most software piracy is of saleable software. 20 line snippets are not for sale, mostly because the transaction costs are higher than the snippet value.
Re: GitHub Copilot investigation
#907Earlier quoted context omitted.
Humans do violate copyright if they use copyrighted passages directly in their work and pass it off as their own without any attribution, which is what copilot has been show to sometimes do, though not always. Copilot will sometimes offer chunks of code that can be found verbatim in open source code bases and passes it off to users without attribution. I agree it is ok to learn from copyrighted work and reproduce new…
> which is what copilot has been show to sometimes do In those cases it seems that humans are already copying code without also propagating licenses appropriately. LLMs are more likely to memorize things which occur a lot (and I'd bet rare things that are representative of some conceptual axis). The main examples presented so far, Davis and Carmack, have the property of having been copied a lot. The generative model…
This is quite important, actually, and I don't think enough people realize this. I am a photographer sometimes and it would be really cool if I could share my photos online under a copyright license that forbids their use in training AI.
Re: GitHub Copilot investigation
#908It will be interesting to see where this goes.
Re: GitHub Copilot investigation
#909Earlier quoted context omitted.
> It would be sad if someone succeeded in shutting down CoPilot for this kind of copyright stuff. It enables the large scale theft of code. It completely ignores licenses. There are plenty of open source licenses that allow code use with proper attribution yet Copilot doesn't (and probably can't) figure a way to comply with all of them. Copilot, as the article suggests, is a marketing stunt. To me it's more than that…
So many comments like this, but none list a tangible harm that's anywhere near the millions of man hours systems like this will save. Heck, basically none (including this one!) list a harm at all!
Seems like a pretty tangible harm to me.
Re: GitHub Copilot investigation
#910Unfortunately the tone I'm getting from many of these comments makes me feel that people see open source projects as a resource to be mined rather than as a product to be respected. A very entitled attitude ("I really don't want to lose my lovely tool") There seems to be -- on the whole -- little respect for the spirit of the GPL and LGPL and it really is quite a change from, say, 20 years ago, when the 'free softwar…
But the show-stopping problem is that copilot is sometimes producing code that is more than fair use of other code that, and is unable to attribute the code or identify how that code is licensed. It is copilot's (Microsoft's) fault that it auto-generates legal minefields, not the person who made an informed decision about licensing their own code.
In spite of the likely downvoting, I'll say that people should be grateful for reciprocal licenses not just because they were and are the foundation of free software (as you point out), but because they shine a light on what it means to license code, and how we are forced to revisit the difference between copyright and licensing when a reciprocal license is violated.