Live data from Hacker News

Copilot regurgitating Quake code, including sweary comments

twitter.com

371–380 of 672 posts

Re: Copilot regurgitating Quake code, including sweary comments

#371

Probably an excellent reminder that both Google and Microsoft decided to use your private emails for a training set to create Smart Reply behavior that can "write emails for you", and they swore up and down there's no way that could ever leak private information. We need legislation banning companies from ingesting data into AI training sets without explicit permission.

Makes me wonder if github are using private repos in their training data.

Re: Copilot regurgitating Quake code, including sweary comments

#372

I'm honestly kinda amazed this as upvoted here as it is. Typically anything ML-related is upvoted to the top positions and any dissent harshly ridiculed. Anyways... it appears those who thought about this as if it was a glorified code search engine were close to being right.

I still don't think it's just a glorified code search engine.

Context-sensitive data retrieval is undoubtedly a part of it, though and the question is how big and relevant is that part and what are the consequences?

To me the biggest issue is that it's impossible to tell whether the suggestions are verbatim reproductions of training material and thus problematic.

It goes to show that this tool and basically every tool relying on the same or similar technology must now be assumed to do this and thus any code suggestion must be regarded plagiarism until proven otherwise. As a consequence such tools are now off-limits for commercial or open source development...

Re: Copilot regurgitating Quake code, including sweary comments

#375
post #220

Earlier quoted context omitted.

Apparently you haven't seen many of the demos that people are showing off? Because saying that this only occurs when the author is explicitly asking for copied code is blatantly false.

No I haven't. If you think the other demos are more interesting please link to them. I'm just saying that this demo is biased and that we can't draw any conclusion from it. Actually the author has just confessed optimizing it for entertainment in a sister comment. That doesn't mean that the claim is false but it doesn't show that it is true either.

I think you misunderstood my comment. The same code gets generated if you call the function `float fast_rsqrt` or `float fast_isqrt` for instance. I intentionally wanted it to be looking like `Q_rsqrt` so that people pick up on it quicker.

Re: Copilot regurgitating Quake code, including sweary comments

#378
post #59

One has to admit, Copilot raises many questions regarding global code quality, reviewing processes and copyright. It's a marketing success.

Honestly, I see this exact issue as the main accomplishment of Copilot. It shows that the black-box machines are to be considered harmful and are incompatible with the current intellectual property and privacy frameworks.

This issue goes way beyond just code - imagine GPT-like systems being used in medical diagnosis and results can suddenly depend on the date of the CT-scan or the name of patient, because the black-box simply regurgitates training data...

Re: Copilot regurgitating Quake code, including sweary comments

#379

Earlier quoted context omitted.

> The ruby one isn't outright terrible, but shows a very Americanized way to do street addresses that would probably become a problem later. As someone who has been coding up address storage and validation for the past week in my current job, that one really made me laugh. Mostly because it tries to simplify all the stuff I have been analyzing and mulling over for a week into a single auto-complete. Spoiler: The Gith…

Isn't address storage and validation a solved problem? Why is it so complicated?

Ex:

412 1/2 E E NE

412 1/2 A E

1E MAIN

1 E MAIN

FOO & BAR

123 ADAM WEST RD

123 ADAM WEST

123 EAST WEST

Re: Copilot regurgitating Quake code, including sweary comments

#380
post #365

Earlier quoted context omitted.

> The ruby one isn't outright terrible, but shows a very Americanized way to do street addresses that would probably become a problem later. As someone who has been coding up address storage and validation for the past week in my current job, that one really made me laugh. Mostly because it tries to simplify all the stuff I have been analyzing and mulling over for a week into a single auto-complete. Spoiler: The Gith…

> I don't really have a problem typing. Im absolutely with you and want to upvote that part of the comment x100. Unfortunately it's often considered a fairly spicy opinions. Entire frameworks (Rails) are built around the idea of typing as little as possible. Others can't even be mentioned without the topic of boilerplate/keystroke count causing a flame war (Redux). A lot of engineers equate their value with the amoun…

I never commit something that I can easily google (with a high quality solution) to memory
Post reply on HN