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

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

I think they kind of do. On the Telemetry section of the Copilot site, they mention that they relay whether a suggestion was accepted or rejected.

I wonder, how much better could Github Copilot become by also looking that the modifications that are subsequently made to the accepted suggestions? Obviously this would go quite a bit further in terms of telemetry, and may become an issue. They would essentially be training based on non-public code at that point.

[ Parent | on HN ]

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

I guess that's a start, but I think comments, flagging, would have value. There's lots of reasons you might not accept something.

[ Parent | on HN ]

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

> On the Telemetry section of the Copilot site, they mention that they relay whether a suggestion was accepted or rejected.

That will make it the target of a collaborative bias attack.

[ Parent | on HN ]

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

Wait, are we sure it'd need to be collaborative?

[ Parent | on HN ]