Codeberg seems to ban vibecoded Projects; reason might be german copyright law

>It looks like Codeberg want only copyrighted material in their service, so it is reliable in the future that e.g. licenses must be followed (e.g. GPL), and copyright doesn’t suddenly get declared as being of the model owner, and it isn’t a copy of something else.
That is a cautious reasonable position - in early days of LLM coding (3 years ago!) indemnity from model companies was a major issue globally because of the lack of clarity of the law around this. The US specifically has settled on it being (effectively?) public domain. But I don’t think that is fully settled, and it certainly isn’t settled in international copyright law.
The goal of the vague “mostly” in the Codeberg change is to ensure there is enough human input to the code they host, to be reasonably sure under German copyright law it is copyright of the person sharing it.

edit: link to poll that caused it (might be down due to high traffic) https://codeberg.org/Codeberg/org/pulls/1253#issuecomment-19820434

edit 1: i dont defend/oppose this move, i just find it interesting

  • poVoq@slrpnk.net
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    2
    ·
    2 hours ago

    Sorry but you are clearly delusional. There is no magic involved, just being able to look at the structure of the code and the pattern of the commits. It’s fairly easy in fact.

    • BJW@lemmus.org
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      3
      ·
      2 hours ago

      Oh, I see. You assume agentic AI that can perform it’s own commits. That would make it easy to tell, but you’d have to be really stupid to give AI such unfettered access to your repository.

      • TrickDacy@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        35 minutes ago

        you’d have to be really stupid to give AI such unfettered access to your repository

        So 1) we absolutely know people are much stupider than that. and 2) doing exactly that has widely been observed.

        • BJW@lemmus.org
          link
          fedilink
          English
          arrow-up
          1
          ·
          15 minutes ago

          Oh, without a doubt. They’ll get some low-hanging fruit, I’m sure.

      • JustEnoughDucks@slrpnk.net
        link
        fedilink
        English
        arrow-up
        1
        ·
        41 minutes ago

        And many, if not most, of the people vibe coding projects on git repos are that stupid. People who have never coded and never used anything other than git clone. That is just a fact of many of the people who do it. They are the people who think they are tech geniuses because they once made an LED blink on arduino or made the millionth timer app.

        It is just a fact of who is flooding the most slop projects. There are plenty of people who use AI in subtler or more useful ways, but that is not what is the target of anti-vibecoding rules. It is the 1000 slop projects generated bloated repositories fully in 1 day that are killing bandwidth and storage limits for everyone else.

      • poVoq@slrpnk.net
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        1 hour ago

        No need to assume that. Just by using LLMs to assist with code writing, the human in the loop changes their commit pattern.

        • BJW@lemmus.org
          link
          fedilink
          English
          arrow-up
          1
          arrow-down
          2
          ·
          edit-2
          55 minutes ago

          “Suspicious commit pattern” sounds like a pretty flimsy basis for banning a human from the platform. If nothing else, this futile crusade will be entertaining for almost everyone; except for their support staff who will need to investigate and either defend or repeal the ban each time there’s a false-positive, and a person is accused of wrong-think because yesterday they commit twice in an hour whereas they usually only commit once per hour.

          • poVoq@slrpnk.net
            link
            fedilink
            English
            arrow-up
            1
            ·
            edit-2
            53 minutes ago

            Most LLM users don’t try to hide it and the commit pattern is a result of the LLM assisted workflow, thus without losing the perceived benefits of using LLMs it can not be easily hidden. And the pattern isn’t only about when but also what. You might be oblivious to it, but the pattern is very clear and not possible to mistake with regular code writing patterns in an overall project. It is harder to spot in individual smaller PRs though, but that isn’t what Codeberg’s new policy is targeting.

            And anyways, this isn’t a question of “wrong-think”, but simply of Codeberg not wanting to be associated with such low quality, likely copyright violating and resource hogging projects. The LLM using people have plenty of other code forges to use, so it is really a non-issue 🤷

            • BJW@lemmus.org
              link
              fedilink
              English
              arrow-up
              1
              ·
              42 minutes ago

              They haven’t had a reason to hide it before now. I wouldn’t be surprised if someone now “vibe coded” a suite of obfuscation tools specifically to avoid detection.

              Yes, that’s why I said it’s a matter of prejudice. Assuming the projects are low quality, copyright violating and resource hogging are all conclusions reached by prejudice. You’re right there are other options available; my comment is just an observation.

                • BJW@lemmus.org
                  link
                  fedilink
                  English
                  arrow-up
                  1
                  ·
                  18 minutes ago

                  Yeah, and Lemmy users are unemployed basement dwellers.

                  What’s that, not all of them? Oh, but some of them, so I can claim it’s “objectively true” 🤷