• plz1@sh.itjust.works
    link
    fedilink
    arrow-up
    43
    ·
    5 days ago

    Looks like they are back-tracking, but knowing MS, it won’t be fully rolled back, just made slightly less shitty. They locked comments on the PR after the backlash.

    Thank you all for your feedback, professional or otherwise. Sorry about the regression. I will work on fixing this in 1.119.

    There is a number of issues with the Co-Author functionality:

    • It should never have been enabled when disableAIFeatures is on.
    • It should not add attribution to changes that were not done by AI.
    • We need to make sure it receives a more test coverage before change the default.
  • OpenPassageways@lemmy.zip
    link
    fedilink
    arrow-up
    22
    ·
    5 days ago

    Turned this shit off as soon as I saw it. What a bunch of bullshit. So IDEs have had quote completion features for years and now you want to claim that you “co-authored” my work because you suggested an end-quote and I hit tab? Fuck off, tempted to just disable this shit for my whole org when they change the billing model anyways.

    • dogs0n@sh.itjust.works
      link
      fedilink
      arrow-up
      8
      ·
      5 days ago

      He said AI didn’t make it, I would assume more than a Co-Authored would be required to ignore licenses, but that’s still a gray area anyways, I think?

  • Zink@programming.dev
    link
    fedilink
    arrow-up
    23
    ·
    5 days ago

    Gross. This reinforces my existing habit of not trying to integrate everything and instead use specific tools for specific functions. That’s kinda unix-like of me, right? lol.

    I like using the git CLI client in a standalone terminal window, and might still do so even if Microsoft weren’t constantly giving me reasons to never even consider changing.

    • ℍ𝕂-𝟞𝟝@sopuli.xyz
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 days ago

      Yes, if you want something that’s not in OpenVSX, you can go on the VS code store on your browser and download the extension as a VSIX file. Then you can add it to Codium manually.

  • hendrik@palaver.p3x.de
    link
    fedilink
    English
    arrow-up
    16
    arrow-down
    7
    ·
    edit-2
    5 days ago

    Guess someone misconfigured their VSCode?! Seems someone helped them find it.

    And seems this is a double-post.

  • Nalivai@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    4 days ago

    Oh, I’m very much in favour of this actually. If you use slopgen in any part of whatever you’re making, it should be labeled. If it was up to me, that would be a feature that you can only turn off by uninstalling copilot.

  • w3dd1e@lemmy.zip
    link
    fedilink
    arrow-up
    8
    arrow-down
    3
    ·
    5 days ago

    I hate it but honestly most people are probably using that shit and lying about it in commits.

    • ItsMeSpez@lemmy.world
      link
      fedilink
      arrow-up
      10
      ·
      5 days ago

      If this note were added to the commit whenever an LLM were used to author code then this would be a good feature but just silently adding it is so shitty.

      • w3dd1e@lemmy.zip
        link
        fedilink
        arrow-up
        5
        arrow-down
        2
        ·
        5 days ago

        I mean I suspect people use AI to write code but disguise it because they know it will upset others so it’s more likely than not that the commit was authored by AI even if VS Code can’t see it.

        Anyone dumb enough to leave that setting on probably doesn’t know what they are doing and probably is using AI.

        It’s still shit and misleading though and MS shouldn’t do it. I use VS Codium so I need to make sure it doesn’t happen there too.