@MightyPork I've seen @cwebber advocate about federation to the GitLab devs, so who knows

@Gargron @MightyPork Git already is distributed. You can host a public git repository on an ipfs namespace. You just don't have snazzy web interfaces and issue trackers that way though.

@andrath @Gargron oh jesus christ don't bring ipfs into this as if it's the answer to everything. i tried it and it just kept cooking my cpu without even doing anything

@MightyPork @Gargron I'm not saying it's the best way. It's *a* way. If you have another way to federate heaps of static files, then that would work too.

@andrath @Gargron I don't think you have to federate the files. pull requests are just metadata referencing different remotes and their branches

@MightyPork @Gargron You need a place to pull from. You can use a webserver that serves static files for pulling. But preferably you want something that you can spread around easily and keep track of so anything you push will end up in the correct place. That's a challenge without centralizing.

@andrath @Gargron this is not how git works tho. you pull from a remote. forking just copies the files to your remote (which is what people have been using on github to backup foreign projects, except it's all eggs in one basket kind of deal there

@MightyPork @Gargron cloning/forking isn't the issue, pushing your changes is. Especially accepting changes from other people. That's tricky to get right. On the other hand, if you have a popular project, loads of people own a backup of your code. 😉

@gargron this is what we get for centralising everything under one private entity.

Sign in to participate in the conversation
Mastodon

Follow friends and discover new ones. Publish anything you want: links, pictures, text, video. This server is run by the main developers of the Mastodon project. Everyone is welcome as long as you follow our code of conduct!