Live data from Hacker News

Copilot regurgitating Quake code, including sweary comments

twitter.com

511–520 of 672 posts

Re: Copilot regurgitating Quake code, including sweary comments

#511

Earlier quoted context omitted.

You mean like the insanely annoying AIs that replaced Google search? The idiotic one that files Javascript books under "Law" in Amazon or the insulting one who runs Ad Sense and thinks my wife isn't good enough and I am stupid enough to leave her for some mail order bride?

Javascript books under "Law" is hilarious

I'm in for JavaScript Penal Code. Make that unwarranted type-coercing operator use punishable by law.

Re: Copilot regurgitating Quake code, including sweary comments

#512

Earlier quoted context omitted.

Apples and oranges: Stack overflow snippets are explicitly granted under a permissive license, as long as you attribute. https://stackoverflow.com/help/licensing It appears that the code that copilot is using is created under a huge variety of licenses, making it risky. On the other hand, a small snippet in a function that is derived from many existing pieces of other code may fall under fair use, even if it is not u…

It just seems bizarre that this wasn’t flagged internally at Microsoft. They have tons of compliance staff.

Could bet they baked in the legal fees and are taking a calculated risk

Re: Copilot regurgitating Quake code, including sweary comments

#513

Earlier quoted context omitted.

It just seems bizarre that this wasn’t flagged internally at Microsoft. They have tons of compliance staff.

That's because Microaoft doesn't dare use this for production code (presumably). They are 100% okay with letting their competitors get into legal hot water.

It’s surely a bit of a liability grey area?

Re: Copilot regurgitating Quake code, including sweary comments

#514

Earlier quoted context omitted.

Pretty sure they were being sarcastic. I also don't find your arguments persuasive in the slightest, and I find myself being skeptical of these recent moral outcries. I'm skeptical of its sincerity, and I don't buy it. "Master" has an etmylogical background far more diverse than the dichotomy to "slave". I can wholeheartedly say that I've not once thought to make that association. It's been a title for centuries. Mas…

Check out the recent Marc Rebillet stream with Flying Lotus and Reggie Watts. They absolutely destroy the bs around the use of the word master. I think both FL and RW will be quite representative of how African Americans (and the rest of the world) feel about this.

Do you have a timestamp? As enjoyable as as it is to listen to each of them, the stream was mostly music and almost two hours long.

Re: Copilot regurgitating Quake code, including sweary comments

#515

From the Copilot FAQ: > The technical preview includes filters to block offensive words And somehow their filters missed f*k? That doesn’t give a lot of confidence in their ability filter more nuanced text. Or maybe it only filters truly terrible offensive words like “master”.

In my testing of Copilot, the content filters only work on input , not output. Attempting to generate text from code containing "genocide" just has Copilot refuse to run. But you can still coerce Copilot to return offensive output given certain innocuous prompts.

Interesting how this continues to be an issue for GPT3 based projects.

A similar thing is happening in AI Dungeon, where certain words and phrases are banned to the point of suspending a users account if used a certain amount of times, yet they will happily output them when it is generated by GPT3 itself, and then punish the user if they fail to remove the offending pieces of text before continuing.

Re: Copilot regurgitating Quake code, including sweary comments

#516

Earlier quoted context omitted.

Do you also block stack overflow and give guidance to never copy code from that website or elsewhere on the Internet? I'm legitimately curious - my org internally officially denounces the copying of stack overflow snippets. Thankfully for my role it's moot as I mostly work with an internal non-public language, for better or worse, and I have no idea how well that's followed elsewhere in the wider company.

Who really copies stack overflow snippets verbatim? It's usually just easier to refer to it for help figuring out the right structure and then adapt it for your own needs. Usually it needs customization for your own application anyway (variables, class instances, etc).

I don't think I've ever copied code directly from any of the Stack* sites. I generally read all the answers (and comments) and then use what I learn to write my own (hopefully better) code specific to my needs.

Re: Copilot regurgitating Quake code, including sweary comments

#517
post #507

Earlier quoted context omitted.

"Shouldn't" isn't the same as "doesn't". I'm not anything close to an ML expert, and I have no opinion on whether what they're aiming for is possible, but this document^[1] (linked in your linked comment) states explicitly that they are aware of the recitation issue and are taking steps to mitigate it. So, in the context of the comment I replied to, I think Github is very far from claiming that recitation is "simply…

That kind of bullshit phrasing can only get you so far. It's like if some corporate PR department told you "we're aware of the halting problem, and are taking steps to mitigate it." You would rightly laugh them out of the room. It's not going to work, and the people making these statements either don't understand how much they don't understand, or are deluding themselves, or are actively lying to us. An honest answer…

You're using some pretty strong language here, but do you have any more substantive criticisms of the analysis they present at https://docs.github.com/en/github/copilot/research-recitatio... ? They seem to think the incidence of meaningful (i.e. substantively infringing) recitation is very low, and that their solution in those cases will be attribution rather than elimination.

Again, I'm not an ML expert, but that sounds a lot more reasonable to me than announcing one's intention to solve the halting problem.

Re: Copilot regurgitating Quake code, including sweary comments

#518
post #52
post #39

Earlier quoted context omitted.

If you find yourself copying code someone else in your organization wrote rather than abstracting it to a function in a shared library or building a more declarative framework to manage the problem, something horrible has happened.

Sometimes boilerplate is unavoidable. As an example, how do you send a GET request with libcurl in C with an authorization header? I can't tell you offhand, but I can tell you the file in my codebase that does have it, because I've duplicated the logic for two separate systems.

So you are saying you would rather every project in the world have at least one--if not, thanks to making it easier via Copilot, many--copies of this code rather than one shared library that provides a high-level abstraction for libcurl?... At least for your own code, how did you end up with two copies of duplicated logic rather than a shared library of functionality?

Re: Copilot regurgitating Quake code, including sweary comments

#519
post #409

Earlier quoted context omitted.

I'm out of the loop.

https://gitgud.io/AuroraPurgatio/aurorapurgatio https://www.reddit.com/user/non-taken-name

I don't get it, that seems like standard fare for an R-rated movie? And then it seems like some complained because they decided to start editing it down to a PG-13 movie?

Re: Copilot regurgitating Quake code, including sweary comments

#520
post #245
post #155

Earlier quoted context omitted.

Excel rounds doubles to 15 digits for display and comparison. The exact precision of doubles is something like 15.6 digits, those remaining 0.6 digits causing some of those examples floating (heh) around.

That depends https://randomascii.wordpress.com/2012/03/08/float-precision...

A lot of these edge cases are about theoretical concerns like "how many digits we need in decimal to represent an exact IEEE binary float".

In practice a double is 15.6 digits precise, which Excel rounds to 15 to eliminate some weirdness.

In their documentation they do cite their number type as 15 digit precision type. Ergo that's the semantic they've settled on.

Post reply on HN