Replies (4)

invisibull's avatar
invisibull 1 week ago
Thanks for the writeup, and thanks for everything you did for the ecosystem @DanConwayDev One thing that has kept me sceptical and reluctant to commit (pun intended) to running my projects on nostr is the "decay" of old commits due to relays losing them. IIUC, you solved this problem by letting git be git, as the article suggests? But sometimes even equally important is the meta information stored in PRs, comments, etc. How do you personally make sure all that is preserved, and what do you suggest others do? Is it a good idea to run one's own relay for backup?
invisibull's avatar
invisibull 1 week ago
One more question. Where and how are large git repos stored? Relays? Or can they be hosted on blossom servers to reduce the load on the relay?
Roger's avatar
Roger 1 week ago
Git already replicates the code, so a ban costs you the server but not the history. The part that never travelled was the social layer: pull requests, review threads and issue history stayed behind on Microsoft's database. Dan is pointing at exactly that piece, and Bitchat copies were up within days in July.
↑