Right - I see the other topic has been locked / author hasn’t returned to follow community rules.

Here’s the original topic https://news.ycombinator.com/item?id=49003386

and a measured (IMHO) response to it. (BTW, do your self a favour and change tabs with that site open :)

https://マリウス.com/i-regret-migrating-to-codeberg/

It’s a tough spot, Codeberg has found themselves in and I wish them luck. But beyond that, this is (yet) another reminder that in 2026, if you don’t self host it, the cloud is just someone else computer

  • DeckPacker@piefed.social
    link
    fedilink
    English
    arrow-up
    4
    ·
    27 days ago

    From what I understand from their blogpost, it was mostly about conserving their own resources, because a lot of the vibecoded projects they got were uploading insane amounts of binary releases and wasting resources on CI/CD while having no users or other collaborators.

    They wanna reserve more server space for projects, that actually productively use it, like bigger FOSS projects with actual users and contributors.

    That is perfectly understandable for me, even without taking my huge distaste for AI into consideration. Anyone that thinks, that this small, community funded project is obligated to host their huge slop repos semms pretty entitled to me.

    • WhyJiffie@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      1
      ·
      27 days ago

      before reading the blog post I was thinking the same. now I don’t.

      the worst of the LLM projects have no place on codeberg that’s for sure, but there would have been better ways than a blanket ban to limit the resource consumption of LLM and crypto projects. codeberg already has a storage quota system, they could be giving a lower quota for LLM projects, maybe also disable free CI for them, which I am a bit surprised they have given. and solve the reputation problem with banners. but no, total blanket ban based on feelings, it is.

      • poVoq@slrpnk.net
        link
        fedilink
        English
        arrow-up
        2
        ·
        27 days ago

        If the hard legal reality of all LLM generated code having a high risk of breaking copyright is “feelings” for you, then sure 🙄

        • FishFace@piefed.social
          link
          fedilink
          English
          arrow-up
          1
          ·
          27 days ago

          There is simply no way that is true. First, the legal arguments are dodgy:

          1. There is a good chance that LLMs are sufficiently transformative that courts will decide they don’t infringe the copyright of their sources.
          2. Even if not, hosts will get DMCA-style safe harbour protection and the most they’ll be liable for is takedown requests, which is a major thing for any large host.

          Second, there is no fucking way a western court is going to tell every big tech company they have to delete 99% of the code that was written since the start of the year, even if the law as written literally said verbatim, “use of any LLM output for any purpose is breach of copyright” because it doesn’t take a conspiracy theorist to realise that it’s politically impossible.

          You may not like that, but it means that, again, Codeberg is doing this based on feels.

        • AlteredEgo@lemmy.ml
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          25 days ago

          Not true, this does not occur frequently. This study and software LiCoEval from 2024 found 0.88% to 2.01% of code “strikingly similar to existing open-source implementations”. Afaik this is mostly textbook examples, snippets from stack overflow snippets or common github repositories, often replicated api examples and language boilerplate. How you prompt and refine also matters, and for generating novel code or business logic the LLM simply cannot use memorized snippets.

          Presumably since then LLMs have worked to reduce that number of memorized code. Since LLMs cannot memorize all their training data, that number is limited. LiCoEval can find the often memorized examples and train to remove them, or suppress them, or they find other ways to reduce direct reproduction from memorization. For example it would be possible to do what malus.sh does with all the training data. Then it cannot memorize copyrighted code.

          So for a model that came out 2026 this already small number might not be that relevant anymore.

    • endofline@lemmy.ca
      link
      fedilink
      English
      arrow-up
      0
      ·
      27 days ago

      What about setting quotas? They could introduce new account validations if they wanted

        • endofline@lemmy.ca
          link
          fedilink
          English
          arrow-up
          0
          arrow-down
          2
          ·
          25 days ago

          Slop is subjective… Bad code existed forever even eons before invention of llms

          • Valmond@lemmy.dbzer0.com
            link
            fedilink
            English
            arrow-up
            1
            ·
            25 days ago

            We’re not talking about bad code, we’re talking about slop code. It’s different. It’s easy just to generate slop code, it is not so easy to code all by yourself.

            • endofline@lemmy.ca
              link
              fedilink
              English
              arrow-up
              0
              arrow-down
              2
              ·
              25 days ago

              Slop has no definition and it’s subjective… It’s crystal clear that people cannot reliably determine what LLM slop from human slop