We discussed it back in March and here are some numbers for the bitcoin core repo:
View quoted note →
tbh those numbers are not that big. last time I checked, git implementations in the browser don't support these advanced flags. doing a full clone automatically in the browser is probably a bad idea as it is unfair on those who are bandwidth constrained.
But this could be done statelessly on a server fairly quickly. bandwidth on a VPS is probably quite cheap these days so if traffic volumes were low it shouldn't be too expensive.
Depending on the bandwidth vs storage costs it could be worth storing a clone of repositories and using that instead. That way it would be easier, or cheaper per interaction, to allow browsing commits, metadata, etc.
From a decentralisation point of view, I could build `ngit serve` which could be used instead (even in offline scenarios) instead of the proxy.
Login to reply
Replies (3)
Maybe, the user could choose to use the browser, use their locally cloned repos via a new command like `ngit serve`, or use a service that does it in the cloud and serves them the required data at much lower bandwidth.
View quoted note →
You could have a button to clone and display files, maybe?
What library would you use in the browser to do a clone?
I did
git clone --no-checkout --depth 1 --filter=blob:none
and got 216K, ahahah.
GitHub
GitHub - bitcoin/bitcoin: Bitcoin Core integration/staging tree
Bitcoin Core integration/staging tree. Contribute to bitcoin/bitcoin development by creating an account on GitHub.
O yeah?! I'm at a loss to think how I didn't try that before. This is the way.