Live data from Hacker News

GitHub Copi­lot inves­ti­ga­tion

githubcopilotinvestigation.com

241–250 of 1001 posts

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

#241
Most of these points can also be raised against DALL-E 2, but software has one extra thorn: patents.

It's a common advice to not read software patents[1] because the infringement penalties are lower if you did so unwittingly, that is, by reinventing the patented technique yourself.

I wonder if using Copilot doesn't push the penalties back again to wilful infringement. Or worse, patent trolls poisoning the training data with patented algorithms.

[1]: https://queue.acm.org/detail.cfm?id=3489047

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

#242

Earlier quoted context omitted.

I mean, he clearly knew about that code in advance and used his prior knowledge to coax Copilot into spitting it out, yeah? Three characters can get you pretty far, that's 1 combination out of 125,580 (considering all english letters, upper and lower, along with most of the numbers and symbols on my keyboard), plus the description of a fairly complex algorithm. Also, this code is really just executing a mathematical…

Of course it is cherry picked. The idea is that it allows you to INTENTIONALLY void any copyright you want. So let's say I obtain an illegal copy of microsoft windows' source code. Under this precedent, what stops me from just (overfitting) training a neural network to produce the source code verbatim, sans any license notice? But it doesn't end there. What stops me from making a neural network that exactly reproduce…

It doesn't void anything. If you use Copilot to copy some licensed code illegally, you are the person in breach, not the tool. People using Copilot are possibly littering their code-base with future copyright liabilities, and they'd have no idea about it. Until someone writes an AI to find infringing software and automatically sue them...

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

#243
post #169

What 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…

> What 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? A better future to me. I don't want pictures of my face training ML models, nor do I want my art, or my code. I don't want my face to be more recognizable to AI, and I don't want my work to contribute to the consolidation of power to a few big firms. And for what, wh…

what if a service could tell you everywhere your photo was on the Internet?

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

#244

Earlier quoted context omitted.

Quoted post unavailable.

> If the code was covered by license in the first place the comment you're replying to stated that it was covered by the LGPL.

Slapping an LGPL on something does not mean that the utilitarian aspects are covered by the license!

---

Yes, I know that comments are expressive. They are clearly not utilitarian.

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

#246
post #190
post #103

Earlier quoted context omitted.

Github does plenty of stuff that you can't do. e.g. the contributions graph as just one example that comes to mind. That's not unfair, and not the basis for a lawsuit, it's just business. > Copilot is not only making money off of open-source, they are making money off of open-source in a way others can't. Of course! That's why MS paid squillions to buy Github.

You're not supposed to be able to use dominance in one market (git hosting) to gain dominance in another (AI powered code suggestions).

What do you mean "You're not supposed to"? Is there some law that forbids this? From my (potentially naive) POV this seems to be roughly equivalent to asking physics professors to stay away from mathematics since they are likely to have some relevant cross-domain expertise.

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

#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 principle that if it's (il)legal to do yourself, then it should be (il)legal to do the same thing with an AI's assistance.

The massive complicating factor is that nobody knows how to do (1) without also doing (2) as a side effect, because we don't understand how deep learning works well enough to control it.

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

#248
I don't understand why GitHub decided to run the project this way. This is a great idea but they messed the whole thing up. They could have make it opt-in from the very beginning and ask people to waive their rights, and I'm sure lots of people and lots of big projects would still be interested in joining the initiative. They could reward participants with, say, 3 year of Copilot access after it is officially launched, and people would love that. But instead they just take code without asking or attribution and keep pushing it, and now we are in this situation.

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

#249
post #150

What's with the default to "if it's not explicitly legal, it must be illegal"? Imagine if every new piece of software your wrote had to be tested for legality because you don't know that it's explicitly legal. Oh there aren't laws for this new thing, so I guess you should challenge yourself all the way to the supreme court? I get the author not liking Copilot, but I don't see that GitHub/Microsoft have any kind of ob…

> What's with the default to "if it's not explicitly legal, it must be illegal"? That's not how I interpret what's happening. People who produce things have rights over their products. Be it artists, craftsmen, inventors, entrepreneurs or coders. There is a legitimate question here as to whether CoPilot has infringed upon those rights. I don't see it being about "making something illegal." I see it about answering a…

A few snippets of code is not a product. If there was an open-source money-making product and someone builds a competing product using considerable help from CoPilot then that is a stronger case for damages then if someone just used some snippets of code in their own product.

But at that point, it would be just like someone cloning the Github code without following the license and in that case, it should become obvious that there is a clear violation harming the creators. But in most use cases of CoPilot, where-in people are just using it to build their own product, I doubt there is a cause for damages.

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

#250
MS needs to give up and terminate Copilot.

The potential legal issues are there, but that's not why Copilot should die.

Copilot should die for any (or a combination of all) these reasons (and more which I don't mention):

- the operator has to already understand the emitted code to be able to determine if it is what is needed, or to modify it if it is close but not quite right

- the operator may have a false sense of capability, leading to bugs and other problems that would appear later (in production?)

- wrong suggestions are a distraction from the careful mental structures which one maintains while writing software

- any problem that Copilot can solve with guaranteed correctness is probably trivial or already met by a (battle tested) library

Forgive the analogy, but effective automated code generation is like autonomous driving systems. Anything less than 100% accuracy is a risk, and in these examples risk of incorrect behavior is not acceptable.

Copilot seems like a pointy-haired boss fantasy where they can hire only junior programmers and expect successful software products.

Post reply on HN