Earlier quoted context omitted.
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 t…
Quoted post unavailable.
GitHub Copilot investigation
231–240 of 1001 posts
Re: GitHub Copilot investigation
#232What do people think the future looks like where publicly available resources on the Internet (art, code, etc) aren't fair use for training ML models? Where you have to opt into models or can opt out (and many wind up doing so)? OpenAI, Microsoft, Google, et al will STILL train such models that can do all the same things, but it will be much harder for non-industry-backed individuals to navigate the legal minefield w…
Any law where the penalty is a fine only exists for the poor. Any regulation where the penalty is in the millions only exists for small businesses.
Re: GitHub Copilot investigation
#233Re: GitHub Copilot investigation
#234Earlier quoted context omitted.
> "look I prompted CoPilot for this piece of code that I already knew about and it spit it right out" https://twitter.com/docsparse/status/1581461734665367554 An english description plus three characters of a function name is enough to coax CoPilot into distributing LGPL-licensed code out of context, without a proper license. That's neither "emotional" nor "cherry-picked", it's a clear-cut license violation.
Quoted post unavailable.
> In a computer program, the lowest level of abstraction, the concrete code of the program, is clearly expression, while the highest level of abstraction, the general function of the program, might be better classified as the idea behind the program.
Copilot is alleged to be reproducing blocks of code verbatim, which fall into the expression side of the idea/expression distinction, which by your own links and statements appears to show that the allegations against Copilot are not false.
I'm not going to say you're necessarily disagreeing with reality (I'm not really sure what that's supposed to mean) but you're certainly contradicting the evidence you've brought.
Re: GitHub Copilot investigation
#235Earlier quoted context omitted.
I think I agree with this comment[1] from the other thread; never previously thought that a process being transformative means input and output datatypes do not coincide, but maybe that is it. 1: https://news.ycombinator.com/item?id=33240681
That's an interesting take, the whole level of indirection thing between Microsoft-OpenAI and StabilityAI and that research group is certainly another dimension to this that sort of muddies the waters.
Re: GitHub Copilot investigation
#236Re: GitHub Copilot investigation
#237If you're against Copilot as developer, you're shooting yourself in the foot. Locking up code under non-permissive licenses stymies the pace of code development and increases the costs of progress dramatically. We all stand on the shoulders of others before us. Including the organisations that stand to benefit the most from aggressive licensing.
Copy & paste isn't "standing on the shoulders of others". It is more like being an intestinal parasite.
Re: GitHub Copilot investigation
#238Earlier quoted context omitted.
> "look I prompted CoPilot for this piece of code that I already knew about and it spit it right out" https://twitter.com/docsparse/status/1581461734665367554 An english description plus three characters of a function name is enough to coax CoPilot into distributing LGPL-licensed code out of context, without a proper license. That's neither "emotional" nor "cherry-picked", it's a clear-cut license violation.
Quoted post unavailable.
the comment you're replying to stated that it was covered by the LGPL.
Re: GitHub Copilot investigation
#239Honestly, Github Copilot seems fine. It's just a tool that you're responsible for using responsibly. If I Google something, and copy and paste that, then Google is not responsible for my infringing. It's just "intelligent autocomplete".
Re: GitHub Copilot investigation
#240Earlier quoted context omitted.
> "look I prompted CoPilot for this piece of code that I already knew about and it spit it right out" https://twitter.com/docsparse/status/1581461734665367554 An english description plus three characters of a function name is enough to coax CoPilot into distributing LGPL-licensed code out of context, without a proper license. That's neither "emotional" nor "cherry-picked", it's a clear-cut license violation.
Quoted post unavailable.
Alternative theory: you're overconfident and wrong, and haven't even read the tweet I shared. CoPilot is observed to reproduce entire files (less two lines), down to variable names and comments, verbatim, from a repo that's covered by the LGPL.
If verbatim copies are not covered by copyright, then software can effectively never be copyrighted. And that there would be an extreme departure from "reality."
regarding your edit: this is a verbatim copy. The process you're describing is actually strengthening, not weakening, my argument. It allows material dissimilarity in the face of an overall similarity. Whatever process is meant to be applied to the licensed code and the allegedly infringing code, it will produce identical output given identical input. You're attempting to claim that the entire file would be deleted by the process and that the remainder would be an empty comparison which would (granted) be covered by fair use. And since CoPilot has been shown to redistribute multiple files, your "case" would hinge upon the entire repository not being covered by copyright. This is beyond absurd.
edit 2:
> Or don't! Just keep downvoting in support of your fantasies! Wheeeeee!
Please review the site guidelines. You're both whining about downvotes and sneering at the community with this. Probably time to take a break from the keyboard.
edit 3:
> Care to address the content of my claims?
Probably time to take a break from the keyboard.