Related:

This is in a PR where Shougo, another long-time contributor, communicates entirely in walls of unparseable AI slop text: https://github.com/vim/vim/pull/19413

Thank you for the detailed feedback! I’ve addressed all the issues:

Thank you for the feedback! I agree that following the Vim 8+ naming convention makes sense.

Thank you for the feedback on naming!

Thanks for the suggestion! After thinking about this more, I believe repeat_set() / repeat_get() is the right choice:

Thank you for the feedback. A brief clarification.

https://hachyderm.io/@AndrewRadev/116176001750596207

@AndrewRadev@hachyderm.io

  • maegul (he/they)@lemmy.ml
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 month ago

    Couldn’t help but notice the casual gendering of Claude to “he” as well.

    Someone somewhere made the important observation not long ago that computer assistants tended to be gendered female when more like a secretary (Siri and Alexa) but now that AIs are “intelligent” and powerful … Claude now has to be a male.

    Especially weird (and telling?) when it is objectively gender neutral as it’s not human.

  • hperrin@lemmy.ca
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 month ago

    I spent literally all day yesterday working on this:

    https://sciactive.com/human-contribution-policy/

    I’ve started to add it to my projects. Eventually, it will be on all of my projects. I made it so that any project could adopt it, or modify it to their needs. It’s got a thorough and clear definition of what is banned, too, so it should help any argument over pull requests.

    Hopefully more projects will outright ban AI generated code (and other AI generated material).

      • hperrin@lemmy.ca
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 month ago

        Basically the best you can do is continue as normal, and if someone submits something that says it is or obviously is AI, point to this policy and reject it. Just having the policy should be a decent deterrent.

          • hperrin@lemmy.ca
            link
            fedilink
            English
            arrow-up
            0
            ·
            1 month ago

            People submitting malicious or deceptive code to open source repositories isn’t a new phenomenon. Just know that if you do it with any name in any way attached to your real name, and anyone finds out, you can kiss your reputation in the software dev community goodbye.

            Also, if you don’t admit that it’s AI generated, and it turns out to be copyrighted code, you’ll have a fun time in court trying to defend yourself for copyright infringement by admitting to fraud.

      • Retail4068@lemmy.world
        link
        fedilink
        arrow-up
        0
        arrow-down
        1
        ·
        1 month ago

        No, it’s a prejudiced hot take that’s completely and utterly unenforceable which will be seen as some Luddite behavior in 10 years when everyone is using the tooling.

  • Retail4068@lemmy.world
    link
    fedilink
    arrow-up
    0
    arrow-down
    1
    ·
    1 month ago

    Amazing watching you all screech at every maintainer that makes your software for free.

    I’m sure all of you are busy making forks which you’ll surely dedicate your own time to keeping AI out and keeping up.