Live data from Hacker News

GitHub Copi­lot inves­ti­ga­tion

githubcopilotinvestigation.com

51–60 of 1001 posts

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

#51
New tech creates winners and losers, and losers inevitably complain. See looms, VHS, Napster, etc. The more of this complaining I see, the more it falls flat. The only interesting thing is which side different communities end up being on.

To be fair, record companies were not in the least bit sympathetic. Open source contributors are easier to identify with, though imo it doesn't actually make their concerns more valid

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

#52
I'd be rather saddened if Copilot was shut down or neutered because of a few vocal few protesting against it.

It's been a massive productivity improvement to our senior devs, and I got so used to it that it's an annoyance when Copilot doesn't respond.

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

#53
post #41

This is a bit off-topic, but I wonder if there are people/teams right now creating git repos, doing the source code equivalent of "SEO" on it, and embedding backdoors in stupidly overoptimized for the training process code? I wonder when we'll hear about the first big hack that gets traced back to production code pushed live after CoPilot "suggested" eval(base64decode({webshell}))

If that code managed to hit production, then the problem is with the management and engineering leadership, not Copilot.

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

#54

Does GitHub not have the right to view and train from your content when you agree to their Terms of Service and upload your code? People are conflating their open source license with the one they give GitHub when making a GitHub account, but they are two entirely separate and parallel licenses. The former is for other people to use your code, the latter is for GitHub to host your code. If you don't like it, you are f…

[deleted]

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

#55
post #45

The example given is "sparse matrix trans­pose in the style of Tim Davis", but someone who wanted something with such specificity would be able to just take it from Github anyway, perhaps with a little more searching.

And would therefore have to follow the license of the code they took it from. That's exactly the point. Copilot is reproducing the same code but without the license.

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

#56
post #9

Earlier quoted context omitted.

> Over time, this process will starve these com­mu­ni­ties. User atten­tion and engage­ment will be shifted into the walled gar­den of Copi­lot and away from the open-source projects them­selves The author seems to be implying that since Copilot can reproduce the code of open source repository X in certain scenarios there'd be no reason for programmers to learn/use/engage with repository X. But this is silly. Maybe s…

It strips GPL, or any license.

It strips the (mandatory, in a lot of cases) licence text. But the licence still applies.

(Or I guess more technically, the original authors copyright still applies, and the rights granted to use the work under the license as an exception to the strict limitation under copyright - do not apply...)

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

#57
post #41

This is a bit off-topic, but I wonder if there are people/teams right now creating git repos, doing the source code equivalent of "SEO" on it, and embedding backdoors in stupidly overoptimized for the training process code? I wonder when we'll hear about the first big hack that gets traced back to production code pushed live after CoPilot "suggested" eval(base64decode({webshell}))

The less overt version of that is to figure out what mistakes copilot already makes (either things that are common in tutorials but not good in production, or things that are outdated, like hashing passwords with md5), and then systematically looking for software that includes such copilot suggestions.

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

#58
I've been trained on open source code, and there are likely many algorithms that I've internalized that are very similar to the "standard" way of performing an operation.

Is there a reason why an AI being trained on the same open source code isn't a similar situation? I agree that wholesale pasting of code chunks is an issue, but that hasn't been my experience with Copilot.

I'm not arguing for Copilot here...I'm genuinely curious why this would be considered any different.

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

#60

New tech creates winners and losers, and losers inevitably complain. See looms, VHS, Napster, etc. The more of this complaining I see, the more it falls flat. The only interesting thing is which side different communities end up being on. To be fair, record companies were not in the least bit sympathetic. Open source contributors are easier to identify with, though imo it doesn't actually make their concerns more val…

What does this comment even mean?

I cannot parse what you are suggesting.

Post reply on HN