There is! https://radicle.dev :)
replyFrom today:
replyHardenedBSD Is Now Officially on Radicle
the fact that you, as the creator of a "competitor", post this as-is without a "At $co, we…" run-on is a good look
replyOh, that's pretty cool! Now I can't decide whether that approach or one based on AT is better...
replyPick whichever. We <3 the Radicle team and they're admittedly solving a much harder problem (gossiping git!) and rather elegantly at that.
replyYeah I’ve met the Radicle people a couple times. I’ve never given it a thorough review but, for their goals, their designs have always seemed strong, and they’re pleasant people to chat with.
replyThe main difference was atproto wanted to tackle scale, so we went with a servers & aggregation model. Radicle is going for device-to-device networking as a primary goal.
Do you think it will be possible to use them together? Having some sort of unified distributed system is intriguing to me. (e.g. can the Radical foundation and AT-proto foundation integrate, even?)
replyThere is also ForgeFed/vervis
replygittorrents were talked about and built at least 15 if not 20 years ago.
replythe issue isn't mirroring of data, this is a solved problem. everything else that a forge does is a problem - issue tracking, PRs, reviews, CI/CD, authn, authz, secrets, audit trails, ...
BitTorrent also enabled search engines to be built easily, which created discoverability. Unfortunately it's a much harder problem for git repos, especially when competing with GitHub search.
replyRadicle may be what you're after
replyGit is already distributed by itself. The management-part is what's missing (mergerequests, permissions, issues..), and it's disputable whether this is really necessary, or just a nice to have.
reply