• GoatSynagogue@lemmy.world
    link
    fedilink
    English
    arrow-up
    84
    arrow-down
    20
    ·
    5 days ago

    A repo host that can remove your repo at any moment because someone can accuse your code of being “vibe coded” is not a repo host I’d trust. It shouldn’t matter how good, bad, or A.I. written your code is. It’s a hosting platform.

    • MrLLM@ani.social
      link
      fedilink
      English
      arrow-up
      18
      arrow-down
      1
      ·
      4 days ago

      I mean, I agree with you, but there’s still room for abuse.

      Have you seen OpenClaw’s issues page?

      Vibe coders and AI agents are floating it with garbage, if they were to do that to Codeberg, it’ll probably run out of resources pretty quickly

    • one_old_coder@piefed.social
      link
      fedilink
      English
      arrow-up
      9
      arrow-down
      3
      ·
      5 days ago

      I have the same feeling with SourceHut which bans projects related to crypto money. I think bitcoins is a stupid idea, but knowing that the owner of the site can ban you because of the stupid idea of the day is a very wrong idea.

    • Buddahriffic@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      4 days ago

      IMO everyone should have a local backup of everything they can get related to the repo. Like I know with git itself, anytime you clone the repo you get everything, but also the supporting stuff that is in the layer outside of git. IMO the host should mainly be the hub where everyone gets and interacts with the project, while everything else is already good to go in a new location, should the host either screw up in good faith, get corrupted by outside influences, or gets overrun by local or remote powers.

      This makes me a bit curious about whether the overall risk to projects is higher from individual local device failure or politics around who controls remote hosting services and the nature of the project.

        • Buddahriffic@lemmy.world
          link
          fedilink
          English
          arrow-up
          4
          ·
          4 days ago

          Yeah, as the other commenter mentioned, git is a distributed source control system, so all clones have the full history (though you can bump up the “starting point” to reduce the overhead of storing all previous commits).

          Hosts like github can add more features on top of that, which would have to be backed up separately, but you can automate the repository itself using a single command, which is the same command used to make a clone in the first place.