versecafe

mostly once repos cross a certain size syncing them becomes a massive engineering effort, not git mirroring but the surrounding metadata that makes a forge useful

if only hn let us add the thumbnails to go with it

what's slow for you seeing a p50 around 130ms for requests on the t3code repo?

The actual PR/issue/review/comment/check syncing, git mirrors are trivial and something the spec thankfully makes extremely easy across all platforms

which part, t3code or gitcafe?

As far as I'm aware this is now the largest public repo to get synced between GitHub and another platform at ~18k PRs, ~4k issues, and over 200k total items between checks, comments, prs, reviews, etc

https://git.cafe if you want a team focused entirely on building a better forge experience rather than a github clone and don't want to deal with hosting yourself (and yes jj support is built in)

maintaining a fork on the zig version works short term but does open some questions about longterm stability/approach and if features should be cut to make maintenance easier; ie Bun.Image, fetch("", {grpc: true}), Bun.redis since it never got finished, etc

Not sweating, just heavily regretting running a fork to shim zig code in and hard forking to focus on stability over meaningless features and flashy AI rewrites.

This is likely irrelevant given bun has stopped taking community PR's entirely and Jarred is pitching that human contributors should be banned.

I do hope something good comes out of it with new platforms competing to refine, innovate, and iterate on git hosting and the UX of it all.

It's a huge technical commitment just to get the basics off the ground but if you're interested in something like that in very early stages is https://app.gitcafe.dev/ with a few public repos like

- https://app.gitcafe.dev/versecafe/webls - https://app.gitcafe.dev/nektro/zigmod - https://app.gitcafe.dev/risky/emailthing