• Anna
    link
    fedilink
    77 hours ago

    Stop trying to make fetch happen… OK what about pull.

    • @slampiskoOP
      link
      77 hours ago

      Sounds like fetch with extra steps

    • Ephera
      link
      fedilink
      188 hours ago

      Git itself is already capable of distributed usage, which is better than federated/decentralized.
      ‘Distributed’ and ‘decentralized’ in this sense:

      But in terms of the Git hosting service, with an issue board and all that, which is often called a “git forge”, you’ve got Forgejo working on an implementation, as well as ForgeFed as a general protocol (also work-in-progress).

      • @[email protected]
        link
        fedilink
        128 hours ago

        It’s funny how git was carefully designed to be decentralized and resistant to failure from any single node… and we immediately put all our fault tolerance on the back of one corporate-owned entity. Welp.

        • @[email protected]
          link
          fedilink
          3
          edit-2
          3 hours ago

          It’s because they solved all the version control problems, but not accessibility and discoverability. I’m probably not going to try and use git peer-to-peer with a total stranger.

    • mesamune
      link
      English
      8
      edit-2
      8 hours ago

      git yes.

      GitHub like services, no. Codeberg/forgejo looks promising, but theres a lot of discussion on what it should “look” like. Seems like its a pretty big challenge to do correctly.

    • @[email protected]
      link
      fedilink
      210 hours ago

      Wouldn’t help if your chosen instance is down, same problem unless multiple other people are storing your code on their servers

      Otherwise it kinda already is federated, you can have multiple remotes configured for a repo and push to both at once I’m pretty sure, then if one goes down you just use the other and sync later

  • @SaveMotherEarthEDF
    link
    2415 hours ago

    There should be a git cli client that plays gifs instead of errors.

    • @[email protected]
      link
      fedilink
      1616 hours ago

      I mean, it’s decentralized alright, but it doesn’t mean it’s HA or automatically replicated. You can just use a different origin server and push/pull from it instead.

      • @[email protected]
        link
        fedilink
        English
        26 hours ago

        My comment is more about how we have this decentralised tool, but we’re unable to get our collective heads out of the centralised model. We e ended up turning it back into centralised VCS.

        • @[email protected]
          link
          fedilink
          14 hours ago

          I get what you mean. GitHub and friends have pushed that back to a more centralized approach. However I think that it’s not too bad actually. Most projects tend to be centralized too

      • @[email protected]
        link
        fedilink
        1715 hours ago

        I’ve pulled and pushed to a common branch that only existed on the machines of a colleague and mine to avoid running automatic pipelines due to us pushing to the gitlab remote, since we were doing some experimentation. I’ve also pulled and pushed from a separate repo on my own machine.

        Git is fantastic, because these use cases are not edge cases but standard