5 ms·
Now if only we had a convenient way of using a distributed VCS without a central hub.
by alkonaut 11y ago
Now if only we had a convenient way of using a distributed VCS without a central hub.
- maze-le 11y agoDid someone say GitTorrent...? https://github.com/cjb/GitTorrent https://github.com/cjb/GitTorrent
- TeMPOraL 11y agoLooks exactly like what's needed. Is it safe enough though? I.e. can I rely on getting a non-maliciously-modified repo when I ask for particular SHA1? Also: sudo npm install --global gittorrent Cool! It automatically installs a local copy of half of GitHub! ;).
- maze-le 11y ago> Is it safe enough though? I'm not so sure about that. I've only used it once, an only to test its functionality, I didn't do any in-depth testing. Well I wouln't use it in production, but in a non-critical, small-scale project it could be worth a try...
- cjbprime 11y ago> I.e. can I rely on getting a non-maliciously-modified repo when I ask for particular SHA1? Someone could serve you a maliciously-modified repo, but Git itself would then reject those objects, since they won't lead to the SHA1 that Git knows that it's looking for -- you would keep trying other peers until someone gave you bits that match the correct SHA1.
- masklinn 11y agoThat sounds like a joke, but that's exactly the problem: the VCS has been distributed, but not all the services enmeshed around it: all the discussions (issues, pull requests, design debates, …). Github makes it easy to host git repositories, but so do a bunch of other services and it's not that hard to host your own either way or to set up trees of repository or multiple mirrors or what have you. The reason people use a central hub is all the meta-information and exchange about the code and the contributor communities. The repository on its own has very little value. And lest you think it's different for the kernel or whatever, a mailing list or an IRC channel are still centralised SPOF[0], when the ML provider goes down so does the project. [0] though possibly more resilient and easier to switch out of ones
- alemhnan 11y agoCould Ethereum (or a similar concept) be the solution of this kind of problems?
- 7373737373 11y agoTogether with systems such as ipfs.io, possibly yes. Have a look at https://github.com/whyrusleeping/gx https://github.com/whyrusleeping/gx But there still are many open problems: - incentivised file storage - fair name spaces - search and indexing and more.
- JohnDoe365 11y agoWhat about BitTorrent DHTs? Or dat http://dat-data.com/ http://dat-data.com/ Or Camlistore? https://camlistore.org/ https://camlistore.org/
- masklinn 11y agoThe problem of content-addressing — aside from the opaqueness to "shallow" contributions (nobody is going to install a content-addressed distributed filesystem just to report a bug to your software, don't kid yourself) — is what content-addressing means for resource updates. How do I get the most recent comment on the most recent bug report on one of my projects? In fact how do I even discover their existence from knowledge of the project's existence?
- morsch 11y agoHas anybody tried to store a project's metadata (issues and PRs) within the project's git repository itself? Seems like a logical step. If you don't want special git semantics around it, you'd have to be clever about how you store it so you don't have conflicts within the metadata. I.e. a naive design just adding a markdown file per issue or for all issues will require manual merging all the time. Still, it seems doable.
- masklinn 11y ago> Has anybody tried to store a project's metadata (issues and PRs) within the project's git repository itself? Seems like a logical step. There were a number of tentative distributed bug trackers a few years ago, they sucked and fizzled out. IIRC Fossil is an attempt at an entire distributed project management system, I don't know how it fares. > I.e. a naive design just adding a markdown file per issue or for all issues will require manual merging all the time. Still, it seems doable. That only works for your own personal project where you're the only user and contributor. Bug reporting by editing a markdown file (or even something actually usable like an org-mode file or an sqlite or BDB file) isn't going to scale very high and is way more effort than most bug reporters (even technical ones) will be willing to put in. And even if your users were willing to subject themselves to that, they still need a way to send back those contributions somehow.
- avip 11y agoWe do. It's called git instaweb && ngrok 1234