We're really talking about the same thing. The only way to enforce p2p is to forbid servers, it's too useful to have specialized software running somewhere wit

We're really talking about the same thing. The only way to enforce p2p is to forbid servers, it's too useful to have specialized software running somewhere with a fixed IP address, DNS, and fat fiber. Even the most successful p2p protocols, bitcoin and bittorrent, are pretty server-heavy in practice. That said, I want my version control to contain, locally, everything relevant to software development, and use some sort of pub/sub model to propagate my changes. Here, a server is helpful: gives a fixed domain, a canonical place to retrieve the repo, and so on and so forth. But it should be more like Fossil, where everything is stored locally and you can spin up your own localhost to access the GUI through the browser. Fossil is too monolithic, I reluctantly had to abandon it on that basis, but it points in the correct direction IMHO. And if the hub is down, as long as peers and backups haven't changed IP addresses since the last time we communicated, I don't see why work couldn't continue.