@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. 😉