Don't encode POST bodies like GitHub Copilot, use URLSearchParams

Re:Don't encode POST bodies like GitHub Copilot, use URLSear... by oefrha on Thursday July 01, 2021 @07:22AM (#27698065)

This points to a general problem. Think of all those top-voted but wrong or bad StackOverflow answers, and how many people copy paste them verbatim. Now you’ve got an AI ingesting and reciting those answers to a wide audience, and they will make way into (even more) new code which is then fed back into the training corpus.

[ Parent | on HN ]

Re:Don't encode POST bodies like GitHub Copilot, use URLSear... by dkersten on Thursday July 01, 2021 @08:10AM (#27698300)

At least on SO other people can comment, down vote or write their own answers to warn others after an issue is found.

[ Parent | on HN ]

Re:Don't encode POST bodies like GitHub Copilot, use URLSear... by maerF0x0 on Thursday July 01, 2021 @08:34PM (#27706651)

The real issue is employers hiring folks who's only skill is gluing together things in SO. So frequently I see people asking others to do the real work for them, because their task wasn't on stackoverflow (or a basic google).

Those who know what to do aren't hanging around on SO because we know what we're doing and we don't have time to do other peoples' job for them.

[ Parent | on HN ]

Re:Don't encode POST bodies like GitHub Copilot, use URLSear... by intothev01d on Thursday July 01, 2021 @09:15AM (#27698742)

Looks like they've built https://en.wikipedia.org/wiki/Tay_(bot) but for code this time

[ Parent | on HN ]

Re:Don't encode POST bodies like GitHub Copilot, use URLSear... by seumars on Thursday July 01, 2021 @08:06AM (#27698276)

I'm not sure that's what feeds the feedback loop. Copilot is essentially a centralized distribution system for code, and efforts can be made to train it using "good" code as well. It's the equivalent of allowing thousands of developers to rewrite the top-voted answer on StackOverflow.

[ Parent | on HN ]