3 ms·

Istm it'd be easy for people to offer "sign up here and we'll pull and host your repo" services. Which would still be a lot better than Github, since it'd be co

Istm it'd be easy for people to offer "sign up here and we'll pull and host your repo" services. Which would still be a lot better than Github, since it'd be competetive and open.

jdc 6y ago
Right, the answer ofc is "put another coin in the machine" where machine does not mean some powerful central authority.
viraptor 6y ago
Given the social part of the project, I expect also a lot of "I'll host yours if you host mine" exchanges. And a "mirror projects I follow + everything from people I follow" option.
- Proven 6y ago
  The not-so-hidden cost of "free"... Compare the risk of some online "friend" you've never met not seeding vs Github being down. With your approach I'd need to seed like 5 other projects in order to stand a chance to get a better uptime vs. Github (which is free and requires no effort from my side). I still haven't seen an explanation of why go through all this trouble rather than set up own Git server at own domain, like many OSS projects already do (example: GNU.org)
  - viraptor 6y ago
    When setting up your own server you need to buy a domain, deal with running the infrastructure, deal with and require others to setup new identifies. You don't need to compete with github's uptime either. If you want that, you would setup/rent a seed. Without it you can rely on some kind of eventual replication. Also GitHub is free - for you, for now. MS can change it at any point. It's also not accessible from a number of countries.
    - rad_gruchalski 6y ago
      > When setting up your own server you need to buy a domain, deal with running the infrastructure, deal with and require others to setup new identifies. No, you don’t. You can push even to a bare repo on disk. If you want to share over network, ssh access vis IP address is enough. > Also GitHub is free - for you, for now. MS can change it at any point. It‘s easy to move. > It's also not accessible from a number of countries. That’s not really GitHub‘s fault, though. Any business / person operating a seed would have to comply with the same laws as GitHub today.
      - viraptor 6y ago
        > ssh access vis IP address is enough In that case you lose discovery, since your IP is likely to change and with SSH you still need to deal with identities. And you still need to operate that host. That's worst of both worlds. > It‘s easy to move. If use a separate social presence - it's easy-ish. If all your links point to GitHub repo - there's work involved, depending on the scale of the project. And that's assuming you did not buy into any of the value-add projects on GitHub. > Any business / person operating a seed would have to comply with the same laws as GitHub today. Apart from seeds in those countries which you can choose whether you want to talk to or not. So even if it doesn't matter to you, it does solve people's problems.

Istm it'd be easy for people to offer "sign up here and we'll pull and host your repo" services. Which would still be a lot better than Github, since it'd be competetive and open.

jdc 6y ago

Right, the answer ofc is "put another coin in the machine" where machine does not mean some powerful central authority.

viraptor 6y ago

Given the social part of the project, I expect also a lot of "I'll host yours if you host mine" exchanges. And a "mirror projects I follow + everything from people I follow" option.

Proven 6y ago
The not-so-hidden cost of "free"... Compare the risk of some online "friend" you've never met not seeding vs Github being down. With your approach I'd need to seed like 5 other projects in order to stand a chance to get a better uptime vs. Github (which is free and requires no effort from my side). I still haven't seen an explanation of why go through all this trouble rather than set up own Git server at own domain, like many OSS projects already do (example: GNU.org)
- viraptor 6y ago
  When setting up your own server you need to buy a domain, deal with running the infrastructure, deal with and require others to setup new identifies. You don't need to compete with github's uptime either. If you want that, you would setup/rent a seed. Without it you can rely on some kind of eventual replication. Also GitHub is free - for you, for now. MS can change it at any point. It's also not accessible from a number of countries.
  - rad_gruchalski 6y ago
    > When setting up your own server you need to buy a domain, deal with running the infrastructure, deal with and require others to setup new identifies. No, you don’t. You can push even to a bare repo on disk. If you want to share over network, ssh access vis IP address is enough. > Also GitHub is free - for you, for now. MS can change it at any point. It‘s easy to move. > It's also not accessible from a number of countries. That’s not really GitHub‘s fault, though. Any business / person operating a seed would have to comply with the same laws as GitHub today.
    - viraptor 6y ago
      > ssh access vis IP address is enough In that case you lose discovery, since your IP is likely to change and with SSH you still need to deal with identities. And you still need to operate that host. That's worst of both worlds. > It‘s easy to move. If use a separate social presence - it's easy-ish. If all your links point to GitHub repo - there's work involved, depending on the scale of the project. And that's assuming you did not buy into any of the value-add projects on GitHub. > Any business / person operating a seed would have to comply with the same laws as GitHub today. Apart from seeds in those countries which you can choose whether you want to talk to or not. So even if it doesn't matter to you, it does solve people's problems.