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
GitHub Copilot investigation
51–60 of 1001 posts
Re: GitHub Copilot investigation
#52It'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 Copilot investigation
#53This 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}))
Re: GitHub Copilot investigation
#54Does 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…
Re: GitHub Copilot investigation
#55The example given is "sparse matrix transpose 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.
Re: GitHub Copilot investigation
#56Earlier quoted context omitted.
> Over time, this process will starve these communities. User attention and engagement will be shifted into the walled garden of Copilot and away from the open-source projects themselves 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.
(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 Copilot investigation
#57This 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}))
Re: GitHub Copilot investigation
#58Is 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 Copilot investigation
#59Re: GitHub Copilot investigation
#60New 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…
I cannot parse what you are suggesting.