Hacker News Reader

We tried. At first we built it on top of IPFS. It was much too slow. BitTorrent is interesting but we need a way to have mutability (repos change all the time). So we built the networking layer ourselves and the forge on top of that.

View on HN

If you built a mutable bittorrent layer yourself (like ipfs but better), then why not make it its own separate thing?

If that's what you've managed to pull off, that's like a way bigger deal than a p2p gitforge (not that that isn't super cool in itself)

I guess architecturally why does it need to be coupled to git and a git forge?

It's optimized for certain workloads around code collab, so for now we don't want to oversell it. It doesn't have to be coupled with Git, though Git is very efficient at synchronizing changes. The protocol currently can be used for other things than a forge, but having an application influence protocol development is very helpful.

Reply on news.ycombinator.com